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
Showing posts with label couple. Show all posts
Showing posts with label couple. Show all posts
Thursday, March 22, 2012
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?
>
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?
>
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: -2147467259 (80004005); Provider Error: 0 (0)
Hi,
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL ServerI think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL ServerI think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
Error: -2147467259 (80004005); Provider Error: 0 (0)
Hi,
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server
I think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
I have a couple of DTS job that runs daily. However, for the past three days
a different job has failed every night with very similar looking error
messages that are listed below. When I re-run the job after it fails it runs
fine and completes successfully. Any information to resolve this will be
highly appreciated.
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionRead (recv()).]General network error.
Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 11 (B)
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
network error. Check your network documentation.
Error source: Microsoft OLE DB Provider for SQL Server
Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server
I think there used to be an issue like this due to something related to
connection pooling, and IIRC the workaround was to disable connection
pooling. Not sure if this is the same issue tho.
Did you try doing a search on support.microsoft.com?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
|||Have see dozens of these, and almost everytime it was hardware or
connectivity driver related...not SQL Server
Stress test the network with NetMon running. Sorry I can't help on the
Netmon side. The stress test can be as simple as copying a HUGE file from
point A to point B.
I've seen corrupt/mismatched drivers, bad router ports and even crimped
cables cause this.
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:21211FD0-C372-436A-9A53-FB5F0B631447@.microsoft.com...
> Hi,
> I have a couple of DTS job that runs daily. However, for the past three
> days
> a different job has failed every night with very similar looking error
> messages that are listed below. When I re-run the job after it fails it
> runs
> fine and completes successfully. Any information to resolve this will be
> highly appreciated.
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionRead (recv()).]General network
> error.
> Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 11 (B)
> Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General
> network error. Check your network documentation.
> Error source: Microsoft OLE DB Provider for SQL Server
>
> Error: -2147467259 (80004005); Provider Error: 0 (0)
> Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server
>
>
>
Monday, March 19, 2012
Error: 17805, Severity: 20, State: 3 Invalid buffer received from client.
Howdy Folks,
Our site has been experiencing this issue for a couple of months now.. Hopefully someone else can assist, as Ive got to a point where I think issue lies within the application or a Microsoft bug. Web searches have reveled a number installations that have also had this error but its has not revealed an actual fix.
I understand this error code basically means data being returned to the client is getting either corrupted or the data is too large to fit into the buffer on the client side. Client in our case is the terminal server, here after called a application server
As the user base has increased form 5 to 20, I have noticed that the issue is occurring more frequently in comparison to when the company first started using the application /database. Its just about daily now...
The db server also has 8 other db's residing on it - but they are all less than 300 meg.
The attached PowerPoint doc has the trace info & the surrounding code for each process that has suffered a buffer error over a period of a week.
DB Server Environment: Win2000 SP4, SQL2000 SP3a, MDAC 2.7 SP1 refresh.
Application Environment: Written In house in VB.NET Framework 1.1 setup as a published app on a terminal server running windows 2000 SP4
Common features of the issue, that have been omitted from trace output for visibility reasons are:
- Involves 1 particular DB (thats accessed by VB app) & its developement db
- All connections are coming from 1 application server
- Issue does not relate to any particular site connecting to the application server using this application
I have reviewed & fixed several potential server side causes but this error still is occuring with in the environment:
MDAC versions must be common on application & server:
- Removed from equation by updating MDAC version on App server to be the same as DB Server: 2.7 SP1 Refresh
Network related
- Considered unlikely; we are also not experiencing network card errors on either server; also all db's would be experiencing connectivity errors.
Which leaves us with Application related options to review:
- Compilation error of application
- App parameter definitions to stored procedures are the correct data type
- Ensure values being passed do not exceed 4000 characters as that has also been known to create this error message
- I've asked the developer to review MS KB 827366 article, as it may be a valid test
- In regard to MSKB 832977 - I am not using pssdiag & have a later version of the MS Analyzer. But what I thought was interesting, is the statement that this problem occurs more frequently when an application submits a large remote procedure call (RPC) input buffer, especially when the RPC input buffer is greater than or equal to 8 KB. However, this problem may occur even if the input buffer is less than 4 KB
- A is using datatypes varchar & char - not nvarchar & nhar
Any assistance with this issue would be appreicated as server performance is being effected - these processes hang around for 1 - 5 mins before terminating (refer duration times in the powerpoint traces)
Thanks In advance
Suze.I think Reads column referrs to physical reads. If that's the case then the number is pretty high and may be the reason for the client timeout. Sporadic behavior of the same query may be caused by inconsistent execution plan generated. Do you use dynamic SQL a lot?|||Thank you for your question...
The number of reads appears only on the first slide, the other 7 don't have any reads - just the really long duration.
Because of this long duration & the audit logout entry for the same process id directly after the buffer error, I've assumed that the process is timing out. But in saying that users are not reporting that they have been kicked out of the application or receiving any error messages - so maybe way off in that assumption.
We are using SP's passing in parameter's. The developer reckons this means its not being built at runtime. As you might be able to tell, I'm a newbie - so I don't know if this means they are dynamic sql or not... are you able to advise.
Best Regards|||The 4000-limit was revealed in my previous environment when SP3 was applied. The FE code was...of course, JAVA, what else can cause this. And they were parsing the call to the stored procedure without TYPEing the parameters, which resulted in every character-based parameter to be interpreted as NVARCHAR. Now, the article (827366) is also referring to the possibility of data type size misalignment, where the value supplied may be outside of the boundaries allowed for a specific data type (just a hunch).|||I like the sound of your hunch. Unfortunately I can't provide the developer any proof - being a newbie in all. Anyway, I think I've done the next best thing by sending the developer the MSKB article 827366 again & Ant profiler to use so he can see what his code is doing - hopefully this will give him the visibility he needs.
Thanks again & Best Regards
Suze.
Our site has been experiencing this issue for a couple of months now.. Hopefully someone else can assist, as Ive got to a point where I think issue lies within the application or a Microsoft bug. Web searches have reveled a number installations that have also had this error but its has not revealed an actual fix.
I understand this error code basically means data being returned to the client is getting either corrupted or the data is too large to fit into the buffer on the client side. Client in our case is the terminal server, here after called a application server
As the user base has increased form 5 to 20, I have noticed that the issue is occurring more frequently in comparison to when the company first started using the application /database. Its just about daily now...
The db server also has 8 other db's residing on it - but they are all less than 300 meg.
The attached PowerPoint doc has the trace info & the surrounding code for each process that has suffered a buffer error over a period of a week.
DB Server Environment: Win2000 SP4, SQL2000 SP3a, MDAC 2.7 SP1 refresh.
Application Environment: Written In house in VB.NET Framework 1.1 setup as a published app on a terminal server running windows 2000 SP4
Common features of the issue, that have been omitted from trace output for visibility reasons are:
- Involves 1 particular DB (thats accessed by VB app) & its developement db
- All connections are coming from 1 application server
- Issue does not relate to any particular site connecting to the application server using this application
I have reviewed & fixed several potential server side causes but this error still is occuring with in the environment:
MDAC versions must be common on application & server:
- Removed from equation by updating MDAC version on App server to be the same as DB Server: 2.7 SP1 Refresh
Network related
- Considered unlikely; we are also not experiencing network card errors on either server; also all db's would be experiencing connectivity errors.
Which leaves us with Application related options to review:
- Compilation error of application
- App parameter definitions to stored procedures are the correct data type
- Ensure values being passed do not exceed 4000 characters as that has also been known to create this error message
- I've asked the developer to review MS KB 827366 article, as it may be a valid test
- In regard to MSKB 832977 - I am not using pssdiag & have a later version of the MS Analyzer. But what I thought was interesting, is the statement that this problem occurs more frequently when an application submits a large remote procedure call (RPC) input buffer, especially when the RPC input buffer is greater than or equal to 8 KB. However, this problem may occur even if the input buffer is less than 4 KB
- A is using datatypes varchar & char - not nvarchar & nhar
Any assistance with this issue would be appreicated as server performance is being effected - these processes hang around for 1 - 5 mins before terminating (refer duration times in the powerpoint traces)
Thanks In advance
Suze.I think Reads column referrs to physical reads. If that's the case then the number is pretty high and may be the reason for the client timeout. Sporadic behavior of the same query may be caused by inconsistent execution plan generated. Do you use dynamic SQL a lot?|||Thank you for your question...
The number of reads appears only on the first slide, the other 7 don't have any reads - just the really long duration.
Because of this long duration & the audit logout entry for the same process id directly after the buffer error, I've assumed that the process is timing out. But in saying that users are not reporting that they have been kicked out of the application or receiving any error messages - so maybe way off in that assumption.
We are using SP's passing in parameter's. The developer reckons this means its not being built at runtime. As you might be able to tell, I'm a newbie - so I don't know if this means they are dynamic sql or not... are you able to advise.
Best Regards|||The 4000-limit was revealed in my previous environment when SP3 was applied. The FE code was...of course, JAVA, what else can cause this. And they were parsing the call to the stored procedure without TYPEing the parameters, which resulted in every character-based parameter to be interpreted as NVARCHAR. Now, the article (827366) is also referring to the possibility of data type size misalignment, where the value supplied may be outside of the boundaries allowed for a specific data type (just a hunch).|||I like the sound of your hunch. Unfortunately I can't provide the developer any proof - being a newbie in all. Anyway, I think I've done the next best thing by sending the developer the MSKB article 827366 again & Ant profiler to use so he can see what his code is doing - hopefully this will give him the visibility he needs.
Thanks again & Best Regards
Suze.
Subscribe to:
Posts (Atom)