Re: Can't Install SP4 for SQL 2000 / Win2k3

Looks like your msdb database has been marked as suspect.
You need to fix this problem before you can go ahead with the service pack
installation.

Try this
1. use sp_resetstatus to reset the status of msdb.
2. stop and start sql server service
3. if the msdb database again becomes suspect, look at the most recen
errorlog, it will give you a clue to why msdb is being set to suspect.
hth
--
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:X_NFe.692$6%2.494@xxxxxxxxxxx
> Vikram,
>
> Thanks for helping out.
>
> The contents were shown in the original post:
>
> "And the C:\temp\1\sqlsp.out shows:
>
> Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery.
> See the SQL Server errorlog for more information."
>
> This message exists both before and after the uninstall and reinstallation
> of SQL 2000.
>
> "Vikram Vamshi" <vikram.vamshi@xxxxxxxxxxxxxxxxxxx> wrote in message
> news:udkuoEskFHA.2852@xxxxxxxxxxxxxxxxxxxxxxx
>> Can you post the contents of c:\temp\1\sqlsp.out?
>> That should give us a clue to what went wrong
>>
>> --
>> Vikram Vamshi
>> Database Engineer
>> Eclipsys Corporation
>> "hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:p6NFe.677$6%2.601@xxxxxxxxxxx
>>>I am attempting to update SQL 2000 Server (RTM) to SP4 on Windows 2003
>>>Server Standard w/ SP1
>>>
>>> After extracting SQL2000-KB884525-SP4-x86-ENU.EXE to C:\SQL2KSP4 and
>>> running setup.bat, the installation hangs at "Validating User. Please
>>> Wait" but then ceases (the install window disappears) with no
>>> errors/dialogue boxes.
>>>
>>> After reading up on this I changed the TEMP and TMP environmental
>>> variables so they have no spaces in them.
>>>
>>> The end of my sqlsp.log shows:
>>>
>>> 10:36:39 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:EMEXTSRV -n -d master -o
>>> "c:\temp\1\sqlsp.out" -Q"Exit(declare @ret int if (select count(*) from
>>> msdb.dbo.systargetservers) = 0 Set @ret=0 else Set @ret=403 Select
>>> )" -E
>>> 10:36:39 Process Exit Code: (-100)
>>> 10:36:39 Error : While detecting required SP3 warnings.
>>> 10:36:39 End Action DialogShowSdUpgrade
>>> 10:36:39 End: ShowDialogs()
>>> 10:36:39 Action CleanUpInstall:
>>> 10:36:39 Installation Failed.
>>>
>>> And the C:\temp\1\sqlsp.out shows:
>>>
>>> Database 'msdb' cannot be opened. It has been marked SUSPECT by
>>> recovery. See the SQL Server errorlog for more information.
>>>
>>> Since the database is not in production and since I have minimal SQL2000
>>> admin experience, I uninstalled SQL 2000 and deleted the C:\Program
>>> Files\SQL Server directory, rebooted, and reinstalled SQL 2000.
>>>
>>> Despite my efforts, the SP4 installation still fails in an identical
>>> fashion as prior to my reinstallation of SQL 2000.
>>>
>>> I have also tried installing SP3 and get the same errors.
>>>
>>> I can't seem to find any relevant solutions in the MSKB or in
>>> dejanews.Com on this.
>>>
>>> Can anybody help this lost soul?
>>>
>>> TIA!
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: SQL 2005 - forcing a database to go suspect
    ... in order to finally arrive with a suspect database. ... SQL Server has increasingly over time considered this a "soft" suspect ... I stopped SQL Services and tried renaming log files, data files. ...
    (microsoft.public.sqlserver.server)
  • Re: Can I restore msdb from another sqlserver s backup
    ... Tibor Karaszi, SQL Server MVP ... "Karin W" wrote in message ... > We have the same problem with a suspected MSDB. ... > droped because it'a a system database. ...
    (microsoft.public.sqlserver.server)
  • Re: Coping everything to New Server
    ... Are these brought in with the master or msdb database? ... Sames thing with the Backup devices under ... > original sql server. ...
    (microsoft.public.sqlserver.setup)
  • Re: Host Operating System Disaster
    ... The system MSDB database was what I was sweating ... One thing to try is to reinstall SQL Server to the same ... location they were at originally before the drives went out. ... explicitly detach the database first using sp_detach_db. ...
    (microsoft.public.sqlserver.setup)
  • Re: MSDB (Subspect)
    ... I have one more suggestion to this issue, I feel that during the MSDB mdf ... and LDF physical file copy (cold Backup), they would have started the SQL ... Stop & Start the SQL Server ... > Probably because the database was damaged when you took the backup. ...
    (microsoft.public.sqlserver.server)