none
SQL Server 2012 Install Failure - Error: 17190, Severity: 16, State: 1

    Question

  • Okay, I've seen a number of people who've experienced this problem.  There are work arounds posted to use a local account rather than a system account but I'd like to be able to complete a 2012 installation using mixed mode authentication so any assistance on what I need to do configure my system so the install shield will complete without issue would be greatly appreciated.

    Attempting to install SQL Server 2012 Enterprise on a Windows 7 x64 system with Visual Studio 2010 Ultimate SP1 and IIS 7.5 Express.  Installations of IIS and VS are default except installing to the D drive where possible as C is an SSD.  Installation options for SQL are pretty much default except for pointing to D and selected mixed mode.  Logs and screen shots can be found at http://hossnet.com/SQL-Install/.  The logs and screenshots have been sanitized so they don't show user ids or system name but the id used for the installation is a LA.  Looking through the system it looks like the install couldn't create the SQL user ids and groups.

    Any recommendations on how to correct this would be greatly appreciated. 

    Allen

    2012-04-13 22:46:06.12 Server      Microsoft SQL Server 2012 - 11.0.2100.60 (X64) 
    Feb 10 2012 19:39:15 
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    2012-04-13 22:46:06.12 Server      (c) Microsoft Corporation.
    2012-04-13 22:46:06.12 Server      All rights reserved.
    2012-04-13 22:46:06.12 Server      Server process ID is 7216.
    2012-04-13 22:46:06.12 Server      System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
    2012-04-13 22:46:06.12 Server      Authentication mode is MIXED.
    2012-04-13 22:46:06.12 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2012-04-13 22:46:06.12 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2012-04-13 22:46:06.12 Server      Registry startup parameters: 
    -d D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2012-04-13 22:46:06.12 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "SQL_Latin1_General_CP1_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2012-04-13 22:46:06.26 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2012-04-13 22:46:06.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2012-04-13 22:46:06.26 Server      Detected 16359 MB of RAM. This is an informational message; no user action is required.
    2012-04-13 22:46:06.26 Server      Using conventional memory in the memory manager.
    2012-04-13 22:46:06.29 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2012-04-13 22:46:06.30 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2012-04-13 22:46:06.30 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2012-04-13 22:46:06.31 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2012-04-13 22:46:06.31 spid5s      Warning ******************
    2012-04-13 22:46:06.31 Server      Software Usage Metrics is disabled.
    2012-04-13 22:46:06.31 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2012-04-13 22:46:06.31 spid5s      Starting up database 'master'.
    2012-04-13 22:46:06.40 Server      CLR version v4.0.30319 loaded.
    2012-04-13 22:46:06.44 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2012-04-13 22:46:06.99 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2012-04-13 22:46:06.99 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2012-04-13 22:46:07.07 spid5s      SQL Trace ID 1 was started by login "sa".
    2012-04-13 22:46:07.07 spid5s      Server name is '<SYSTEM NAME>'. This is an informational message only. No user action is required.
    2012-04-13 22:46:07.08 spid12s     Password policy update was successful.
    2012-04-13 22:46:07.08 spid12s     Error: 17190, Severity: 16, State: 1.
    2012-04-13 22:46:07.08 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2012-04-13 22:46:07.08 spid12s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2012-04-13 22:46:07.08 spid12s     Error: 17182, Severity: 16, State: 1.
    2012-04-13 22:46:07.08 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2012-04-13 22:46:07.08 spid12s     Error: 17182, Severity: 16, State: 1.
    2012-04-13 22:46:07.08 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2012-04-13 22:46:07.08 spid12s     Error: 17826, Severity: 18, State: 3.
    2012-04-13 22:46:07.08 spid12s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2012-04-13 22:46:07.08 spid12s     Error: 17120, Severity: 16, State: 1.
    2012-04-13 22:46:07.08 spid12s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Saturday, April 14, 2012 9:01 PM

Answers

  • Ahmed,

    Nice to see how responsive you are on this thread.  Thank you.  Concerning your latest suggestion, I had previously verified in the SQL Server Configuration Manager that "Force Encryption" wasn't set for any of the protocols.

    I am happy to report that I have successfully installed SQL Server 2012 Enterprise on my Windows 7 x64 PC with VS 2010 Ultimate and IIS 7.5.  My background is technical so I understand the concept of making limited changes so that you can track changes and understand their effects.  Unfortunately given the amount of time it takes to install SQL Server (even on my I7 SSD based system) and limited time to get this going I had to make a few changes that individually or in tandem could account for the success.  Perhaps if I have time later I'll build out a VM and try to recreate the problem.  Anyway, the steps that I performed to get a successful installation.

    1) Uninstall the previous failed installation:

    • Uninstalled SQL Server 2008/2012 from the Control Panel - Program and Features
      NOTE: Good procedure can be found at http://technet.microsoft.com/en-us/library/ms143412.aspx
    • Manually deleted the "Microsoft SQL Server" directory from the "Program Files" and "Program Files (x86)" directories.
      NOTE: I could do this because I don't have any other SQL installations.
    • Deleted any MS SQL users and groups (Control Panel - Administrative Tools - Computer Management)
    • Deleted any left over SQL profiles (Computer - Properties - Advanced System Settings - Advanced - User Profiles)
    • Deleted any left over SQL profile directories (C:\Users)
    • Deleted the PendingFileRenameOperations registry entry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager)
      NOTE: Alwayake a backup of your registry for playing with it.
      NOTE: There are a number of articles on the net about this key.  This step is one of the pieces that could have been the fix but because in my impatience making multiple changes I can't prove it right now.
    • Rebooted

    2) Installed SQL Server 2012:

    • Selected the components I wanted to install
    • Selected the desired installation directory
    • Selected my desired 'Mixed Mode'
    • Named my SQL instance to something other than the default
      NOTE: Again, another change that could have made a difference.
    • Accepted the defaults for everything else. 

    As I've been researching this issue there seems to be a bit of speculation that the 2012 install process can be thrown off by systems built using response files.  I question the details of that but because I'm using an SSD for my primary partition I built out my system using a response file so that all the system logs, user files, etc would reside on a spindle based drive.  Is that my problem here?  I don't think so as I was able to successfully install SQL Server 2012 the first time.  I had to uninstall it because I realized there were a few apps that I wanted installed prior (VS for one) to install SQL Server.  My gut is that the uninstall process left something funky and the act of changing the instance name or lengthy manual clean up got me past it.

    Anyway, I'm up and running.  Thank you for your help and hope this post helps someone else.

     

    Sunday, April 15, 2012 10:00 PM

