Error when shrinking data file in SQL 2005

I've just upgraded my production server from 2K to 2K5, and I've got one
database that is way too big (almost 5 GB with 88% free space). I have no
problems shrinking the transaction log, but when I try to shrink the data
file, I get the following message:
"A severe error occurred on the current command. The results, if any,
should be discarded. File ID 1 of database ID 8 cannot be shrunk as it is
either being shrunk by another process or is empty. (Microsoft SQL Server,
Error: 0)"
At one point, I had autoshrink turned on for the database to handle the
transaction log, but this has never been a problem for the data file. Durin
g
my upgrade process, I detatched this database and copied it over to my test
server, where I am still having no problems. Help!!Hi
I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC CHECKDB?
John
"Gary" wrote:

> I've just upgraded my production server from 2K to 2K5, and I've got one
> database that is way too big (almost 5 GB with 88% free space). I have no
> problems shrinking the transaction log, but when I try to shrink the data
> file, I get the following message:
> "A severe error occurred on the current command. The results, if any,
> should be discarded. File ID 1 of database ID 8 cannot be shrunk as it is
> either being shrunk by another process or is empty. (Microsoft SQL Server,
> Error: 0)"
> At one point, I had autoshrink turned on for the database to handle the
> transaction log, but this has never been a problem for the data file. Dur
ing
> my upgrade process, I detatched this database and copied it over to my tes
t
> server, where I am still having no problems. Help!!
>|||"John Bell" wrote:
[vbcol=seagreen]
> I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC >CHECKDB?[/vbc
ol]
John,
I ended up getting that problem solved (by detaching and reattaching the
database and then taking it offline and rebooting the server), but I've got
another somewhat related problem. In a maintenance plan I was doing a
rebuild on the indexes for the database. That maintenance plan never
completed (it hung up), and now my data file size is about 4 GB (it was abou
t
500 MB) with basically no free space. I've run DBCC CHECKDB along with abou
t
everything else I can think of, and I can't find any way to get that file
size back down.
Thanks!|||Hi Gary
Is this the data file or log file? If it is the log file you can use BACKUP
LOG ... WITH TRUNCATE_ONLY and then DBCC SHRINKFILE.
John
"Gary" wrote:

> "John Bell" wrote:
>
> John,
> I ended up getting that problem solved (by detaching and reattaching the
> database and then taking it offline and rebooting the server), but I've go
t
> another somewhat related problem. In a maintenance plan I was doing a
> rebuild on the indexes for the database. That maintenance plan never
> completed (it hung up), and now my data file size is about 4 GB (it was ab
out
> 500 MB) with basically no free space. I've run DBCC CHECKDB along with ab
out
> everything else I can think of, and I can't find any way to get that file
> size back down.
> Thanks!
>|||John,
No, it's the data file. I've tried to manually rebuild/reorganize
individual indexes, and that's not really working, either.
Gary
[vbcol=seagreen]
> Hi Gary
> Is this the data file or log file? If it is the log file you can use BACKU
P
> LOG ... WITH TRUNCATE_ONLY and then DBCC SHRINKFILE.
> John
>
> "Gary" wrote:
>|||Hi
You can use sp_spaceused to see what is being used by the file, and DBCC
SHRINKFILE will shrink it. In general it is not a good idea to contunually
expand/shrink the files.
John
"Gary" wrote:
[vbcol=seagreen]
> John,
> No, it's the data file. I've tried to manually rebuild/reorganize
> individual indexes, and that's not really working, either.
> Gary
>|||i came accross this problem too. what did was to restart the service
and executed dbcc shrinkfile again. that time it succeeded.|||Hi,
I got the same error,
When i moved all of user tables and indexes out of primary FG and to a new
FG, my Primary is left with around 17GB of which less than a 1GB is actually
used, and when I ran shrink file on the only file on that FG, it took ages.
then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is not
that bad :-) ). when I ran it again I get the error described.
when I back up the db and restore it, then I can shrink the file.
this is a db in simle mode, dev environment. worried what happens when we go
to production with this.
error:
File ID 1 of database ID X cannot be shrunk as it is either being shrunk by
another process or is empty.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should
be discarded.
CTS DBA
"XNMB" wrote:

