Error: Backup Log terminating abnormally

hi
i am using sql server 2000. when i try to backup log file it throws out the following error and hence the second command that is dbcc shrinkfile never gets executed. if i restart sql server and re-run these commands ... no error pops up ... both the comma
nds get completed sccessfully and log file gets shrunk too.
these are the commands that i run
BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
this is the error that i get
Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
I am quite sure that no other command is active at the time when i issue these commands, still i get error. any help will be appreciated.
regards
yashrah.
Hi
Can you check your SQL Error log for the message when this command failed,
also can you please provide the SQL Server 2000 Service pack level.
you can get the Service pack level by running select @.@.version from query
analyzer.
Also, do you have replication set up, if yes, what kind of replication?
3023 means, It thinks there is some concurrent database operation going on
that is blocking the ALTER DATABASE, because it is unable to acquire the
database lock.
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in message
news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
> hi
> i am using sql server 2000. when i try to backup log file it throws out
> the following error and hence the second command that is dbcc shrinkfile
> never gets executed. if i restart sql server and re-run these commands ...
> no error pops up ... both the commands get completed sccessfully and log
> file gets shrunk too.
> these are the commands that i run
> BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
> DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
> this is the error that i get
> Server: Msg 3023, Level 16, State 3, Line 1
> Backup and file manipulation operations (such as ALTER DATABASE ADD FILE)
> on a database must be serialized. Reissue the statement after the current
> backup or file manipulation operation is completed.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
> I am quite sure that no other command is active at the time when i issue
> these commands, still i get error. any help will be appreciated.
> regards
> yashrah.
|||thanx for ur concern...
SQL Error Log says
2004-07-22 02:40:23.10 backup BACKUP failed to complete the command exec shrink_bamprimaryimport_logfile
infact "shrink_bamprimaryimport_logfile" is my stored procedure that contains the two commands (backup log and dbcc shrinkfile) written below.
servie pack 3a is installed and no replication set up is there.
"Sadeesh[MSFT]" wrote:

> Hi
> Can you check your SQL Error log for the message when this command failed,
> also can you please provide the SQL Server 2000 Service pack level.
> you can get the Service pack level by running select @.@.version from query
> analyzer.
> Also, do you have replication set up, if yes, what kind of replication?
> 3023 means, It thinks there is some concurrent database operation going on
> that is blocking the ALTER DATABASE, because it is unable to acquire the
> database lock.
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in message
> news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
>
>

Error: Backup Log terminating abnormally

hi
i am using sql server 2000. when i try to backup log file it throws out the
following error and hence the second command that is dbcc shrinkfile never g
ets executed. if i restart sql server and re-run these commands ... no error
pops up ... both the comma
nds get completed sccessfully and log file gets shrunk too.
these are the commands that i run
BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
this is the error that i get
Server: Msg 3023, Level 16, State 3, Line 1
Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on
a database must be serialized. Reissue the statement after the current back
up or file manipulation operation is completed.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
I am quite sure that no other command is active at the time when i issue the
se commands, still i get error. any help will be appreciated.
regards
yashrah.Hi
Can you check your SQL Error log for the message when this command failed,
also can you please provide the SQL Server 2000 Service pack level.
you can get the Service pack level by running select @.@.version from query
analyzer.
Also, do you have replication set up, if yes, what kind of replication?
3023 means, It thinks there is some concurrent database operation going on
that is blocking the ALTER DATABASE, because it is unable to acquire the
database lock.
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in mess
age
news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
> hi
> i am using sql server 2000. when i try to backup log file it throws out
> the following error and hence the second command that is dbcc shrinkfile
> never gets executed. if i restart sql server and re-run these commands ...
> no error pops up ... both the commands get completed sccessfully and log
> file gets shrunk too.
> these are the commands that i run
> BACKUP LOG BAMPrimaryImport WITH TRUNCATE_ONLY
> DBCC SHRINKFILE ( BAMPrimaryImport_log, 500 )
> this is the error that i get
> Server: Msg 3023, Level 16, State 3, Line 1
> Backup and file manipulation operations (such as ALTER DATABASE ADD FILE)
> on a database must be serialized. Reissue the statement after the current
> backup or file manipulation operation is completed.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
> I am quite sure that no other command is active at the time when i issue
> these commands, still i get error. any help will be appreciated.
> regards
> yashrah.|||thanx for ur concern...
SQL Error Log says
2004-07-22 02:40:23.10 backup BACKUP failed to complete the command exec
shrink_bamprimaryimport_logfile
infact "shrink_bamprimaryimport_logfile" is my stored procedure that contain
s the two commands (backup log and dbcc shrinkfile) written below.
servie pack 3a is installed and no replication set up is there.
"Sadeesh[MSFT]" wrote:

