ERROR 926 dATABSE msdb CANNOT OPEN

Hi paul
we are using MS SQL Server2000 when we try to take backup we are getting
this Error " Error 926 Data base MSDB cannot Open it has been marked
suspect by recovery"
Please if you solution to solve this problem let us know.
Thanks in advance
S KaliyanSeems your msdb is corrupted. Restore msdb from your mort recent backup(s).
But do investigate why
msdb went corrupt first:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"S Kaliyan" <as_kalyan@.patel-india.com> wrote in message
news:Oqi5ek3MFHA.3788@.tk2msftngp13.phx.gbl...
> Hi paul
> we are using MS SQL Server2000 when we try to take backup we are getting
> this Error " Error 926 Data base MSDB cannot Open it has been marked
> suspect by recovery"
> Please if you solution to solve this problem let us know.
> Thanks in advance
> S Kaliyan
>
>

Error 823 with msdb

When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the followin
g
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should no
t
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msd
b
> is fixed, I am dead in the water (the existing plans still run fine). And
I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens

Error 823 with msdb

When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install?
Any suggestions are greatly appreciated.
Thanks
Russ Stevens
I just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens
|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens
|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>
|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens
|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas

"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens

Error 823 with msdb

When I try to create a new Maintenance Plan or revise an existing one I
get the following error:
Error: 823, Severity: 24, State: 2
Microsoft SQL-DMO (ODBC SQL State:HY000)
Error 823: I/O error (torn page) detected during read at offsett
0x000000000f0000 in file 'd:\sqldata\MSSQL\data\msdbdata.mdf'.
There are no known disk problems that I can detect. The existing
Maintenance Plans run fine. I do not have a backup of msdb prior to when
this problem started (I have no idea of when it started, it only appears
when I try to modify the maintenance plan).
I can easily recreate the maintenance plans but I need to fix the problem
with msdb first. Can msdb be repaired, can I empty it to start fresh, can I
use the msdb from an original install'
Any suggestions are greatly appreciated.
Thanks
Russ StevensI just tried to repair msdb
DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
It fixed 6 errors - I now have a bigger mess <g> - am getting the following
error (and other strange errors) when I try to modify a Maintenance Plan;
Error 170: Line 1: Incorrect syntax near ','.
I need a clean working msdb - appreciate any help.
Thanks
Russ Stevens|||Anytime you run a dbcc checkdb with repair_allow_data_loss you risk data
integrity. there is no way to know what kind of data is lost etc. In
your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.
Alternatively you can always restore from backup :)
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> I just tried to repair msdb
> DBCC CHECKDB ('msdb', REPAIR_ALLOW_DATA_LOSS)
> It fixed 6 errors - I now have a bigger mess <g> - am getting the following
> error (and other strange errors) when I try to modify a Maintenance Plan;
> Error 170: Line 1: Incorrect syntax near ','.
> I need a clean working msdb - appreciate any help.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
<<In your case, you have to recreate the maintenance plan, which should not
be a big issue. In fact if that is the only problem that you get after
the repair, you should be happy.>>
No - I am not happy <g> - I couldn't create a maintenance plan before the
repair or after the repair. I can't add a plan or revise a plan. Until msdb
is fixed, I am dead in the water (the existing plans still run fine). And I
can't restore from an msdb backup as I evidently don't have one that was
made before the problem started (I only keep a few weeks).
Looks like I need to rebuild the master and start over. It just seems that
MS should have a way of rebuilding just msdb without having to rebuild the
master.
Thanks
Russ Stevens|||There is a way to rebuild msdb from scratch. May not be a supported one.
Try this on a test server before doing this on a production server
Start SQL Server from the command prompt recover just the master
database, such as sqlservr.exe -c -f -T3608 -T4022
you can then connect to sql server from query analzyer (-f means yo
uwill only get single connection), then you can delete MSDB database.
There is a script in mssql\install folder called instmsdb.sql. This is
the script to recreate MSDB database.
I have to warn you this is probably not a supported solution by
Microsoft. I am not responsible for any damage :) But if you are
thinking of rebuilding master database anyway, why not give this a try?
the idea is test it thoroughly and make sure it test in your development
server.
Yih-Yoon Lee
My blog http://www.mssql-tools.com/blog
E-mail: yihyoon.online@.gmail.com
/* remove .online to send me e-mail */
Russell Stevens wrote:
> Yih-Yoon,
> <<In your case, you have to recreate the maintenance plan, which should not
> be a big issue. In fact if that is the only problem that you get after
> the repair, you should be happy.>>
> No - I am not happy <g> - I couldn't create a maintenance plan before the
> repair or after the repair. I can't add a plan or revise a plan. Until msdb
> is fixed, I am dead in the water (the existing plans still run fine). And I
> can't restore from an msdb backup as I evidently don't have one that was
> made before the problem started (I only keep a few weeks).
> Looks like I need to rebuild the master and start over. It just seems that
> MS should have a way of rebuilding just msdb without having to rebuild the
> master.
> Thanks
> Russ Stevens
>|||Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevens|||A rebuild of Master will recreate the structure and base data, but not
repopulate existing data. I would have tried the other solution first.
Drop and rerun the instmsdb.sql script. Then the risk was limited to just
msdb, which contains far less useful information than master.
Also, a good installation recommendation is to always set a responsible
backup strategy for your system databases. School of hard knocks works, but
it is an expensive lesson.
Sincerely,
Anthony Thomas
"Russell Stevens" <rastevens@.aol.com> wrote in message
news:%23tlm6PWAFHA.3504@.TK2MSFTNGP12.phx.gbl...
Yih-Yoon,
I suspect the instmsdb.sql script is also used by the rebuildm.exe
utility. I didn't want to chance it. I rebuilt everything, am back on line
(after an all nighter).
Needless to say I was quite amazed that after rebuilding, my sa password
had been set to a blank - no message, no warning, I was just open to the
world. How can Microsoft miss something like that?
Thanks for your help.
Russ Stevenssql