> i came accross this problem too. what did was to restart the service
> and executed dbcc shrinkfile again. that time it succeeded.
>|||I tried detach and re-attach the database fie and run DBCC SHRINKFILE
But I wouldn't recommend shrinking. Here's an article by the great Tibor
Karaszi on database shrinking
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...[vbcol=seagreen]
> Hi,
> I got the same error,
> When i moved all of user tables and indexes out of primary FG and to a new
> FG, my Primary is left with around 17GB of which less than a 1GB is
> actually
> used, and when I ran shrink file on the only file on that FG, it took
> ages.
> then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is
> not
> that bad :-) ). when I ran it again I get the error described.
> when I back up the db and restore it, then I can shrink the file.
> this is a db in simle mode, dev environment. worried what happens when we
> go
> to production with this.
> error:
> File ID 1 of database ID X cannot be shrunk as it is either being shrunk
> by
> another process or is empty.
> Msg 0, Level 11, State 0, Line 0
> A severe error occurred on the current command. The results, if any,
> should
> be discarded.
> --
> CTS DBA
>
> "XNMB" wrote:
>|||hi,
thanks for the reply.
I know what you mean, but what I don't understand is why shrinkfile wouldn't
work when there's so much free space in the file.
over 8GB
if the original database shrunk in SQL 2000 it works perfectly.
Thanks
--
CTS DBA
"bass_player [SBS-MVP]" wrote:

> I tried detach and re-attach the database fie and run DBCC SHRINKFILE
> But I wouldn't recommend shrinking. Here's an article by the great Tibor
> Karaszi on database shrinking
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> "CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
> news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...
>
>

Error when shrinking data file in SQL 2005