> Hi
> Can you check your SQL Error log for the message when this command failed,
> also can you please provide the SQL Server 2000 Service pack level.
> you can get the Service pack level by running select @.@.version from query
> analyzer.
> Also, do you have replication set up, if yes, what kind of replication?
> 3023 means, It thinks there is some concurrent database operation going on
> that is blocking the ALTER DATABASE, because it is unable to acquire the
> database lock.
> Regards
> Sadeesh
> --
> This posting is provided AS IS with no warranties, and confers no rights.
> "Yashrah [Xavor]" <YashrahXavor@.discussions.microsoft.com> wrote in me
ssage
> news:73E811CE-FCBF-4D29-9538-6D22F842A8EC@.microsoft.com...
>
>sql

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
Jeff
Some anti-virus software perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>
|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.
|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g2000hsg.go oglegroups.com...
>
>
It might be possible but why always the same database each time?
|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>
|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:[vbcol=seagreen]
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegro ups.com...
>
>
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?
|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to exclude them... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegr oups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>
sql

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroup
s.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g20
00hsg.googlegroups.com...
>
>
>
>
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:[vbcol=seagreen]
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>
>
>
>
>
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to ex
clude them... :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

Error: 5105 on MSDB database

Every couple of weeks it appears that my MSDB database is getting
corrupt. Here is my situation.
Everyday at 4 am I take a backup off all the instances, then at 5 am
the computer reboots. Once the computer is up all the instances try to
start up except MSDB will have a problem. When I log into Enterprise
Manager the instance is listed as Suspect. I have to restore the
database from the backup taken at 4 am and everything is fine.
Here is the error from the log file the last time it happened.
2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
error. The physical file name 'C:\Program Files\Microsoft SQL Server
\MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
But I have also received this error:
2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
process cannot access the file because it is being used by another
process.) during the creation/opening of physical device C:\Program
Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
for virtual device number (VDN) 1.
I have no idea what this other process would be.
Any ideas?
Thanks,
JeffSome anti-virus software perhaps?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 1:31 pm, "jeffchi...@.gmail.com" <jeffchi...@.gmail.com>
wrote:
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
> Any ideas?
> Thanks,
> Jeff
I actually get both of the errors each time, one is from the sql
agent. I am new to sql server.
Thanks.|||On May 14, 1:41 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Some anti-virus software perhaps?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <jeffchi...@.gmail.com> wrote in messagenews:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It might be possible but why always the same database each time?|||Try excluding msdb from the backup and see if you get the same error
post-reboot. Also if you skip the reboot, does sql continue indefinitely
without a problem?
Someone mentioned antivirus. Not sure that would cause your particular
issue, but you do have the AV set to exclude .mdf and .ldf file types,
right?
--
TheSQLGuru
President
Indicium Resources, Inc.
<jeffchirco@.gmail.com> wrote in message
news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> Every couple of weeks it appears that my MSDB database is getting
> corrupt. Here is my situation.
> Everyday at 4 am I take a backup off all the instances, then at 5 am
> the computer reboots. Once the computer is up all the instances try to
> start up except MSDB will have a problem. When I log into Enterprise
> Manager the instance is listed as Suspect. I have to restore the
> database from the backup taken at 4 am and everything is fine.
> Here is the error from the log file the last time it happened.
> 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> error. The physical file name 'C:\Program Files\Microsoft SQL Server
> \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> But I have also received this error:
> 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> process cannot access the file because it is being used by another
> process.) during the creation/opening of physical device C:\Program
> Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> for virtual device number (VDN) 1.
> I have no idea what this other process would be.
>
> Any ideas?
> Thanks,
> Jeff
>|||On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
> Try excluding msdb from the backup and see if you get the same error
> post-reboot. Also if you skip the reboot, does sql continue indefinitely
> without a problem?
> Someone mentioned antivirus. Not sure that would cause your particular
> issue, but you do have the AV set to exclude .mdf and .ldf file types,
> right?
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> <jeffchi...@.gmail.com> wrote in message
> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
> > Every couple of weeks it appears that my MSDB database is getting
> > corrupt. Here is my situation.
> > Everyday at 4 am I take a backup off all the instances, then at 5 am
> > the computer reboots. Once the computer is up all the instances try to
> > start up except MSDB will have a problem. When I log into Enterprise
> > Manager the instance is listed as Suspect. I have to restore the
> > database from the backup taken at 4 am and everything is fine.
> > Here is the error from the log file the last time it happened.
> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
> > But I have also received this error:
> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
> > process cannot access the file because it is being used by another
> > process.) during the creation/opening of physical device C:\Program
> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
> > for virtual device number (VDN) 1.
> > I have no idea what this other process would be.
> > Any ideas?
> > Thanks,
> > Jeff
It's hard cause it doesn't happen every day. But yes it does appear
there if we skip the reboot then the problem goes away. But for some
reason this computer requires a reboot. A very small sql database is
on it.
No mdf and ldf files are not excluded from the antivirus. They should
be?|||> No mdf and ldf files are not excluded from the antivirus. They should
> be?
Well, unless you appreciate the exact type of error you have, you want to exclude them... :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<jeffchirco@.gmail.com> wrote in message
news:1179241236.636144.163400@.u30g2000hsc.googlegroups.com...
> On May 14, 6:32 pm, "TheSQLGuru" <kgbo...@.earthlink.net> wrote:
>> Try excluding msdb from the backup and see if you get the same error
>> post-reboot. Also if you skip the reboot, does sql continue indefinitely
>> without a problem?
>> Someone mentioned antivirus. Not sure that would cause your particular
>> issue, but you do have the AV set to exclude .mdf and .ldf file types,
>> right?
>> --
>> TheSQLGuru
>> President
>> Indicium Resources, Inc.
>> <jeffchi...@.gmail.com> wrote in message
>> news:1179174709.370501.139320@.h2g2000hsg.googlegroups.com...
>> > Every couple of weeks it appears that my MSDB database is getting
>> > corrupt. Here is my situation.
>> > Everyday at 4 am I take a backup off all the instances, then at 5 am
>> > the computer reboots. Once the computer is up all the instances try to
>> > start up except MSDB will have a problem. When I log into Enterprise
>> > Manager the instance is listed as Suspect. I have to restore the
>> > database from the backup taken at 4 am and everything is fine.
>> > Here is the error from the log file the last time it happened.
>> > 2007-05-14 04:53:38 - ! [298] SQLServer Error: 5105, Device activation
>> > error. The physical file name 'C:\Program Files\Microsoft SQL Server
>> > \MSSQL\Data\MSDBData.mdf' may be incorrect. [SQLSTATE 42000]
>> > But I have also received this error:
>> > 2007-04-15 05:13:33.81 spid58 udopen: Operating system error 32(The
>> > process cannot access the file because it is being used by another
>> > process.) during the creation/opening of physical device C:\Program
>> > Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf.
>> > 2007-04-15 05:13:33.89 spid58 FCB::Open failed: Could not open
>> > device C:\Program Files\Microsoft SQL Server\MSSQL\Data\MSDBData.mdf
>> > for virtual device number (VDN) 1.
>> > I have no idea what this other process would be.
>> > Any ideas?
>> > Thanks,
>> > Jeff
> It's hard cause it doesn't happen every day. But yes it does appear
> there if we skip the reboot then the problem goes away. But for some
> reason this computer requires a reboot. A very small sql database is
> on it.
> No mdf and ldf files are not excluded from the antivirus. They should
> be?
>

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?
There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&l...om+sq l+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
[url]http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883[/u
rl]
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>sql

