| Author |
Topic |
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-18 : 09:15:09
|
| Hello everyone!I've got a very annoying problem, one that I've yet to figure out. My company has various SQL 2000 servers setup, some for development and some in production. I have tried on all the installed (done by myself, set with "default" instance) to install the available service packs only to get the following, and very annoying message:"Setup was unable to verify the state of the server for an upgrade. Verify the server is able to start and that you provided a valid sa password and restart setup."I'm logged into the system as an admin, supplied the sa password and cannot get past this. I have tried with the SQL Service running as well as shutdown to no avail. I have searched on Google, these forums, Microsofts website, and various other "SQL-related" sites and still cannot find any instances of this happening to anyone else.Please help. I want to update our servers to the latest and greatest to help keep them secure (this of course is assuming that the SP's and Security Fixes are indeed secure).Thanks for any help anyone can supply, it is greatly appreciated.Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-04-18 : 10:00:07
|
| Check the security mode your servers are set to. If they are "Windows NT Only" then the sa account will not be able to login. You'll need to use NT Authentication to apply the patch instead.Jeff BanschbachConsultant, MCDBA |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-18 : 10:05:45
|
| They are all set to mixed mode, these servers are generally used for web based applications. I have also tried using a "trusted connection" login (ie: interactive user) with no luck.Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-04-18 : 11:02:12
|
| If your SQL Server is running in a domain user account, I would guess that this account may not have sufficient permissions to read some registry key. So you could try changing the service account to Localsystem, installing the service pack, and then changing the service account back to your domain user.---------------Strong SQL Developer wanted in the Boston area. Please e-mail if interested. |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-18 : 11:19:20
|
| Thanks for the suggestion but still no-go. Set the service to use LocalSystem and attempted the install, same error. Logged in as the actual NT user that the SQL service uses which is part of the Administrative group and tried to install, same error.One thing I can say is that our IT "guy" sets up all our webservers based on C2 compliance as well as using a checklist from Microsoft. I'm suspecting that one of those settings is causing issues with the patching of SQL Server as this happens on ALL of our SQL 2000 machines, it's not a specific incident.Thanks again!Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-04-18 : 12:04:23
|
| Is there anything of any interest in the sqlsp.log file that the patch should be generating? Should be in the temp directory of the server you are attempting to install on.It seems to be having a problem starting the service, so you'll also want to look in the the server event viewer for any clues as to why the sp can't start the sql server service.Jeff BanschbachConsultant, MCDBAEdited by - efelito on 04/18/2002 12:14:05 |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-04-18 : 13:13:11
|
| Make sure all services are stopped besides:- Alerter- Cluster Service- Computer Browser- Event Log- License Logging Service- Logical Disk Manager- Messenger- Net Logon- NTLM Security Support Provider- Plug and Play- Remote Procedure Call (RPC) Locator- Remote Procedure Call (RPC) Service- Server- Spooler- TCP/IP NetBIOS Helper- Time Service- WorkstationIf it still fails, post your sqlsp.Log-Chad |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-18 : 13:26:53
|
| Here is the sqlsp.log contents. I tried stopping all the services you listed (although some I wasn't able to, not even with a net stop command).13:21:01 Begin Setup13:21:01 Version on Media: 8.00.53413:21:01 Mode = Normal13:21:01 ModeType = NORMAL13:21:01 Begin: SetupInitialize() 13:21:01 End: SetupInitialize()13:21:01 Begin: CheckFixedRequirements()13:21:01 Platform ID: 0xf000000013:21:01 Version: 5.0.219513:21:01 File Version - C:\WINNT\System32\shdocvw.dll: 6.0.2600.013:21:01 End: CheckFixedRequirements()13:21:01 Begin Action: CheckRequirements13:21:01 Processor Architecture: x86 (Pentium)13:21:01 Service Pack: 51213:21:01 ComputerName: EXTRANET113:21:01 User Name: smeissner13:21:01 IsAllAccessAllowed returned: 113:21:01 OS Language: 0x40913:21:01 End Action CheckRequirements13:21:01 CreateSetupTopology(EXTRANET1), Handle : 0x17a40a0, returned : 013:21:01 CreateSetupTopology returned : 0, Handle : 0x17a40a013:21:01 Topology Type : 1, Return Value : 013:21:01 ST_GetPhysicalNode returned : 0, PNHandle : 0x17a40f013:21:01 PN_EnumerateEx returned : 013:21:01 PN_GetSQLStates returned : 0, SqlStates : 0x8800822513:21:01 PN_StartScan [0x17a40f0] returned : 013:21:01 PN_GetNext [0x17a40f0] returned : 0, Handle: [0x17a4690]13:21:01 SQLI_GetPackageId [0x17a4690] returned : 0, PackageId = 0x213:21:01 SQLI_GetVersion [0x17a4690] returned : 0, Version = 8.00.19413:21:01 PN_GetNext [0x17a40f0] returned : 18, Handle: [0x0]13:21:01 ReleaseSetupTopology13:21:01 This combination of Package and Operating System allows a full product install.13:21:01 Begin: SetupInstall()13:21:01 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir ...13:21:01 CommonFilesDir=C:\Program Files\Common Files13:21:01 Windows Directory=C:\WINNT13:21:01 Program Files=C:\Program Files13:21:01 TEMPDIR=C:\DOCUME~1\smeissner\Local Settings\Temp13:21:01 End: SetupInstall()13:21:01 Begin: ShowDialogs()13:21:01 Initial Dialog Mask: 0x8300037, Disable Back=0x113:21:01 Begin Action ShowDialogsHlpr: 0x113:21:01 Begin Action: DialogShowSdWelcome13:21:04 End Action DialogShowSdWelcome13:21:04 Dialog 0x1 returned: 113:21:04 End Action ShowDialogsHlpr13:21:04 ShowDialogsGetDialog returned: nCurrent=0x2,index=113:21:04 Begin Action ShowDialogsHlpr: 0x213:21:04 Begin Action: DialogShowSdMachineName13:21:04 ShowDlgMachine returned: 113:21:04 Name = EXTRANET1, Type = 0x113:21:04 End Action DialogShowSdMachineName13:21:04 begin ShowDialogsUpdateMask13:21:04 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 013:21:04 Updated Dialog Mask: 0xbf00035, Disable Back = 0x113:21:04 Dialog 0x2 returned: 013:21:04 End Action ShowDialogsHlpr13:21:04 ShowDialogsGetDialog returned: nCurrent=0x4,index=213:21:04 Begin Action ShowDialogsHlpr: 0x413:21:04 Begin Action: DialogShowSdInstallMode13:21:04 ShowDlgInstallMode returned: 113:21:04 InstallMode : 0x213:21:04 End Action DialogShowSdInstallMode13:21:04 begin ShowDialogsUpdateMask13:21:04 nFullMask = 0xbf00035, nCurrent = 0x4, nDirection = 113:21:04 Updated Dialog Mask: 0xb000627, Disable Back = 0x113:21:04 Dialog 0x4 returned: 113:21:04 End Action ShowDialogsHlpr13:21:04 ShowDialogsGetDialog returned: nCurrent=0x20,index=513:21:04 Begin Action ShowDialogsHlpr: 0x2013:21:04 Begin Action: DialogShowSdLicense13:21:04 End Action DialogShowSdLicense13:21:04 Dialog 0x20 returned: 113:21:04 End Action ShowDialogsHlpr13:21:04 ShowDialogsGetDialog returned: nCurrent=0x200,index=913:21:04 Begin Action ShowDialogsHlpr: 0x20013:21:04 Begin Action: DialogShowSdInstanceName13:21:04 Begin Action: ShowDlgInstanceName13:21:06 Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion\CSDVersionNumber key not found, no SP installed13:21:06 The language on the CD is 1033 and installed is 103313:21:06 End Action : Verify Language13:21:06 SKU is : Standard Edition13:21:06 End Action: ShowDlgInstanceName13:21:06 ShowDlgInstanceName returned : 013:21:06 InstanceName : MSSQLSERVER13:21:06 End Action DialogShowSdInstanceName13:21:06 begin ShowDialogsUpdateMask13:21:06 nFullMask = 0xb000627, nCurrent = 0x200, nDirection = 013:21:06 Updated Dialog Mask: 0xbc00627, Disable Back = 0x113:21:06 Dialog 0x200 returned: 013:21:06 End Action ShowDialogsHlpr13:21:06 ShowDialogsGetDialog returned: nCurrent=0x400,index=1013:21:06 Begin Action ShowDialogsHlpr: 0x40013:21:06 Begin Action: DialogShowSdMaintain13:21:06 ShowDlgMaintainInstall returned : 113:21:06 Type : 0xc13:21:06 CreateSetupTopology(EXTRANET1), Handle : 0x17a4f98, returned : 013:21:06 CreateSetupTopology returned : 0, Handle : 0x17a4f9813:21:06 Topology Type : 1, Return Value : 013:21:06 ST_GetPhysicalNode returned : 0, PNHandle : 0x17a40f013:21:06 PN_EnumerateEx returned : 013:21:06 PN_GetSQLStates returned : 0, SqlStates : 0x8800822513:21:06 PN_GetInstance for MSSQLSERVER [0x17a40f0] returned : 013:21:06 SQLI_GetPackageId [0x17a4668] returned : 0, PackageId = 0x213:21:06 SQLI_GetVersion [0x17a4668] returned : 0, Version = 8.00.19413:21:06 SQLI_GetSQLStates for MSSQLSERVER [0x17a4668] returned : 0, SQLStates: 0xc0020513:21:06 SQLI_GetInstallPath [0x17a4668] returned : 0, Path = C:\Program Files\Microsoft SQL Server\MSSQL13:21:06 SQLI_GetDataPath [0x17a4668] returned : 0, DataPath = e:\extranet_dbase\MSSQL13:21:06 SQLI_GetVersion [0x17a4668] returned : 0, Version = 8.00.19413:21:06 SQLI_GetRegKeyRoot [0x17a4668] returned : 0, RegKeyRoot = Software\Microsoft\MSSQLServer13:21:06 SQLI_GetPackageName [0x17a4668] returned : 0, szPackage = Standard Edition13:21:06 SQLI_GetPackageId [0x17a4668] returned : 0, PackageId = 0x213:21:06 Previous Install Path: C:\Program Files\Microsoft SQL Server\MSSQL13:21:06 Previous Install Data: e:\extranet_dbase\MSSQL13:21:06 Previous Install Version: 8.00.19413:21:06 ReleaseSetupTopology13:21:06 End Action DialogShowSdMaintain13:21:06 begin ShowDialogsUpdateMask13:21:06 nFullMask = 0xbc00627, nCurrent = 0x400, nDirection = 113:21:06 Updated Dialog Mask: 0xb002627, Disable Back = 0x113:21:06 Dialog 0x400 returned: 113:21:06 End Action ShowDialogsHlpr13:21:06 ShowDialogsGetDialog returned: nCurrent=0x2000,index=1313:21:06 Begin Action ShowDialogsHlpr: 0x200013:21:06 Begin Action: DialogShowSdUpgrade13:21:06 ShowDlgUpgrade returned : 113:21:06 Checking databases on instance 'MSSQLSERVER'13:21:06 Authenticate access13:21:06 Begin SDPassword Dialog13:21:14 End SDPassword Dialog13:21:14 C:\DOCUME~1\smeissner\Local Settings\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-m13:21:25 Process Exit Code: (0) 13:21:25 C:\sql2ksp2\x86\BINN\osql.exe -S EXTRANET1 -n -d master -Q "exit" -U sa -P 13:21:25 Process Exit Code: (0) 13:21:25 Access authenticated13:21:25 C:\sql2ksp2\x86\BINN\osql.exe -S EXTRANET1 -n -b -d master -o C:\DOCUME~1\smeissner\Local Settings\Temp\~sqldb0.txt -i C:\DOCUME~1\smeissner\Local Settings\Temp\SqlSetup\Bin\dbverify.sql -U sa -P 13:21:25 Process Exit Code: (1) 13:21:25 C:\DOCUME~1\smeissner\Local Settings\Temp\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -Service MSSQLSERVER 13:21:40 Process Exit Code: (0) 13:21:40 Cannot open specified file: C:\DOCUME~1\smeissner\Local Settings\Temp\~sqldb0.txt13:21:41 Setup was unable to verify the state of the server for an upgrade. Verify the server is able to start and that you provided a valid sa password and restart setup.13:21:41 End Action DialogShowSdUpgrade13:21:41 End: ShowDialogs()13:21:41 Action CleanUpInstall:13:21:41 Installation Failed.I'm running out of ideas. Any assistance is greatly appreciated.NOTE: This happens on WIN2K Server with SQL Server 2000 Standard installed. I have been successful installing SP2 on a WIN2K Professional system with SQL Server 2000 Personal installed.Thanks again!Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-04-18 : 14:28:03
|
| Haven't had a chance to review your sqlsp.log, but please note that chadmat asked you to stop all services EXCEPT the ones he listed.Jeff BanschbachConsultant, MCDBAEdited by - efelito on 04/18/2002 14:37:21 |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-04-18 : 14:34:22
|
I think the problem is that your temp directory has a space in it. If you look at the following line, you'll notice a file path with a space (the Local Settings directory to be exact) and no quotes around it. Try changing your temp directory to one without spaces, or logging in as the local admin on the box so your temp directory is c:\winnt\temp. quote: 13:21:25 C:\sql2ksp2\x86\BINN\osql.exe -S EXTRANET1 -n -b -d master -o C:\DOCUME~1\smeissner\Local Settings\Temp\~sqldb0.txt -i C:\DOCUME~1\smeissner\Local Settings\Temp\SqlSetup\Bin\dbverify.sql -U sa -P 13:21:25 Process Exit Code: (1)
In order for this command to work it would have to look like this. quote: 13:21:25 C:\sql2ksp2\x86\BINN\osql.exe -S EXTRANET1 -n -b -d master -o "C:\DOCUME~1\smeissner\Local Settings\Temp\~sqldb0.txt" -i "C:\DOCUME~1\smeissner\Local Settings\Temp\SqlSetup\Bin\dbverify.sql" -U sa -P 13:21:25 Process Exit Code: (1)
Jeff BanschbachConsultant, MCDBAEdited by - efelito on 04/18/2002 14:36:29Edited by - efelito on 04/18/2002 15:36:28 |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-18 : 15:43:10
|
| Thanks! My bad, misread it. Oops, I'll give all your suggestions a try. Thanks again for reviewing the log and making suggestions.Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-04-19 : 08:41:49
|
| A big thanks to all that contributed to this. I logged in as the local admin and it worked like a champ. I don't know why this hasn't been raised before though, is it normal protocol to login as the local admin to install SP's for SQL Server? I typically just use my domain login for the machine (I belong to the Admin Group) for everything related to SQL Server. I create an actual "SQLService" User on the machine for SQL Server to use (as instructed by Microsoft).Thanks again!Kyle HeonPixelMEDIA, Inc.Programmer L2kheon@pixelmedia.com |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-04-19 : 11:52:28
|
| This appears to be a bug in the install script. It should really be able to handle spaces in directory and file names by now. I usually log in as the account I've configured SQL Server to startup with. I usually have this account configured as a local admin and it's always had c:\winnt\temp as it's temp directory. Don't know why yours has the local settings one. Could be a roaming profile issue or something nutty like that. Glad everything is working for you now.Jeff BanschbachConsultant, MCDBA |
 |
|
|
pschuller
Starting Member
1 Post |
Posted - 2004-09-14 : 16:06:14
|
| When running sp3 you have to have the correct server listed in the SQL Server, Client Network Utility.If you don't you get errors like Setup was unable to validate your passwordsetup was unable to verify the state of the server for an upgrade.and in the sqlsp.log Error reading: Software\Microsoft\MSSQLServer\Client:SharedMemory On |
 |
|
|
|