| 
	
 | 
 Posted by Nicolas Noakes on 01/19/06 08:08 
Hello, 
 
I posted this 2005-01-16 in microsoft.public.sqlserver.setup, but have 
had no replies yet... 
 
 
We are running SBS 2003 Standard Edition with SP1, and WSUS (Windows 
Server Update Services).  All was well until I tried to install the 
folloing update, which failed: 
 
Update for SQL Server 2000 Desktop Engine (SharePoint) on Windows Server 
2003 (KB909544) 
 
I now cannot start the MSSQL$SHAREPOINT service - it starts and 
immediately stops again. 
 
I cannot find the update file for KB909544 on the Microsoft Download 
Centre website, and obviously it cannot be reinstalled via WSUS of the 
Windows Update website because it is identified as already installed. 
 
It does not seem that the database for KB909544 vesion of MSDE will be 
able to be read by previous versions (refer to the kb article), and I 
see a error about the master database having an "invalid schema" in the 
sql log file.  I therefore suspect that the database has been upgraded, 
but not the MSDE engine.  Refer to the verbatim info below (sorry about 
linewrapping, I'm posting from devdex.com) 
 
Does anyone have any suggestions?  Thanks in advance for your 
assistance. 
 
Regards, 
Nicolas 
 
 
System Event Log for the failed update: 
--------------------------------------- 
 
Event Type:	Error 
Event Source:	Windows Update Agent 
Event Category:	Installation  
Event ID:	20 
Date:		2005/12/30 
Time:		14:34:26 
User:		N/A 
Computer:	SERVER1 
Description: 
Installation Failure: Windows failed to install the following update 
with error 0x800706be: Update for SQL Server 2000 Desktop Engine 
(SharePoint) on Windows Server 2003 (KB909544). 
 
For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp. 
Data: 
0000: 57 69 6e 33 32 48 52 65   Win32HRe 
0008: 73 75 6c 74 3d 30 78 38   sult=0x8 
0010: 30 30 37 30 36 62 65 20   00706be  
0018: 55 70 64 61 74 65 49 44   UpdateID 
0020: 3d 7b 30 46 33 30 32 41   ={0F302A 
0028: 42 38 2d 43 39 33 45 2d   B8-C93E- 
0030: 35 36 46 35 2d 43 35 36   56F5-C56 
0038: 31 2d 33 33 37 31 38 30   1-337180 
0040: 35 39 30 43 46 37 7d 20   590CF7}  
0048: 52 65 76 69 73 69 6f 6e   Revision 
0050: 4e 75 6d 62 65 72 3d 31   Number=1 
0058: 30 30 20 00               00 .  
 
 
The SQL log file looks like this: 
--------------------------------- 
 
2006-01-16 14:21:58.31 server    Microsoft SQL Server  2000 - 8.00.2039 
(Intel X86)  
	Oct  4 2005 16:05:38  
	Copyright (c) 1988-2003 Microsoft Corporation 
	Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1) 
 
2006-01-16 14:21:58.31 server    Copyright (C) 1988-2002 Microsoft 
Corporation. 
2006-01-16 14:21:58.31 server    All rights reserved. 
2006-01-16 14:21:58.31 server    Server Process ID is 5480. 
2006-01-16 14:21:58.31 server    Logging SQL Server messages in file 
'c:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'. 
2006-01-16 14:21:58.32 server    SQL Server is starting at priority 
class 'normal'(2 CPUs detected). 
2006-01-16 14:21:58.35 server    SQL Server configured for thread mode 
processing. 
2006-01-16 14:21:58.35 server    Using dynamic lock allocation. [500] 
Lock Blocks, [1000] Lock Owner Blocks. 
2006-01-16 14:21:58.39 spid4     Starting up database 'master'. 
2006-01-16 14:21:58.48 spid4     0 transactions rolled back in database 
'master' (1). 
2006-01-16 14:21:58.48 spid4     Recovery is checkpointing database 
'master' (1) 
2006-01-16 14:21:58.51 server    Using 'SSNETLIB.DLL' version 
'8.0.2039'. 
2006-01-16 14:21:58.51 spid5     Starting up database 'model'. 
2006-01-16 14:21:58.51 server    SQL server listening on Shared Memory. 
2006-01-16 14:21:58.51 server    SQL Server is ready for client 
connections 
2006-01-16 14:21:58.53 spid4     Server name is 'SERVER1\SHAREPOINT'. 
2006-01-16 14:21:58.53 spid4     Skipping startup of clean database id 4 
2006-01-16 14:21:58.53 spid4     Skipping startup of clean database id 6 
2006-01-16 14:21:58.53 spid4     Starting up database 'STS_Config'. 
2006-01-16 14:21:58.57 spid5     Clearing tempdb database. 
2006-01-16 14:21:58.75 spid5     Starting up database 'tempdb'. 
2006-01-16 14:21:58.87 spid4     Recovery complete. 
2006-01-16 14:21:58.96 spid4     Database 'master' has invalid schema. 
 
*** Sent via Developersdex http://www.developersdex.com ***
 
  
Navigation:
[Reply to this message] 
 |