Results 1 to 9 of 9
  1. #1
    Join Date
    Mar 2004
    Posts
    5

    Unanswered: Unattended Installation of SQL 2000 fails

    We're trying to use the unattended installation method for installing SQL 2000 on Windows 2000 servers. I've installed it (through terminal server) on two machines successfully, and two machines unsuccessfully. On the unsuccessful machines, it fails with no errors, and no SQL files are installed (bombs out almost immediately).

    Anyone else had this problem? Could it possibly be a hardware issue?

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Check - Event Viewer, SQLSTP.LOG (if created) from Windows directory for further information.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    Mar 2004
    Posts
    5
    The sqlstp.log file doesn't contain anything but normal entries until the very last line that says "Installation Failed". I rebooted the server remotely, but now it won't come back, so I can't check the event viewer yet...any other ideas while I'm waiting on the server?
    Thanks!

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Event viewer is only the hope to get some information in this regard.

    Instead of trying with TS try to install locally on the box.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    Mar 2004
    Posts
    5
    OK, I'll check that as soon as I can get the box back up.

    We've tried the manual install, and that works fine, but we won't be able to use that method for some of our remote sites (Canada & Europe).

  6. #6
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Ensure no hardcoded servernames/variables used in unattended installation files.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  7. #7
    Join Date
    Mar 2004
    Posts
    5
    OK, I checked, and nothing is sent to the event log. It looks like it's not even getting that far.

    As for the hardcoded server name, here's the string we use, and it has worked in the past:

    BuildServer <servername> <path to setup files> <path to installation files> <path to log files>

    Is this what you're talking about when you say "no hard coded server names"? I'm not sure how else we would use this command. Plus, it works fine for some servers...
    Thanks again...

  8. #8
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    I thought its a global script and if its parameterised then should be no issues.

    Ensure the OS is equipped with same levels of service pack where the installation worked fine earlier.

    Try to install manually on the failed machines to ensure no issues on OS part.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  9. #9
    Join Date
    Mar 2004
    Posts
    5

    Smile

    OK, I'll try that. Thanks again for all of your help!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •