I work on a SQL 2000 Standard server that is part of our SBS package. Two days ago we ran a set of MS updates on the server and the residual symptom is that DTS packages, the Import or Export wizard all will not run. The Sql Server Agent service runs under the local system account, however that was true prior to the updates.
The error when attempting to run an import is that the OLEDB connection object is not available. The error occurs when trying to use the Access driver or a DSN. Further investigation indicates that msdb could not be contacted.
Does anyone have an idea as to what might cause this and a workaround?
Thanks,
misdeanI would perform an integrity check (DBCC CHECKDB) of the MSDE database, to se if it is corrupt. It might be because it's late night here, but that's the only reason I could think of now.|||I will give it a try. Somehow, I believe is is related to the MS updates applied the other day. I will run DBCC on it in the AM and post the results.
Thanks,
Keith
Showing posts with label ran. Show all posts
Showing posts with label ran. Show all posts
Wednesday, March 7, 2012
Monday, February 20, 2012
msdb is Suspect
Is am running SQL 2000 SP3 on a Win 2000 box.
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...
My msdb is marked suspet. I ran sp_resetstatus and restarted SQL and
the dB is still suspect.
I found an article that recommends...
One approach would be to drop & recreate the msdb databases (see
instmsdb.sql and instserv.sql in the c:\mssql\install directory of your
sqlserver install). You would lose backup/restore histories, all
operators, scheduled tasks, etc. but would get it back up and running.
Is this the only solution? Is there a way to do this without loosing
my backup history?
TIA,
Larry...
Paul,
You are the man!!! This did the trick.
As always, thanks for your help!!!!
Larry...
Subscribe to:
Posts (Atom)