I've just upgraded my production server from 2K to 2K5, and I've got one
database that is way too big (almost 5 GB with 88% free space). I have no
problems shrinking the transaction log, but when I try to shrink the data
file, I get the following message:
"A severe error occurred on the current command. The results, if any,
should be discarded. File ID 1 of database ID 8 cannot be shrunk as it is
either being shrunk by another process or is empty. (Microsoft SQL Server,
Error: 0)"
At one point, I had autoshrink turned on for the database to handle the
transaction log, but this has never been a problem for the data file. During
my upgrade process, I detatched this database and copied it over to my test
server, where I am still having no problems. Help!!Hi
I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC CHECKDB?
John
"Gary" wrote:
> I've just upgraded my production server from 2K to 2K5, and I've got one
> database that is way too big (almost 5 GB with 88% free space). I have no
> problems shrinking the transaction log, but when I try to shrink the data
> file, I get the following message:
> "A severe error occurred on the current command. The results, if any,
> should be discarded. File ID 1 of database ID 8 cannot be shrunk as it is
> either being shrunk by another process or is empty. (Microsoft SQL Server,
> Error: 0)"
> At one point, I had autoshrink turned on for the database to handle the
> transaction log, but this has never been a problem for the data file. During
> my upgrade process, I detatched this database and copied it over to my test
> server, where I am still having no problems. Help!!
>|||"John Bell" wrote:
> I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC >CHECKDB?
John,
I ended up getting that problem solved (by detaching and reattaching the
database and then taking it offline and rebooting the server), but I've got
another somewhat related problem. In a maintenance plan I was doing a
rebuild on the indexes for the database. That maintenance plan never
completed (it hung up), and now my data file size is about 4 GB (it was about
500 MB) with basically no free space. I've run DBCC CHECKDB along with about
everything else I can think of, and I can't find any way to get that file
size back down.
Thanks!|||Hi Gary
Is this the data file or log file? If it is the log file you can use BACKUP
LOG ... WITH TRUNCATE_ONLY and then DBCC SHRINKFILE.
John
"Gary" wrote:
> "John Bell" wrote:
> > I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC >CHECKDB?
> John,
> I ended up getting that problem solved (by detaching and reattaching the
> database and then taking it offline and rebooting the server), but I've got
> another somewhat related problem. In a maintenance plan I was doing a
> rebuild on the indexes for the database. That maintenance plan never
> completed (it hung up), and now my data file size is about 4 GB (it was about
> 500 MB) with basically no free space. I've run DBCC CHECKDB along with about
> everything else I can think of, and I can't find any way to get that file
> size back down.
> Thanks!
>|||John,
No, it's the data file. I've tried to manually rebuild/reorganize
individual indexes, and that's not really working, either.
Gary
> Hi Gary
> Is this the data file or log file? If it is the log file you can use BACKUP
> LOG ... WITH TRUNCATE_ONLY and then DBCC SHRINKFILE.
> John
>
> "Gary" wrote:
> > "John Bell" wrote:
> >
> > > I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC >CHECKDB?
> >
> > John,
> >
> > I ended up getting that problem solved (by detaching and reattaching the
> > database and then taking it offline and rebooting the server), but I've got
> > another somewhat related problem. In a maintenance plan I was doing a
> > rebuild on the indexes for the database. That maintenance plan never
> > completed (it hung up), and now my data file size is about 4 GB (it was about
> > 500 MB) with basically no free space. I've run DBCC CHECKDB along with about
> > everything else I can think of, and I can't find any way to get that file
> > size back down.
> >
> > Thanks!
> >|||Hi
You can use sp_spaceused to see what is being used by the file, and DBCC
SHRINKFILE will shrink it. In general it is not a good idea to contunually
expand/shrink the files.
John
"Gary" wrote:
> John,
> No, it's the data file. I've tried to manually rebuild/reorganize
> individual indexes, and that's not really working, either.
> Gary
>
> > Hi Gary
> >
> > Is this the data file or log file? If it is the log file you can use BACKUP
> > LOG ... WITH TRUNCATE_ONLY and then DBCC SHRINKFILE.
> >
> > John
> >
> >
> > "Gary" wrote:
> >
> > > "John Bell" wrote:
> > >
> > > > I assume you are using DBCC SHRINKFILE? Have you tried doing a DBCC >CHECKDB?
> > >
> > > John,
> > >
> > > I ended up getting that problem solved (by detaching and reattaching the
> > > database and then taking it offline and rebooting the server), but I've got
> > > another somewhat related problem. In a maintenance plan I was doing a
> > > rebuild on the indexes for the database. That maintenance plan never
> > > completed (it hung up), and now my data file size is about 4 GB (it was about
> > > 500 MB) with basically no free space. I've run DBCC CHECKDB along with about
> > > everything else I can think of, and I can't find any way to get that file
> > > size back down.
> > >
> > > Thanks!
> > >|||i came accross this problem too. what did was to restart the service
and executed dbcc shrinkfile again. that time it succeeded.|||Hi,
I got the same error,
When i moved all of user tables and indexes out of primary FG and to a new
FG, my Primary is left with around 17GB of which less than a 1GB is actually
used, and when I ran shrink file on the only file on that FG, it took ages.
then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is not
that bad :-) ). when I ran it again I get the error described.
when I back up the db and restore it, then I can shrink the file.
this is a db in simle mode, dev environment. worried what happens when we go
to production with this.
error:
File ID 1 of database ID X cannot be shrunk as it is either being shrunk by
another process or is empty.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should
be discarded.
--
CTS DBA
"XNMB" wrote:
> i came accross this problem too. what did was to restart the service
> and executed dbcc shrinkfile again. that time it succeeded.
>|||I tried detach and re-attach the database fie and run DBCC SHRINKFILE
But I wouldn't recommend shrinking. Here's an article by the great Tibor
Karaszi on database shrinking
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...
> Hi,
> I got the same error,
> When i moved all of user tables and indexes out of primary FG and to a new
> FG, my Primary is left with around 17GB of which less than a 1GB is
> actually
> used, and when I ran shrink file on the only file on that FG, it took
> ages.
> then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is
> not
> that bad :-) ). when I ran it again I get the error described.
> when I back up the db and restore it, then I can shrink the file.
> this is a db in simle mode, dev environment. worried what happens when we
> go
> to production with this.
> error:
> File ID 1 of database ID X cannot be shrunk as it is either being shrunk
> by
> another process or is empty.
> Msg 0, Level 11, State 0, Line 0
> A severe error occurred on the current command. The results, if any,
> should
> be discarded.
> --
> CTS DBA
>
> "XNMB" wrote:
>> i came accross this problem too. what did was to restart the service
>> and executed dbcc shrinkfile again. that time it succeeded.
>>|||hi,
thanks for the reply.
I know what you mean, but what I don't understand is why shrinkfile wouldn't
work when there's so much free space in the file.
over 8GB
if the original database shrunk in SQL 2000 it works perfectly.
Thanks
--
CTS DBA
"bass_player [SBS-MVP]" wrote:
> I tried detach and re-attach the database fie and run DBCC SHRINKFILE
> But I wouldn't recommend shrinking. Here's an article by the great Tibor
> Karaszi on database shrinking
> http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> "CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
> news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...
> > Hi,
> >
> > I got the same error,
> > When i moved all of user tables and indexes out of primary FG and to a new
> > FG, my Primary is left with around 17GB of which less than a 1GB is
> > actually
> > used, and when I ran shrink file on the only file on that FG, it took
> > ages.
> > then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is
> > not
> > that bad :-) ). when I ran it again I get the error described.
> >
> > when I back up the db and restore it, then I can shrink the file.
> > this is a db in simle mode, dev environment. worried what happens when we
> > go
> > to production with this.
> >
> > error:
> > File ID 1 of database ID X cannot be shrunk as it is either being shrunk
> > by
> > another process or is empty.
> > Msg 0, Level 11, State 0, Line 0
> > A severe error occurred on the current command. The results, if any,
> > should
> > be discarded.
> >
> > --
> > CTS DBA
> >
> >
> > "XNMB" wrote:
> >
> >> i came accross this problem too. what did was to restart the service
> >> and executed dbcc shrinkfile again. that time it succeeded.
> >>
> >>
>
>|||I had similar problem with the data file shrinking, but I think I solved the
problem safer way (without restoring or detaching the database and without
service restart):
1) Backup database log
2) Run sp_helpfile and note the size of the data file (6444160 KB, for
example)
3) Run ALTER DATABASE and use the file size number slightly bigger than
actual file size:
ALTER DATABASE TESTDB
MODIFY FILE
( NAME = TESTDB_DATA
, SIZE = 6444165KB )
4) Now shrink file command works:
USE TESTDB
GO
DBCC SHRINKFILE (N'TESTDB_DATA' , TRUNCATEONLY)
GO
Let me know if this worked for anybody else.
"CTS_DBA" wrote:
> hi,
> thanks for the reply.
> I know what you mean, but what I don't understand is why shrinkfile wouldn't
> work when there's so much free space in the file.
> over 8GB
> if the original database shrunk in SQL 2000 it works perfectly.
> Thanks
> --
> CTS DBA
>
> "bass_player [SBS-MVP]" wrote:
> > I tried detach and re-attach the database fie and run DBCC SHRINKFILE
> >
> > But I wouldn't recommend shrinking. Here's an article by the great Tibor
> > Karaszi on database shrinking
> > http://www.karaszi.com/SQLServer/info_dont_shrink.asp
> >
> > "CTS_DBA" <CTSDBA@.discussions.microsoft.com> wrote in message
> > news:630320F3-22A4-4D33-A245-54D14D4784FD@.microsoft.com...
> > > Hi,
> > >
> > > I got the same error,
> > > When i moved all of user tables and indexes out of primary FG and to a new
> > > FG, my Primary is left with around 17GB of which less than a 1GB is
> > > actually
> > > used, and when I ran shrink file on the only file on that FG, it took
> > > ages.
> > > then I stoped it (in 2000 it would have taken max 2-3 hours, our SAN is
> > > not
> > > that bad :-) ). when I ran it again I get the error described.
> > >
> > > when I back up the db and restore it, then I can shrink the file.
> > > this is a db in simle mode, dev environment. worried what happens when we
> > > go
> > > to production with this.
> > >
> > > error:
> > > File ID 1 of database ID X cannot be shrunk as it is either being shrunk
> > > by
> > > another process or is empty.
> > > Msg 0, Level 11, State 0, Line 0
> > > A severe error occurred on the current command. The results, if any,
> > > should
> > > be discarded.
> > >
> > > --
> > > CTS DBA
> > >
> > >
> > > "XNMB" wrote:
> > >
> > >> i came accross this problem too. what did was to restart the service
> > >> and executed dbcc shrinkfile again. that time it succeeded.
> > >>
> > >>
> >
> >
> >