Error: 17883, Severity: 1, State: 0 during DB backup

I receive this error only when backing up database "a". I have changed times
of day and ran it manually and it occurrs only on this one. THere are 15
other databases on the server. We are running SQL 2000 sp4 on Windows 2003
Dell server raid 5, 2 GB of ram. No external disks.
Any ideas?There are a lot of possibilities. See here:
http://www.google.com/search?hl=en&lr=&q=site%3Asupport.microsoft.com+sql+17883
Andrew J. Kelly SQL MVP
"Stacey" <Stacey@.discussions.microsoft.com> wrote in message
news:3E0F3A50-8A68-4859-AAE1-5C937A03EB36@.microsoft.com...
>I receive this error only when backing up database "a". I have changed
>times
> of day and ran it manually and it occurrs only on this one. THere are 15
> other databases on the server. We are running SQL 2000 sp4 on Windows 2003
> Dell server raid 5, 2 GB of ram. No external disks.
> Any ideas?
>

Error while taking the backup

Error while taking the backup....
I used the following command
backup database test to disk = 'e:\bktest05172005'
"e:" is basically a map drive.
Error :
Windows - Delayed Write Failed
Windows was unable to save all the data for the file
\Device\LanmanRedirector\nSys0120\share\bktest0517 2005. The data has been
lost. This error may be caused by a failure of your computer hardware or
network connection. Please try to save this file elsewhere.
OK
Any idea ?
Thanks
Hi
Do not use mapped drives. Only use UNC paths.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Joh" <joh@.mailcity.com> wrote in message
news:uwslpuwWFHA.2128@.TK2MSFTNGP14.phx.gbl...
> Error while taking the backup....
> I used the following command
> backup database test to disk = 'e:\bktest05172005'
> "e:" is basically a map drive.
> Error :
> --
> Windows - Delayed Write Failed
> --
> Windows was unable to save all the data for the file
> \Device\LanmanRedirector\nSys0120\share\bktest0517 2005. The data has been
> lost. This error may be caused by a failure of your computer hardware or
> network connection. Please try to save this file elsewhere.
> --
> OK
> --
> Any idea ?
> Thanks
>
>
|||There is a way to use mapped drives, but its not recommended, even not from
me ;-)
If the Agent uses a mapped drive to backup the database on it, a logon
script has to be defined for that service account mapping the drive for it.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Joh" <joh@.mailcity.com> schrieb im Newsbeitrag
news:uwslpuwWFHA.2128@.TK2MSFTNGP14.phx.gbl...
> Error while taking the backup....
> I used the following command
> backup database test to disk = 'e:\bktest05172005'
> "e:" is basically a map drive.
> Error :
> --
> Windows - Delayed Write Failed
> --
> Windows was unable to save all the data for the file
> \Device\LanmanRedirector\nSys0120\share\bktest0517 2005. The data has been
> lost. This error may be caused by a failure of your computer hardware or
> network connection. Please try to save this file elsewhere.
> --
> OK
> --
> Any idea ?
> Thanks
>
>