All replies

  • Can you check the workaround in the below blogpost

    http://blogs.msdn.com/b/karthick_pk/archive/2011/03/05/initializing-the-fallback-certificate-failed-with-error-code-1-state-1-error-number-2146893788.aspx


    Regards,
    Ahmed Ibrahim
    SQL Server Setup Team
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
    This can be beneficial to other community members reading the thread.

    Sunday, April 15, 2012 1:10 AM
  • Ahmed,

    Thank you for the quick response.  I had read through that link previously and while the problem isn't quite the same I had attempted the fix with no luck.  Just for safety sake, I uninstalled everything I could find relating to SQL Server 2012/2008, cleared all profiles, users, groups, files and rebooted.  Incidentally, I can encrypt files no problem.

    When I re-ran the installer it failed in the same way.  What I can't get past is when I looking in the users I see that the installation never created the all the user IDs and groups that it should have.  For instance, on this last install attempt there aren't any new user accounts created and for the groups created are (SQLServer2005SQLBrowserUser$FOVERO1 and SQLServerMSASUser$FOVERO1$MSSQLSERVER) and user profiles are (NT SERVICE\MsDtsServer110 and NT SERVICE\MSSQLServerOLAPService).

    Any assistance would be appreciated.

    Sunday, April 15, 2012 4:24 AM
  • Can you check the workaround in the below thread ?

    http://social.msdn.microsoft.com/forums/en-US/sqldatabaseengine/thread/3c45dc77-7402-49ac-81f1-16d781d3f434/


    Regards,
    Ahmed Ibrahim
    SQL Server Setup Team
    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
    This can be beneficial to other community members reading the thread.

    Sunday, April 15, 2012 5:59 AM
  • Ahmed,

    Nice to see how responsive you are on this thread.  Thank you.  Concerning your latest suggestion, I had previously verified in the SQL Server Configuration Manager that "Force Encryption" wasn't set for any of the protocols.

    I am happy to report that I have successfully installed SQL Server 2012 Enterprise on my Windows 7 x64 PC with VS 2010 Ultimate and IIS 7.5.  My background is technical so I understand the concept of making limited changes so that you can track changes and understand their effects.  Unfortunately given the amount of time it takes to install SQL Server (even on my I7 SSD based system) and limited time to get this going I had to make a few changes that individually or in tandem could account for the success.  Perhaps if I have time later I'll build out a VM and try to recreate the problem.  Anyway, the steps that I performed to get a successful installation.

    1) Uninstall the previous failed installation:

    • Uninstalled SQL Server 2008/2012 from the Control Panel - Program and Features
      NOTE: Good procedure can be found at http://technet.microsoft.com/en-us/library/ms143412.aspx
    • Manually deleted the "Microsoft SQL Server" directory from the "Program Files" and "Program Files (x86)" directories.
      NOTE: I could do this because I don't have any other SQL installations.
    • Deleted any MS SQL users and groups (Control Panel - Administrative Tools - Computer Management)
    • Deleted any left over SQL profiles (Computer - Properties - Advanced System Settings - Advanced - User Profiles)
    • Deleted any left over SQL profile directories (C:\Users)
    • Deleted the PendingFileRenameOperations registry entry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager)
      NOTE: Alwayake a backup of your registry for playing with it.
      NOTE: There are a number of articles on the net about this key.  This step is one of the pieces that could have been the fix but because in my impatience making multiple changes I can't prove it right now.
    • Rebooted

    2) Installed SQL Server 2012:

    • Selected the components I wanted to install
    • Selected the desired installation directory
    • Selected my desired 'Mixed Mode'
    • Named my SQL instance to something other than the default
      NOTE: Again, another change that could have made a difference.
    • Accepted the defaults for everything else. 

    As I've been researching this issue there seems to be a bit of speculation that the 2012 install process can be thrown off by systems built using response files.  I question the details of that but because I'm using an SSD for my primary partition I built out my system using a response file so that all the system logs, user files, etc would reside on a spindle based drive.  Is that my problem here?  I don't think so as I was able to successfully install SQL Server 2012 the first time.  I had to uninstall it because I realized there were a few apps that I wanted installed prior (VS for one) to install SQL Server.  My gut is that the uninstall process left something funky and the act of changing the instance name or lengthy manual clean up got me past it.

    Anyway, I'm up and running.  Thank you for your help and hope this post helps someone else.

     

    Sunday, April 15, 2012 10:00 PM