Hello,
on this Windows Server 2012 Standard server with local SQL Server 2012, SharePoint 2013 Products Configuration Wizard will not go beyond Step 3.
On Wizard: "Failed to connect to the configuration database" and 2 lines we can find in the log:
Exception: System.Runtime.InteropServices.COMException (0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
In psconfigui log we get
08/27/2013 15:41:18.22 psconfigui.exe (0x3024) 0x2CA4 SharePoint Foundation Topology 9sis Medium Attempting to give SE_ASSIGNPRIMARYTOKEN_NAME privilege to application pool user mydomain\sa_sql_sc
08/27/2013 15:41:18.22 psconfigui.exe (0x3024) 0x2CA4 SharePoint Foundation Topology 9sit Medium Attempting to give SE_INCREASE_QUOTA_NAME privilege to application pool user mydomain\sa_sql_sc
08/27/2013 15:41:18.22 psconfigui.exe (0x3024) 0x2CA4 SharePoint Foundation Topology fx74 High An exception occured while committing IIS configuration changes: Keyset does not exist (Exception from HRESULT: 0x80090016)
08/27/2013 15:41:19.25 psconfigui.exe (0x3024) 0x2CA4 SharePoint Foundation Topology bmt5 High Creating new application pool 'SecurityTokenServiceApplicationPool'.
[...]
The directory C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys has
Everyone: Read
SYSTEM: Full control
LOCAL SERVICE: Read
sa_sql_sc: Read
Administrators: Full control
At exact same time in event log we have just after startup of SharePoint Services a HttpEvent Warning 7040
SSL Certificate Settings created by an admin process for endpoint : 0.0.0.0:32844 .
Then SharePoint services are stopped and event 1530
SSL Certificate Settings deleted for endpoint : 0.0.0.0:32844 .
At exact same time in application event log SPAdminV4 starts and we get about 20 attempts / warnings on COM+ SOAP Services followed by SharePoint events 100 & 104:
Failed to connect to the configuration database.
An exception of type System.Runtime.InteropServices.COMException was thrown. Additional exception information: Keyset does not exist (Exception from HRESULT: 0x80090016)
System.Runtime.InteropServices.COMException (0x80090016): Keyset does not exist (Exception from HRESULT: 0x80090016)
at Microsoft.Web.Administration.Interop.AppHostWritableAdminManager.CommitChanges()
at Microsoft.Web.Administration.Configuration.CommitChanges()
at Microsoft.Web.Administration.ConfigurationManager.CommitChanges()
at Microsoft.Web.Administration.ServerManager.CommitChanges()
at Microsoft.SharePoint.Administration.SPIisServerManager.CommitChanges(ApplyChanges applyChanges)
at Microsoft.SharePoint.Administration.SPIisProvisioningAssistant.ProvisionApplicationPool(String name, SecurityIdentifier sid, String password, SPIisApplicationPoolSettings settings)
at Microsoft.SharePoint.Administration.SPIisManager.ProvisionApplicationPool(String name, SecurityIdentifier sid, SecureString password, SPIisApplicationPoolSettings settings)
at Microsoft.SharePoint.Administration.SPIisWebServiceApplicationPool.ProvisionLocal(SPIisWebServiceApplicationPoolProvisioningOptions options)
at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.ProvisionApplicationInstance()
at Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceApplication.ProvisionLocal(SPServiceInstance serviceInstance)
at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Provision()
at Microsoft.SharePoint.Administration.SPFarm.Join(Boolean skipRegisterAsDistributedCacheHost)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Nothing obvious found in sysinternals' Procmon report.
In security event log we have several Audit Success on time, including:
Key file operation.
Subject:
Security ID: SYSTEM
Account Name: MYDOMAIN-ADMINSRV$
Account Domain: MyDomain
Logon ID: 0x3E7
Cryptographic Parameters:
Provider Name: Microsoft Software Key Storage Provider
Algorithm Name: UNKNOWN
Key Name: {3160F19D-2655-4D30-8CFA-0BED02EE2C87}
Key Type: Machine key.
Key File Operation Information:
File Path: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\ba086a1d10fca7378236dbaad4c7960c_d9ec63d0-a904-4896-afc8-e54524a060e3
Operation: Read persisted key from file.
Return Code: 0x0
Beyond MachineKeys directory protection - which as you can see from above seems OK-, what else could I check?
Thanks in advance for any help.
/Patrice