Error while taking BackUp of a database in SQL Express 2005

I installed MSDE2000 initially, and later upgraded to SQL Express 2005.

Then I created a database"CGQA00032" in SQL Express 2005.

On taking the BackUp of the database using T-SQL command:

BACKUP DATABASE CGQA00032 to disk = 'CGQA00032.bak'

I got the following Message when I run this query in Managemant Studio :

<<<<<<<<<<<<<<<<<<<<<<<<<<<

Processed 672 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Data' on file 4.
Processed 1 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Log' on file 4.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror_count'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'recovery_model'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_bulk_logged_data'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_snapshot'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_single_user'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_backup_checksums'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_damaged'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'begins_log_chain'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_incomplete_metadata'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_force_offline'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_copy_only'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'first_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'last_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'fork_point_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'database_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'family_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 3009, Level 16, State 1, Line 1

Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.

BACKUP DATABASE successfully processed 673 pages in 2.141 seconds (2.575 MB/sec).
2

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

1. What is the problem with msdb database?

2. Is it a problem of upgrading through a previous version of SQL Server?

3. Is there any Service Pack available to overcome such problem?

Please help ASAP.

Best Regards,

Vishal Gawai

Moving to Engine forum|||

It seems that when you upgrade MSDE to SQL Server Express 2005 RTM the msdb database is not upgraded.

