Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1854
  • Last Modified:

MS SQL SVR 2008 R2 errors installing on a win 2008 r2 sp1 server

Any help would be greatly appreciated.  Can't get MS SQL SVR 2008 R2 to install on a win 2008 r2 sp1 server.  See errors below.

Description:
  SQL Server 2008 R2 Setup has encountered an error.

Problem signature:
  Problem Event Name:      SQL100Exception
  Problem Signature 01:      SQL Server 2008 R2@RTM@
  Problem Signature 02:      0x987D2693
  Problem Signature 03:      0x987D2693
  Problem Signature 04:      0xE8A9805D
  Problem Signature 05:      0xE8A9805D
  Problem Signature 06:      SqlEngineDBStartConfigAction_install_configrc
  Problem Signature 07:      0x9C5770A6
  Problem Signature 08:      Unknown
  Problem Signature 09:      Unknown
  Problem Signature 10:      Unknown
  OS Version:      6.1.7601.2.1.0.274.10
  Locale ID:      1033

Additional information about the problem:
  LCID:      1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
0
Steelin_It
Asked:
Steelin_It
  • 2
1 Solution
 
x-menIT super heroCommented:
can you post the logs from the "Setup Boostrap" folder?
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
While you're getting the logs, a few other things to check:
  Confirm the prerequisites are loaded.  Usually that's .NET 3.5 SP1... and usually the installer will take care of it for you.  Not high hopes on this one.
  Run 'winver.exe' which can usually be found in the windows/system32 directory, and confirm it looks 'normal'... not a Debug version of the OS.  Apparently there is an issue with the debug version.  (There are also apparently some evaluation editions of Windows which also cause the SQL installer to fail in this way.)
  Were there any other versions of the client or SQL tools previously installed on this instance?
  Another possible item to check... in the local security policies make certain the setting "Computer Configuration\Windows Settings\Local Policies\User Rights Assignment\Debug programs" isn't getting turned on by group policy.
0
 
Steelin_ItAuthor Commented:
It turned out that we had a "debugged" version of the os for the install that was corrupt
0
 
Steelin_ItAuthor Commented:
The Debugged version of the install was corrupt.  An install of the original version took care of the problem
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now