Error 5173

I had to do a restore of my msdb. Before I did, I
detached all of my databases. The restore went fine, and
I was able to re-attach all of my databases, except for
one of them. When I try to attach it, I get an error that
says "Error 5173: Cannot associate files with different
databases." The ldf files are on a differend drive than
the mdf file, but they were like that before I detached
them. Nothing has changed on this database. How do I get
this DB attached?
Thanks.
Hi
At a guess you have either got the wrong file names are missing files or
they are in the wrong order!
You may also want to check the permissions on the files and directories.
If that fails you may want to try sp_attach_single_file_db and only specify
the data file (make sure you keep a copy of the original files)
John
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
> I had to do a restore of my msdb. Before I did, I
> detached all of my databases. The restore went fine, and
> I was able to re-attach all of my databases, except for
> one of them. When I try to attach it, I get an error that
> says "Error 5173: Cannot associate files with different
> databases." The ldf files are on a differend drive than
> the mdf file, but they were like that before I detached
> them. Nothing has changed on this database. How do I get
> this DB attached?
> Thanks.
|||I've double and triple checked the file names and they are
correct. All permissions look correct. It's only
one .mdf and one .ldf that need to attach.
If I run "sp_attach_single_file_db", will that create a
new log file? If so, is there a way for me to point the
log file somewhere else. I have to keep the log file on a
seperate drive due to disk space (60GB log file).
Thanks again.

>--Original Message--
>Hi
>At a guess you have either got the wrong file names are
missing files or
>they are in the wrong order!
>You may also want to check the permissions on the files
and directories.
>If that fails you may want to try
sp_attach_single_file_db and only specify
>the data file (make sure you keep a copy of the original
files)
>John
>"Ken" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
and[vbcol=seagreen]
that[vbcol=seagreen]
get
>
>.
>
|||Hi
I would make sure that you keep safe copies of all the files!
I would then try to re-attach them in the original locations, if that works
then detach them again and move the files.
Alternatively if you backed up the database before trying this, you could
restore the backup using the MOVE option. See Books online about the RESTORE
command.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:1f1a301c457b6$0dbf1ef0$a301280a@.phx.gbl...[vbcol=seagreen]
> I've double and triple checked the file names and they are
> correct. All permissions look correct. It's only
> one .mdf and one .ldf that need to attach.
> If I run "sp_attach_single_file_db", will that create a
> new log file? If so, is there a way for me to point the
> log file somewhere else. I have to keep the log file on a
> seperate drive due to disk space (60GB log file).
> Thanks again.
>
> missing files or
> and directories.
> sp_attach_single_file_db and only specify
> files)
> message
> and
> that
> get