See: http://support.microsoft.com/kb/914781/en-us

The columns you are seeing complained about are columns added to the backup* tables in msdb in SQL Server 2005.

Apparently this was addressed in SP1 so you need to apply either SQL Server Express SP1 or SQL Server Express SP2 to your SQL Server Express installation.

|||

Thank you for ur help.

I would like to know one more thing:

When I tried the above problem on French version of SQL Server 2005 Express Ed.

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

Is this because of the above reason as explained?

Becasue this error does not occur on English version of SQL Server 2005 Express.

Regards,

Vishal

|||

vishalg wrote:

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

This is a confusion where the word error is used for any messages. If you look at the severity of the message you will see that it is 10. This means that it is an informational message and not an error at all.

As for why you don't see the error in the French version.

Checking at the download site. The English edition of SQL Server 2005 Express Edition was released 7 November 2005. The French edition was released 25 January 2006. They probably included available critical fixes in the release (ahead of SP1) and this problem was probably both picked up quite quickly after release, and relatively easy to address (as the update code for msdb was available just not enabled/included).

Error while taking BackUp of a database in SQL Express 2005

I installed MSDE2000 initially, and later upgraded to SQL Express 2005.

Then I created a database"CGQA00032" in SQL Express 2005.

On taking the BackUp of the database using T-SQL command:

BACKUP DATABASE CGQA00032 to disk = 'CGQA00032.bak'

I got the following Message when I run this query in Managemant Studio :

<<<<<<<<<<<<<<<<<<<<<<<<<<<

Processed 672 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Data' on file 4.
Processed 1 pages for database 'iwdm_CGQA00032_V4', file 'iWDM_CGQA00032_V4_Log' on file 4.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror_count'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'mirror'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_password_protected'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'recovery_model'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_bulk_logged_data'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_snapshot'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_single_user'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_backup_checksums'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_damaged'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'begins_log_chain'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'has_incomplete_metadata'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_force_offline'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_copy_only'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'first_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'last_recovery_fork_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'fork_point_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'database_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'family_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'state_desc'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'create_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'drop_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'file_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_only_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'read_write_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_lsn'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'differential_base_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'backup_size'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'filegroup_guid'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_readonly'.
Msg 207, Level 16, State 1, Line 1
Invalid column name 'is_present'.
Msg 3009, Level 16, State 1, Line 1

Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.

BACKUP DATABASE successfully processed 673 pages in 2.141 seconds (2.575 MB/sec).
2

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

1. What is the problem with msdb database?

2. Is it a problem of upgrading through a previous version of SQL Server?

3. Is there any Service Pack available to overcome such problem?

Please help ASAP.

Best Regards,

Vishal Gawai

Moving to Engine forum|||

It seems that when you upgrade MSDE to SQL Server Express 2005 RTM the msdb database is not upgraded.

See: http://support.microsoft.com/kb/914781/en-us

The columns you are seeing complained about are columns added to the backup* tables in msdb in SQL Server 2005.

Apparently this was addressed in SP1 so you need to apply either SQL Server Express SP1 or SQL Server Express SP2 to your SQL Server Express installation.

|||

Thank you for ur help.

I would like to know one more thing:

When I tried the above problem on French version of SQL Server 2005 Express Ed.

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

Is this because of the above reason as explained?

Becasue this error does not occur on English version of SQL Server 2005 Express.

Regards,

Vishal

|||

vishalg wrote:

I recieved SQL server native error 4035 . (Message :: Processed 672 pages for database........)

This is a confusion where the word error is used for any messages. If you look at the severity of the message you will see that it is 10. This means that it is an informational message and not an error at all.

As for why you don't see the error in the French version.

