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

Problem resolved.

My CD had a bad copy of msdbdata.mdf on my installation CDs!
This explains why a reinstall did not fix the errors.

Thanks to the Microsoft engineer who helped me discover this when i called
to obtain the
hotfix mentioned previously in this thread.

I simply shut down SQL Server, copied msdbdata.mdf from the installation CD,
restarted SQL,
ran 'sp_resetstatus msdb' from query analyzer, then stop/restarted SQL. This
resolved the msdb issue.
After the msdb issue was resolved, SP4 installed nicely!

Thanks for attempting to help me, Vikram!

"hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:R4QHe.10307$6%2.1229@xxxxxxxxxxx
> Looks like I have one of those Microsoft logic problems....
>
> Article ID:328354
> "SYMPTOMS When you run a RESTORE DATABASE WITH RECOVERY statement to bring
> a standby server online, you might receive one of the following error
> messages:
>
> Error: 9003
> The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
>
> Error: 9004
> An error occurred while processing the log for database '%.*ls'.
>
> CAUSE
> This problem occurs because physical characteristics (virtual log parity)
> for inactive virtual log files in the transaction log are not preserved
> when a full database backup is restored.
>
> RESOLUTION
> To resolve this problem, obtain the latest service pack for Microsoft SQL
> Server 2000.
>
> DANG! Isn't that what I am trying to do in the first place? Maybe I will
> try to find the hotfix and apply that alone.
>
>
> "hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:W%OHe.9150$_R1.515@xxxxxxxxxxx
> Upon running 'sp_resetstatus msdb' I see:
>
> "Prior to updating sysdatabases entry for database 'msdb', mode = 0 and
> status = 1073742104 (status suspect_bit = 256).
> For row in sysdatabases for database 'msdb', the status bit 256 was forced
> off and mode was forced to 0.
> Warning: You must recover this database prior to access."
>
> Then, I start and stop the SQL service, like you said. The event logs
> show:
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Error: 9003, Severity: 20, State: 6
> The LSN (88:289:1) passed to log scan in database 'msdb' is invalid.
>
> and then it shows:
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
>
> Error: 3414, Severity: 21, State: 1
> Database 'msdb' (database ID 4) could not recover. Contact Technical
> Support.
>
> and then it shows:
>
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
>
> 17052 :
> Recovery complete.
>
> I then try again to reinstall SP4 but I get the same error as earlier in
> the sqlsp.out file:
>
> "Database 'msdb' cannot be opened. It has been marked SUSPECT by
> recovery. See the SQL Server errorlog for more information."
>
> It seems a little odd that a complete uninstall and reinstall of the
> product nets the same "suspect" msdb...
>
>
> "Vikram Vamshi" <vikram.vamshi@xxxxxxxxxxxxxxxxxxx> wrote in message
> news:e0dlR4qlFHA.2852@xxxxxxxxxxxxxxxxxxxxxxx
>> It should, but the way things go you can never rely on that fact :)
>>
>> --
>> Vikram Vamshi
>> Database Engineer
>> Eclipsys Corporation
>> "hamm3r" <hammer@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:TzWGe.13774$Kx6.1958@xxxxxxxxxxx
>>> Thanks for the tips. I'll try this on Monday.
>>>
>>> Another (simple?) question to throw out there though...
>>>
>>> Shouldn't unstalling and reinstalling SQL2000 result in a pristine msdb
>>> database?
>>>
>>>
>>> "Vikram Vamshi" <vikram.vamshi@xxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:OyuLk3IlFHA.3256@xxxxxxxxxxxxxxxxxxxxxxx
>>>> 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
>>>>>>> elect )" -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: Unable to get global configuration data.
    ... "SharinDenver" wrote: ... how to resolve the default website. ... on the web server. ... Unable to connect to database. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: test just reinstalled my OS
    ... I never reformat a drive with valuable data on it, ... >> backup it's database file, reinstall it, and then add the database again. ... > LOL ...
    (comp.graphics.apps.lightwave)
  • Re: WSUS and WSS 3.0 broken
    ... I'd read the documentation first, and then if you don't find specific guidance, I would uninstall both, then reinstall companyweb, then reinstall WSUS. ... you might be able to get those database files back from shadow ...
    (microsoft.public.windows.server.sbs)
  • Re: User Rights Assignment - not available
    ... To resolve this issue, first run the Esentutl.exe tool to examine the ... and WinDir is the folder where Windows XP ... This operation may find that this database is corrupt ... Initiating INTEGRITY mode... ...
    (microsoft.public.windowsxp.security_admin)
  • Re: WSUS and WSS 3.0 broken
    ... You might want to look at the WSUS release notes - I'm pretty sure ... Add/Remove, then reinstall? ... SBS monitoring & reporting now works as does WSS 2.0. ... you might be able to get those database files ...
    (microsoft.public.windows.server.sbs)