Error 5173

I had to do a restore of my msdb. Before I did, I
detached all of my databases. The restore went fine, and
I was able to re-attach all of my databases, except for
one of them. When I try to attach it, I get an error that
says "Error 5173: Cannot associate files with different
databases." The ldf files are on a differend drive than
the mdf file, but they were like that before I detached
them. Nothing has changed on this database. How do I get
this DB attached?
Thanks.Hi
At a guess you have either got the wrong file names are missing files or
they are in the wrong order!
You may also want to check the permissions on the files and directories.
If that fails you may want to try sp_attach_single_file_db and only specify
the data file (make sure you keep a copy of the original files)
John
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:1f03501c457ae$c2d08cf0$a601280a@.phx
.gbl...
> I had to do a restore of my msdb. Before I did, I
> detached all of my databases. The restore went fine, and
> I was able to re-attach all of my databases, except for
> one of them. When I try to attach it, I get an error that
> says "Error 5173: Cannot associate files with different
> databases." The ldf files are on a differend drive than
> the mdf file, but they were like that before I detached
> them. Nothing has changed on this database. How do I get
> this DB attached?
> Thanks.|||I've double and triple checked the file names and they are
correct. All permissions look correct. It's only
one .mdf and one .ldf that need to attach.
If I run "sp_attach_single_file_db", will that create a
new log file? If so, is there a way for me to point the
log file somewhere else. I have to keep the log file on a
seperate drive due to disk space (60GB log file).
Thanks again.

>--Original Message--
>Hi
>At a guess you have either got the wrong file names are
missing files or
>they are in the wrong order!
>You may also want to check the permissions on the files
and directories.
>If that fails you may want to try
sp_attach_single_file_db and only specify
>the data file (make sure you keep a copy of the original
files)
>John
>"Ken" <anonymous@.discussions.microsoft.com> wrote in
message
> news:1f03501c457ae$c2d08cf0$a601280a@.phx
.gbl...
and[vbcol=seagreen]
that[vbcol=seagreen]
get[vbcol=seagreen]
>
>.
>|||Hi
I would make sure that you keep safe copies of all the files!
I would then try to re-attach them in the original locations, if that works
then detach them again and move the files.
Alternatively if you backed up the database before trying this, you could
restore the backup using the MOVE option. See Books online about the RESTORE
command.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:1f1a301c457b6$0dbf1ef0$a301280a@.phx
.gbl...[vbcol=seagreen]
> I've double and triple checked the file names and they are
> correct. All permissions look correct. It's only
> one .mdf and one .ldf that need to attach.
> If I run "sp_attach_single_file_db", will that create a
> new log file? If so, is there a way for me to point the
> log file somewhere else. I have to keep the log file on a
> seperate drive due to disk space (60GB log file).
> Thanks again.
>
> missing files or
> and directories.
> sp_attach_single_file_db and only specify
> files)
> message
> and
> that
> get

Error 5173