Error when running RedGate SQL Backup Job in SQL Server 2005

I have 4 SQL Server 2005 production servers that I installed RedGate SQL Bac
k
up on. All but one run fine. The one that doesn't I get the below error.
Executed as user : AD-DomainName\UserName. SQL Backup job failed with
exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step f
ailed.
The back up is backing up to the AD server which is different than the
server the job runs on. It is a shared folder on the AD and the permissions
grant the owner of the job Full Access.
I do not know what else to do with this issue. It mirrors the other 3 that
work fine.
Any and all help is appreciated.
-ChrisChris,
SQL Server caches login information from active directory. The one
troublesome machine has apparently cached out of date AD information. In
David Grey's BLOG he discusses a similar problem (not with Red Gate) that
may help you resolve.
http://www.codefounders.com/communi...entication.aspx
RLF
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2B7A5543-C258-4BA2-8CF4-BF2A7F4F1434@.microsoft.com...
>I have 4 SQL Server 2005 production servers that I installed RedGate SQL
>Back
> up on. All but one run fine. The one that doesn't I get the below error.
> Executed as user : AD-DomainName\UserName. SQL Backup job failed with
> exitcode 0 SQL Error code 18456[SQLState 42000] (Error 50000) The step
> failed.
> The back up is backing up to the AD server which is different than the
> server the job runs on. It is a shared folder on the AD and the
> permissions
> grant the owner of the job Full Access.
> I do not know what else to do with this issue. It mirrors the other 3 that
> work fine.
> Any and all help is appreciated.
> -Chris
>

