SQL Server Performance

[SOLVED] Installation issues on Win2k SP4

Discussion in 'General DBA Questions' started by thorne, Aug 24, 2004.

  1. thorne New Member

    Hi, <br /><br />Sorry if this has already been asked. I will search the forums after posting this, but it is an urgent matter which I must resolve as soon as possible, hence the post.<br /><br />While attempting to install MS SQL Server 2000 Enterprise on Windows 2000 (SP4,) the installation constantly fails, while it attempts to start the service during the installation process.<br /><br />The error message is something vague, stating the service could not be started, and to check the log file (sqlstp.log).<br /><br />All I can see in the log file are named pipes issues. Any help would be appreciated.<br /><br />Log File Contents:<br /><blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><br />10:56:11 C:program FilesMicrosoft SQL Server80ToolsBinncnfgsvr.exe -F "C:WINNTsqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 65792 -U sa -P <br />###############################################################################<br /><br />Starting Service ...<br />SQL_Latin1_General_CP1_CI_AS<br />-m -Q -T4022 -T3659<br /><br />Connecting to Server ...<br />driver={sql server};server=QA-MANDB-01;UID=sa<img src='/community/emoticons/emotion-4.gif' alt=';P' />WD=;database=master<br /><br />[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.<br />[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (GetOverLappedResult()).<br />driver={sql server};server=QA-MANDB-01;UID=sa<img src='/community/emoticons/emotion-4.gif' alt=';P' />WD=;database=master<br />[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.<br />[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (GetOverLappedResult()).<br />driver={sql server};server=QA-MANDB-01;UID=sa<img src='/community/emoticons/emotion-4.gif' alt=';P' />WD=;database=master<br />[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection broken.<br />[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionRead (GetOverLappedResult()).<br /><br /><b>SQL Server configuration failed.</b><br /><br />###############################################################################<br /><br />10:56:36 Process Exit Code: (-1) <br />10:56:47 Setup failed to configure the server. Refer to the server error logs and C:WINNTsqlstp.log for more information.<br />10:56:47 Action CleanUpInstall:<br />10:56:47 C:WINNTTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT<br />10:56:47 Process Exit Code: (1060) The specified service does not exist as an installed service.<br /><br />10:56:47 C:WINNTTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service MSSQLSERVER<br />10:56:47 Process Exit Code: (0) <br />10:56:47 StatsGenerate returned: 2<br />10:56:47 StatsGenerate (0x0,0x1,0xf00,0x400,1033,303,0x0,0x1,0,0,0<br />10:56:47 StatsGenerate -1,Terminator)<br /><b>10:56:47 Installation Failed.</b><br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br />I found this in another thread, but it did not resolve the installation issue.<br /><blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><br />Stop the following services [before installing]:<br />IIS - Internet Information Server <br />Exchange Server <br />SNA Server <br />Disk Keeper <br />SNMP Service <br />Anti-virus software (such as McAfee) <br />Backup products (such as ARC Server)<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote">
  2. derrickleggett New Member

    So, it's actually installing SQL Server but can't start the service??? That's what it looks like. Go to Control Panel/Administrative Tools/Services . See if the MSSQLSERVER and SQLServerAgent services are running. If they are, let's work on it from there. It sounds like an authentication issue, which shouldn't be that big of a deal to fix.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  3. thorne New Member

    Hi,<br /><br />The installation actually fails (note the log output.) No MSSql services are listed in the services applet. Also, there is a warning in the event viewer from when it attempts to start MS SQL Server during the installation.<br /><br />Event Viewer Warning:<br /><blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><br />Event Type:Warning<br />Event Source:MSSQLServer<br />Event Category:(<img src='/community/emoticons/emotion-11.gif' alt='8)' /><br />Event ID:19011<br />Date:8/24/2004<br />Time:4:16:53 PM<br />User:N/A<br />Computer:QA-MANDB-01<br />Description:<br />The description for Event ID ( 19011 ) in Source ( MSSQLServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: (SpnRegister) : Error 1355.<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br />Thanks!
  4. derrickleggett New Member

    Sweet. Look in your registry and see if you have these keys.

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServer

    If you do, you have a few options:

    1. Delete them and restart the installation process. (I don't recommend this one.)
    2. Reinstall your OS and start over. (I do recommend this one if you're cheap.)
    3. Call MS Support and do whatever they tell you to do. (I definitely recommend this one. It's $250.00 per incident.)

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  5. satya Moderator

    This is one of the critical parts of Kerberos and SQL Server interaction. With SQL Server, you can run the SQL Server service under one of the following: a LocalSystem account, a local user account from another computer, or a domain user account.

    When the computer that is running SQL Server starts, it tries to register its own SPN in Active Directory by using the DsWriteAccountSpn API call. If the call is not successful, the following warning is logged in Event Viewer:

    Source: MSSQLServer EventID: 19011 Description: SuperSocket info: (SpnRegister)
    http://support.microsoft.com/?id=811889 - How to troubleshoot the "Cannot generate SSPI context" error message.

    HTH

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  6. thorne New Member

    <blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by derrickleggett</i><br />1. Delete them and restart the installation process. (I don't recommend this one.)<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br />Tried this about 12 times, using different accounts (local system, local admin) and had the same error each time. I have not tried this using the domain admin account as the server itself is on the network, but in a workgroup. I did not join it to the domain. Now I'm wondering if that could be the issue?<br /><br />2. Fresh Install:<br />I've given that some thought, and who's to say it just won't happen again?<br /><br />3. MS Support:<br />Costs money..... [<img src='/community/emoticons/emotion-2.gif' alt=':D' />]
  7. derrickleggett New Member

    I wouldn't give 2 some thought. I would do it.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.
  8. thorne New Member

    We formatted the hard drive earlier today and re-installed everything. This solved the issue.

    Thanks!
  9. derrickleggett New Member

    It usually does. lol

    Glad your issue is fixed. Hopefully, you'll never have to go through this again.

    MeanOldDBA
    derrickleggett@hotmail.com

    When life gives you a lemon, fire the DBA.

Share This Page