I had to do a restore of my msdb. Before I did, I
detached all of my databases. The restore went fine, and
I was able to re-attach all of my databases, except for
one of them. When I try to attach it, I get an error that
says "Error 5173: Cannot associate files with different
databases." The ldf files are on a differend drive than
the mdf file, but they were like that before I detached
them. Nothing has changed on this database. How do I get
this DB attached?
Thanks.Hi
At a guess you have either got the wrong file names are missing files or
they are in the wrong order!
You may also want to check the permissions on the files and directories.
If that fails you may want to try sp_attach_single_file_db and only specify
the data file (make sure you keep a copy of the original files)
John
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
> I had to do a restore of my msdb. Before I did, I
> detached all of my databases. The restore went fine, and
> I was able to re-attach all of my databases, except for
> one of them. When I try to attach it, I get an error that
> says "Error 5173: Cannot associate files with different
> databases." The ldf files are on a differend drive than
> the mdf file, but they were like that before I detached
> them. Nothing has changed on this database. How do I get
> this DB attached?
> Thanks.|||I've double and triple checked the file names and they are
correct. All permissions look correct. It's only
one .mdf and one .ldf that need to attach.
If I run "sp_attach_single_file_db", will that create a
new log file? If so, is there a way for me to point the
log file somewhere else. I have to keep the log file on a
seperate drive due to disk space (60GB log file).
Thanks again.
>--Original Message--
>Hi
>At a guess you have either got the wrong file names are
missing files or
>they are in the wrong order!
>You may also want to check the permissions on the files
and directories.
>If that fails you may want to try
sp_attach_single_file_db and only specify
>the data file (make sure you keep a copy of the original
files)
>John
>"Ken" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
>> I had to do a restore of my msdb. Before I did, I
>> detached all of my databases. The restore went fine,
and
>> I was able to re-attach all of my databases, except for
>> one of them. When I try to attach it, I get an error
that
>> says "Error 5173: Cannot associate files with different
>> databases." The ldf files are on a differend drive than
>> the mdf file, but they were like that before I detached
>> them. Nothing has changed on this database. How do I
get
>> this DB attached?
>> Thanks.
>
>.
>|||Hi
I would make sure that you keep safe copies of all the files!
I would then try to re-attach them in the original locations, if that works
then detach them again and move the files.
Alternatively if you backed up the database before trying this, you could
restore the backup using the MOVE option. See Books online about the RESTORE
command.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:1f1a301c457b6$0dbf1ef0$a301280a@.phx.gbl...
> I've double and triple checked the file names and they are
> correct. All permissions look correct. It's only
> one .mdf and one .ldf that need to attach.
> If I run "sp_attach_single_file_db", will that create a
> new log file? If so, is there a way for me to point the
> log file somewhere else. I have to keep the log file on a
> seperate drive due to disk space (60GB log file).
> Thanks again.
>
> >--Original Message--
> >Hi
> >
> >At a guess you have either got the wrong file names are
> missing files or
> >they are in the wrong order!
> >You may also want to check the permissions on the files
> and directories.
> >
> >If that fails you may want to try
> sp_attach_single_file_db and only specify
> >the data file (make sure you keep a copy of the original
> files)
> >
> >John
> >
> >"Ken" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
> >> I had to do a restore of my msdb. Before I did, I
> >> detached all of my databases. The restore went fine,
> and
> >> I was able to re-attach all of my databases, except for
> >> one of them. When I try to attach it, I get an error
> that
> >> says "Error 5173: Cannot associate files with different
> >> databases." The ldf files are on a differend drive than
> >> the mdf file, but they were like that before I detached
> >> them. Nothing has changed on this database. How do I
> get
> >> this DB attached?
> >>
> >> Thanks.
> >
> >
> >.
> >

Error 208: Invaild object name msdb.dbo.MSdistpublishers

Recently my msdb database became corrupt so I had to reinstall SQL Server 7.0. In doing so new system databases were created. I was able to restore all databases and system databases from backups except for the msdb database (unfortunately my backup overwrote the good database before I realized there was a problem). Because of this I have lost publication and subscriber info from my distribution tables that resided in the old msdb database.

What I would like to do is delete all references to previous publications and subscribers and create them all over again. But it does not allow me to create new or delete old publishers or subscribers. I get this and other errors...

Error 208: Invaild object name 'msdb.dbo.MSdistpublishers'

There is in fact no MSdistpublishers table in msdb because it is a new db. Can anyone help me reverse out of this?

Thanks in advance.

SteveIn future make sure to have regular backups for SYSTEM databases too.

I suggest to delete the replication and recreate it freshly which will re-enable the task. Make sure to check all jobs and tasks are scheduled properly after the MSDB restore.

Refer to SQL error log for any information.