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 everyday. Show all posts
Showing posts with label everyday. 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?
>
Sunday, March 11, 2012
Error: %1 is not a valid Win32 application
Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/defaul...kb;en-us;320873 and
http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/defaul...kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/defaul...kb;en-us;320873 and
> http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/defaul...kb;en-us;320873 and
http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/defaul...kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/defaul...kb;en-us;320873 and
> http://support.microsoft.com/defaul...b;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuración del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribió en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> > Hi,
> >
> > This morning I tried to start my MSDE instance like I do everyday.
> > But, sadly, an error message raised, telling me that '%1 is not a
> > valid Win32 application'.
> >
> > At this point, as I didn't have anything important at this instance, I
> > removed the program through the control panel, and reinstalled it.
> > But, when it was finishing, it raised another error: "The installer
> > could not configure the server. Read the server's and installer's
> > error registry for more information".
> please have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuración del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribió en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> > Hi,
> >
> > This morning I tried to start my MSDE instance like I do everyday.
> > But, sadly, an error message raised, telling me that '%1 is not a
> > valid Win32 application'.
> >
> > At this point, as I didn't have anything important at this instance, I
> > removed the program through the control panel, and reinstalled it.
> > But, when it was finishing, it raised another error: "The installer
> > could not configure the server. Read the server's and installer's
> > error registry for more information".
> please have a look at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320873 and
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Error: %1 is not a valid Win32 application
Hi,
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
This morning I tried to start my MSDE instance like I do everyday. But,
sadly, an error message raised, telling me that '%1 is not a valid Win32
application'.
At this point, as I didn't have anything important at this instance, I
removed the program through the control panel, and reinstalled it. But, when
it was finishing, it raised another error: "The installer could not
configure the server. Read the server's and installer's error registry for
more information".
Searching the directory, I found the cnfgsrv.out:
Iniciando servicio ... (Initiating service...)
Modern_Spanish_CI_AS
-m -Q -T4022 -T3659
Error al intentar iniciar el servicio (193) (Error trying to initiate the
service)
Error de configuracin del servidor SQL Server. (Configuration error of the
SQL Server)
Well, after that, I removed everything related to SQL Server, the Management
Console, the SQL Agent, everything. Deleted all the files, searched the
registry, deleting everything.
Then I reinstalled the MSDE instance again, getting the same error.
Then, I tried to install the SQL Server, but the installer told me that "The
SQL Server 2000 Standard Edition component is not compatible with this
operating system. Only the client components will be available".
My operating system is Windows 2000 Professional.
How can I reinstall SQL Server?
Thanks!!
Arnau.
hi Arnau,
Arnau Font wrote:
> Hi,
> This morning I tried to start my MSDE instance like I do everyday.
> But, sadly, an error message raised, telling me that '%1 is not a
> valid Win32 application'.
> At this point, as I didn't have anything important at this instance, I
> removed the program through the control panel, and reinstalled it.
> But, when it was finishing, it raised another error: "The installer
> could not configure the server. Read the server's and installer's
> error registry for more information".
please have a look at
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991 for 2 pieces
of information about properly manually unistall MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
I found an useful article at microsoft:
http://support.microsoft.com/default...b;en-us;812486
I had a hidden file at Program Files named 'Microsoft' that didn't allow the
MSDE service to run!
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:3ss810FpikjbU1@.individual.net...
> hi Arnau,
> Arnau Font wrote:
> please have a look at
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991 for 2
pieces
> of information about properly manually unistall MSDE...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Subscribe to:
Posts (Atom)