Error when opening Maintenance Plan in SQL 2000

I've recently installed SQL 2000 on a new server. Migrated production
databases and data from old SQL 6.5.
Everything checks out OK applications work fine, all data
came over no problem. However... when I try to open or create a
database maintenance plan I get is error:
Microsoft SQL-DMO (ODBC SQLState: 42S22)
Error 207: Invalid column name 'category_id'.
Invalid column name 'netsend_address'.
Invalid column name 'last_netsend_date'.
Invalid column name 'last_netsend_time'.
these colune names do not exist, do I need to create them and if so,
which table do they need to be in? Any help is greatly appreciated. ThanksHI;
Columns mentioned below are in the sysoperators table in msdb database
netsend_address nvarchar 100 NOT NULL
last_netsend_date int 4 NULL
last_netsend_time int 4 NULL
category_id int 4 NULL
IT Looks to me that something happend to your msdb database.
Do you have a backup to restore it from before migration?
--
Danijel Novak
"Lisa Hoffman" <LisaHoffman@.reish.com> wrote in message
news:OH0vej2BGHA.3584@.TK2MSFTNGP11.phx.gbl...
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so, which
> table do they need to be in? Any help is greatly appreciated. Thanks
>|||Hi Lisa
You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
If you need to restore MSDB check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
John
"Lisa Hoffman" wrote:
> I've recently installed SQL 2000 on a new server. Migrated production
> databases and data from old SQL 6.5.
> Everything checks out OK applications work fine, all data
> came over no problem. However... when I try to open or create a
> database maintenance plan I get is error:
> Microsoft SQL-DMO (ODBC SQLState: 42S22)
> Error 207: Invalid column name 'category_id'.
> Invalid column name 'netsend_address'.
> Invalid column name 'last_netsend_date'.
> Invalid column name 'last_netsend_time'.
> these colune names do not exist, do I need to create them and if so,
> which table do they need to be in? Any help is greatly appreciated. Thanks
>
>|||The MS article states "The model and msdb databases can only be restored
from backups created on a Microsoft® SQL Server� 2000 server. Restore of
backups of these databases made on SQL Server version 7.0 or earlier is
not supported."
This was a migration from 6.5 (and I do not have access to this db
anymore). Any other suggestions?
John Bell wrote:
> Hi Lisa
> You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> If you need to restore MSDB check out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> John
> "Lisa Hoffman" wrote:
>
>>I've recently installed SQL 2000 on a new server. Migrated production
>>databases and data from old SQL 6.5.
>>Everything checks out OK applications work fine, all data
>>came over no problem. However... when I try to open or create a
>>database maintenance plan I get is error:
>>Microsoft SQL-DMO (ODBC SQLState: 42S22)
>>Error 207: Invalid column name 'category_id'.
>>Invalid column name 'netsend_address'.
>>Invalid column name 'last_netsend_date'.
>>Invalid column name 'last_netsend_time'.
>>these colune names do not exist, do I need to create them and if so,
>>which table do they need to be in? Any help is greatly appreciated. Thanks
>>|||Hi
I would assume that MSDB was backed up after your installation and therefore
it could be resumed to it's previous state? Any jobs etc should be reviewed
and manually re-created.
John
"Lisa Hoffman" wrote:
> The MS article states "The model and msdb databases can only be restored
> from backups created on a Microsoft® SQL Server� 2000 server. Restore of
> backups of these databases made on SQL Server version 7.0 or earlier is
> not supported."
> This was a migration from 6.5 (and I do not have access to this db
> anymore). Any other suggestions?
> John Bell wrote:
> > Hi Lisa
> >
> > You may want to run a DBCC CHECKCATALOG or DBCC CHECKDB on your MSDB database.
> >
> > If you need to restore MSDB check out
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_2w1f.asp
> >
> > John
> >
> > "Lisa Hoffman" wrote:
> >
> >
> >>I've recently installed SQL 2000 on a new server. Migrated production
> >>databases and data from old SQL 6.5.
> >>Everything checks out OK applications work fine, all data
> >>came over no problem. However... when I try to open or create a
> >>database maintenance plan I get is error:
> >>
> >>Microsoft SQL-DMO (ODBC SQLState: 42S22)
> >>Error 207: Invalid column name 'category_id'.
> >>Invalid column name 'netsend_address'.
> >>Invalid column name 'last_netsend_date'.
> >>Invalid column name 'last_netsend_time'.
> >>
> >>these colune names do not exist, do I need to create them and if so,
> >>which table do they need to be in? Any help is greatly appreciated. Thanks
> >>
> >>
> >>
>

