"Failed" install SS 2008 Express R2 on Win 2008 SP 2 server

  • I was requested to install SQL Server 2008 Express R2 on a virtual Win 2008 SP 2 Standard Edition server. Pretty normal request yes? Except for:

    FIRST ATTEMPT:

    1. The windows server is in an undocumented security configuration.

    2. Power Shell was not installed

    3. .Net Internet connectivity failed (SSMS needs internet to check certificates on startup)

    4. Windows Firewall enabled, allowing outbound access only unless inbound exceptions granted.

    SECOND ATTEMPT:

    OK. started Power Shell. Installer now works...up to a point: OOOPPPSSS - Access Denied.

    (uninstall SS2008 Exp Ed), try again.

    OK... grant debug powers. Installer now works... much further along.

    At completion:

    1st Your SQL Server 2008 Installation completed with failures.

    2nd Access Denied

    Launch SSMS - it starts! Specify Windows authentication - oh, we're sorry. Your database is in SINGLE USER mode. [huh?]

    go find the details file, scroll down, find the last entries say:

    2010-12-08 16:48:36 Slp: Error result: -595541211

    2010-12-08 16:48:36 Slp: Result facility code: 1152

    2010-12-08 16:48:36 Slp: Result error code: 49957

    2010-12-08 16:48:36 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine

    2010-12-08 16:48:36 Slp: Sco: Attempting to open registry subkey

    2010-12-08 16:48:36 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed

    2010-12-08 16:48:36 Slp: Sco: Attempting to get registry value DW0201

    2010-12-08 16:48:37 Slp: Submitted 1 of 1 failures to the Watson data repository

    I assume this means that I have a privileges failure, but can't tell for sure.

    Questions:

    1. How did the DB get in single user mode? More critically, in 2008 Express, how do I get it out?

    2. What is the minimum 'relaxed' security settings to obtain an error-free (at least, error message free) installation?

    3. How can I get the real error messages within the thousands of lines of messages in the hundreds of diagnostic files I have to choose from (thank you Dr Watson)?

  • For details, you can look at this web page, containing a few more details: http://serverfault.com/questions/186550/can-not-install-sql-server-2008-express-or-standard

  • 1) Check that your account has got administrative priviledges & you have got full access to all the drives on the server

    2)Check there is no "unknown" policy running on the box

    and maybe do a manual install?

  • @halcyon

    Installing using the built-in admin account. Followed the directions in KB article 2000257 and found I needed to turn on the debug permission, backup and audit/security logging were already available.

    Steve

  • Steve,

    1)when you were un-installing the express, were you doing from the control panel?

    was it normal - ie you can see the server name?

    2) is it being run on the notebook? Can you check that your hardware is compatible with your software?

    On my windows 7, I cannot build windows server 2008 R2

  • We are installing SS2008 Express on a Dell server in our lights-out data center. The virtual server's operating system is Windows 2008 Standard Edition SP 2. All necessary requirements are either met or exceeded.

    The issue has to revolve around permissions, given the lack of documentation. Usually when building a new machine, a blank machine is installed with its OS, then the software installed, then security adjustments are made. Under those circumstances, no problems are encountered.

    However, we are working from the image of a 'hardened' server with most if not all security holes tightened down. Hence my question regarding minimum permissions/privileges.

    KB20000257 describes how three Local Policy Object Display Names / User Rights must be granted to the installing user account (UR: SeBackupPrivilege, SeDebugPrivilege, SeSecurityPrivilege).

    Turns out that, under Security Options, a fourth setting must be adjusted: UAC-Behavior of elevation prompt - Elevate without prompting. I deduce from this setting that a prompt was occurring somewhere in the install process as the administrator user id needed to elevate privileges from the default Win 2008 'allowance'.

    Hence my question: what is the MINIMAL security setting required to smoothly install any variation of SQL Server 2008 on a Windows 2008 Server? The currently available documentation is incomplete or incorrect. I suspect very few individuals, if any, know the full answer to this question.

    Side note: After successfully installing Win 2008 evaluation copy (full Enterprise), when attempting to install the purchased license for standard edition, without changing the UAC, SQL Server installer claims that the install failed with errors. However, the license is inserted and everything is fine.

    I keep thinking of the scene in Marathon Man when Dustin Hoffman is sitting in the dentist chair being asked 'Is it safe?' - and having no idea what 'it' is.

    Steve

  • Steve,

    Are you confident that on the "normal" server build, you can install same version of the SQL on the same version of Windows server without any issues?

    Have you checked local and domain policies?

Viewing 7 posts - 1 through 6 (of 6 total)

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