I have had an issue lately where a new implementation of SCVMM 2012 R2 would integrate perfectly with SCOM, but PRO would fail its diagnostics.
The detailed message in SCVMM has an error code of 11825, but is not that helpful.
On the SCVMM server, there are a couple of interesting events in the Application and Security logs. First the Security Log.
The detail of this Audit failure is shown below, at first I thought it was an issue with the NULL SID:
An account failed to log on.
Security ID: XXXXXXXX\SA.SCVMM-SQL
Account Name: SA.SCVMM-SQL
Account Domain: XXXXXXXXX
Logon ID: 0x118CA
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Failure Reason: Unknown user name or bad password.
Sub Status: 0xC0000064
Caller Process ID: 0x598
Caller Process Name: C:\Program Files\Microsoft SQL Server\MSSQL11.SCVMM\MSSQL\Binn\sqlservr.exe
Workstation Name: XXXXXXXXX
Source Network Address: –
Source Port: –
Detailed Authentication Information:
Logon Process: Authz
Authentication Package: Kerberos
Transited Services: –
Package Name (NTLM only): –
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
– Transited services indicate which intermediate services have participated in this logon request.
– Package name indicates which sub-protocol was used among the NTLM protocols.
– Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
The account this relates to, is the domain service account that is being used for SCVMMs local SQL install. This error also has a related event in the Application log, on the SCVMM server also.
This suggests that the SQL account does not have permission to AD.
The SQL Server service account does not have permission to access Active Directory Domain Services (AD DS). (Error ID: 2607)
After much digging and pulling out what hair I have left, I have found this issue is resolved by adding the SQL service account to the built-in domain group “Windows Authorization Access Group”. Pro then works perfectly.
Hope this helps someone with more hair than me 🙂