Checking at the download site. The English edition of SQL Server 2005 Express Edition was released 7 November 2005. The French edition was released 25 January 2006. They probably included available critical fixes in the release (ahead of SP1) and this problem was probably both picked up quite quickly after release, and relatively easy to address (as the update code for msdb was available just not enabled/included).

Error while restoring SQL7 data on SQL Express 2005

Hi,

I have backup of data from SQL Server 7.0 and now when i'm trying to restore it into SQL Express 2005, I'm getting following error......

--
Msg 3154, Level 16, State 2, Line 1
The backup set holds a backup of a database other than the existing 'GOSLDW' database.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
--

Here is SQL i'm using to restore database,

RESTORE DATABASE GOSLDW
FROM DISK = 'C:\sqlserverData\GOSLDW'
WITH MOVE 'GOSLDW' TO 'C:\sqlserverData\GOSLDW.mdf',
MOVE 'GOSLDW' TO 'C:\sqlserverData\GOSLDW.ldf'
GO

Why i'm getting this error? Am i missing anything here?

Thanks in advance for your HELP.

- R

There is already a database existing with this name, you either have to drop the database first or replace it with the WITH REPLACE option, see BOL for more details.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||

Thanks for you reply...

After droping database and runing same query again I got message back that database is restore successfully but I don't see any database created.

How i can see this restored database?

I'm new in this SQLServer world..... Thanks for your help.

-R

|||

When you say you can't see it where are you looking? If this is the treeview in SSMS then try right clicking on the databases node and select refresh. If yuo still can not see it then try executing the following query

select * from sys.databases

|||

I guess you are just connected to the wrong instance, use the following command while connected to the *assumed* right instance to see wheter the database appears in the list: SELECT * FROM sys.databases If not the instance does not hold the database you want to use and you restore the database on another system than the wanted :-|

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks now its working fine. I had to stop server and restart to see all database.

Thanks for you help,

R

|||You should not have to do that, a simple refresh of the node should allow you to see them all.

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".|||Where is this option located?
I'm using SQL Express|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me

Thanks for the pointer.|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".|||Where is this option located?
I'm using SQL Express|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me

Thanks for the pointer.|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".|||Where is this option located?
I'm using SQL Express|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me

Thanks for the pointer.|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".
|||Where is this option located?
I'm using SQL Express
|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me
Thanks for the pointer.
|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".
|||Where is this option located?
I'm using SQL Express
|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me
Thanks for the pointer.
|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database,

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".|||Where is this option located?
I'm using SQL Express|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me

Thanks for the pointer.|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring database

Hi,
Im trying to restore a database, when i try to restore by selecting the file groups option it gives me an error Microsoft SQL DMO The backup set holds a backup of a database other than the existing database. RESTORE DATABASE terminated abnormally.
I tried deleting all the tables and the stored procedures that are there, but it still gives the same error.I got this message, too.

In the Options tab, check "Force Restore over existing database".|||Where is this option located?
I'm using SQL Express|||

Tell me. why do I need to check the option "Override the existing database"?

Thanks for the answer

|||If you check "Force Restore over existing database", it must works.|||In Express, click Options on the left and check the field called 'Overwrite the Existing Database'. Also, you may need to change the mdf and log file names to your new database.|||

I had a similar problem, but I was trying to restore the ".bak" file from my laptop to my pc. I had copied the file my pc My Documents folder and tried to restore from SQL Management Express, kept getting the same error. Eventually i tried placing the file in the original backup location it was created but this time on the pc i.e. "C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\Backup" then it worked. Not sure what's the reason for this but just thought I’d share since I know someone else is probably bursting their heads over the same issue..

|||Setting the "Overwrite existing database" fix the problem for me

Thanks for the pointer.|||

I was getting the following error and ur solution worked fine here, Thx a lot!

"The backup set holds a backup of a database other than the existing database."

Error while restoring a database.HELP!

Hello,

I am taking the error message which is in the below side,while restoring a database.(I am using sql server 2005)

The backup set holds a backup of a database other than the existing 'db1' database. (db1 is the database name.)

Can you help me?

This error indicate the database being restored is not the same database backuped in the backup set. This is possible even when the database name is the same. You can take a look at this error description:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_reslsyserr_2_7mk4.asp