Error when loading Package

Hi all,
I've finished an SSIS Package on my computer and want to move the project into production server. I was just copied the whole files and when I load the package from production server there was an error occured, the description is below :

Error 1 Error loading 'SC2DC_Regular.dtsx' : The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails. . e:\dw workplace\sc2dc_server\SC2DC_Regular.dtsx 1 1

What's the problem with my Package, I never met this error before with the same behaviour of moving SSIS project from one computer to another.
Thanks in advance

Is you production server 64-bit? If so, the problem may be that your scripts are not precompiled. Make sure your PreCompileScriptIntoBinaryCode is True (the default). Scripts are compiled when the script editor IDE is closed, so you may need to open and close the scripts (tasks and components) to get them to compile.
|||The property is True and like I wrote before I moved my previous project to that production server and it's work fine. Only this current project I got this error.|||Hi all,
Does anyone know what's the real problem with my package ?|||Hi,
after searching the answer for days I found this thread :

https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1244365&SiteID=1

no wonder there's no people here tried to answered my question ;p except JayH, thanks bro :-)

sql

Error when generating in Excel

I am currently having a problem in production when generating a report in
Excel. I get the following error:
Reporting Services Erro
----
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. (rrRenderingError) Get Online Help
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown.
Excel Rendering Extension : Invalid index in the index path.
----
Microsoft Reporting Services
I would certainly appreciate if any one has a solution to this issue. One
thing I have found on the web is that they talk about Office version.(i.e. we
should have Office 2003 or XP on the reporting services machine & we do have
it in production) This report was working fine in production off recent
without any problems. But now I get this error on generating a report. The
other reports are working fine in terms of generating to excel.
Any inputs is greatly appreciated.
Thanks
MukundI got to view the log files in the Reporting Services directory & found the
following details. May be it will help to find the solution to this problem.
Please let me know if anyone has a solution to this issue.
Mukund
-----aspnet_wp!chunks!998!12/22/2004-15:01:24::
i INFO: ### GetReportChunk('RenderingInfo_EXCEL', Other), chunk was not
found! this=f881b8dc-4271-49a8-aed4-4b1a9f0d1620
aspnet_wp!reportrendering!998!12/22/2004-15:01:24:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown., ;
Info:
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. --> System.Exception: Excel Rendering Extension : Invalid index in
the index path.
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GetReference(ReportItem dataRegion, IntList indexPath, Int32 startIndex)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.CollectHiddenReportItems(IntList indexPath, PageReportItems& pageRI)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreScanPage(ReportItem
parentDataRegion, Boolean isPageNeedsEvaluation, Hashtable& riReferenceTable,
PageLayout& pageLayout, PageReportItems& pageRIItems, Stack&
dynamicLayoutStack, Hashtable& dataRegionsTable, Boolean[]& reduceRowGapList,
OutlineRenderStates[]& verticalOutlineStates, OutlineRenderStates[]&
horizontalOutlineStates)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderStaticPage(StreamWriter
streamWriter, ReportItem parentDataRegion, PageLayout pageLayout, Hashtable
formulaRIMap, Int32 currentPageNumber, PageReportItems& pageRIItems, Boolean&
isPageNeedsHeader, ExcelStyle& footerStyle, Stack& dynamicLayoutStack)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageLayout(PageLayout pageLayout, Int32& currentPageNumber, Stack& stack)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageCollection(PageCollection
pageCollection, Int32& currentPageNumber, Stack& stack, PageLayout&
lastPageLayout)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateWorkSheets()
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateMainSheet()
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderExcelWorkBook(CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.ProcessReport(CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapshot(CreateReportChunk
createChunkCallback, RenderingContext rc, GetResource getResourceCallback)
-- End of inner exception stack trace --
aspnet_wp!webserver!998!12/22/2004-15:01:27:: e ERROR: Reporting Services
error
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. --> System.Exception: Excel Rendering Extension : Invalid index in
the index path.
aspnet_wp!library!9bc!12/22/2004-15:11:13:: i INFO: Cleaned 0 batch records,
0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs
-----
"Mukund" wrote:
> I am currently having a problem in production when generating a report in
> Excel. I get the following error:
> Reporting Services Error
> ----
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown. (rrRenderingError) Get Online Help
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown.
> Excel Rendering Extension : Invalid index in the index path.
> ----
> Microsoft Reporting Services
> I would certainly appreciate if any one has a solution to this issue. One
> thing I have found on the web is that they talk about Office version.(i.e. we
> should have Office 2003 or XP on the reporting services machine & we do have
> it in production) This report was working fine in production off recent
> without any problems. But now I get this error on generating a report. The
> other reports are working fine in terms of generating to excel.
> Any inputs is greatly appreciated.
> Thanks
> Mukund
>|||I am aslo getting the same error. Its works for other reports. Only one report i cant export to excel and html. if any one know the solution pls reply...
From http://www.developmentnow.com/g/115_2004_12_0_0_454135/Error-when-generating-in-Excel.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com