Post reply

Installing SQL 2000 on new server

  • June 13, 2005 at 3:36 pm

    #93204

    We are attempting to install SQL 2000 on a new box with Win2003 server sp1 using mixed authentication.  We take the defaults (except for the data directory) and everything seems to install fine.  However, when we start up the service, it shuts itself off.  Looking in the system log (which unfortunately I do not have access to) we are receiving error 17052 installing tempdb. I've asked the IT gurus to check the permissions since that seems to be a common problem but other than that I'm at a loss. Any ideas? Nothing I've googled seems to apply, and the KB articles I've found refer to clustered servers which we are not doing. The box has 2 cpus with hyperthreading and 2G mem. Thanks!

  • June 13, 2005 at 4:09 pm

    #565134

    Could you post the text that comes along with the error?  How are you staring the service?

    Checking permissions on the account under which SQL Server runs is a good idea.  Also check permissions on the account that the SQL Server Agent runs under (though wrong permissions there shouldn't keep it from starting).

    And then again, I might be wrong ...
    David Webb

  • June 13, 2005 at 4:24 pm

    #565136

    Rita,

    If you don't have access to system logs then maybe you have access to SQL Server error logs? But if you don't have access to system logs do you think you have rights to startup the service? Another thing: tempdb is re-created each time the SQL server is restarted. Do you think you or SQL server startup account have rights to create/modify files?

    I did have a couple of cases that I mention now and then. Something or someone removed SYSTEM from Access Control List of  SQL Server directories and SQL Server had LocalSystem as startup account.

    Yelena

    Regards,Yelena Varsha

  • June 14, 2005 at 1:05 am

    #565177

    You did not mention anything about installing SQL server 2000 service pack 3. I had problems with fresh installation and also once I changed server name, all solved with SP3 installation. On windows 2003 server you always need SQL server SP3.

     

    Jyrki

  • June 14, 2005 at 5:38 am

    #565229

    And the answer was... Installing SQL with a local admin startup account initially. We were then able to change the account to a non-privilged account to run under.  Apparently, the local admin account privileges don't trickle down to SQL during the install.  Therefor, it couldn't setup the registry entries, etc... Thanks for your suggestions.

    Jyrki - the reason we didn't install any sp's is that we are imaging the machine so that if sp4 gives us trouble, we can easily rollback to the pre-sp state and install sp3a.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply