Answered by:
CRM 2011 Installation Errors on checking service accounts can monitor Perf Counters Validation

Question
-
When the CRM 2011 installer runs its SystemChecks, I get 2 failures - both are "Logon failure: unknown user name or bad password." When I click "Help" it opens the help file but I get "This program cannot display the webpage". Both accounts have the correct username and password (if I change them, the error message is different). I added all 3 (Installation, AspNet, Async) accounts to the Local Administrators, Performance Log Users, and Performance Monitor Users groups and it doesn't seem to affect the result.
The following 2 entries appear in the Installation Log:
16:31:26| Error| Check AspNetServiceAccountCanMonitorPerfCountersValidator : Failure: Logon failure: unknown user name or bad password.
16:31:26| Error| Check AsyncServiceAccountCanMonitorPerfCountersValidator : Failure: Logon failure: unknown user name or bad password.
- Edited by Chris the CRM User Wednesday, March 23, 2011 12:08 AM Noted that it was CRM 2011
Tuesday, March 22, 2011 9:19 PM
Answers
-
I'm still not sure what was causing this issue but we were able to run the installer successfully under the domain administrator account.
- Marked as answer by Chris the CRM User Thursday, March 24, 2011 1:23 PM
Thursday, March 24, 2011 1:23 PM
All replies
-
We are getting the following Audit Failures in the Security Event Log:
(MYCOMPANY\CRMSystem, is the account running the installer, MYCOMPANY\CrmAsync is the async service, MYCOMPANY\CrmService is the Application account)
Audit Failure
A privileged service was called.
Subject:
Security ID: MYCOMPANY\crmsystem
Account Name: crmsystem
Account Domain: MYCOMPANY
Logon ID: 0x11b7ba
Service:
Server: NT Local Security Authority / Authentication Service
Service Name: LsaRegisterLogonProcess()
Process:
Process ID: 0x1e8
Process Name: C:\Windows\System32\lsass.exe
Service Request Information:
Privileges: SeTcbPrivilege
Audit Failure
An account failed to log on.
Subject:
Security ID: MYCOMPANY\crmsystem
Account Name: crmsystem
Account Domain: MYCOMPANY
Logon ID: 0x11b7ba
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0xb54
Caller Process Name: C:\Users\CRMSYS~1\AppData\Local\Temp\MSCRM_{EBD1EA0F-5D81-4983-A3B5-02CCABDAF21C}\Microsoft.Crm.Setup.Server.exe
Network Information:
Workstation Name: MYCOMPANYcrmserver
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: C
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.
Audit Failure
A privileged service was called.
Subject:
Security ID: MYCOMPANY\crmsystem
Account Name: crmsystem
Account Domain: MYCOMPANY
Logon ID: 0x11b7ba
Service:
Server: NT Local Security Authority / Authentication Service
Service Name: LsaRegisterLogonProcess()
Process:
Process ID: 0x1e8
Process Name: C:\Windows\System32\lsass.exe
Service Request Information:
Privileges: SeTcbPrivilege
Audit Failure
An account failed to log on.
Subject:
Security ID: MYCOMPANY\crmsystem
Account Name: crmsystem
Account Domain: MYCOMPANY
Logon ID: 0x11b7ba
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0xb54
Caller Process Name: C:\Users\CRMSYS~1\AppData\Local\Temp\MSCRM_{EBD1EA0F-5D81-4983-A3B5-02CCABDAF21C}\Microsoft.Crm.Setup.Server.exe
Network Information:
Workstation Name: MYCOMPANYcrmserver
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: C
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.
I also have 2 audit successes for logging in as each account:
Audit Success
A logon was attempted using explicit credentials. Subject: Security ID: MYCOMPANY\crmsystem Account Name: crmsystem Account Domain: MYCOMPANY Logon ID: 0x317662 Logon GUID: {4ab09159-73b4-2217-2308-0c433e9b7334} Account Whose Credentials Were Used: Account Name: CRMASYNC Account Domain: MYCOMPANY Logon GUID: {55c08073-0931-e2b6-f972-602cb053edc2} Target Server: Target Server Name: localhost Additional Information: localhost Process Information: Process ID: 0x9dc Process Name: C:\Users\CRMSYS~1\AppData\Local\Temp\MSCRM_{0C855F92-AB7B-4450-971B-246B69F6EF74}\Microsoft.Crm.Setup.Server.exe Network Information: Network Address: - Port: - This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
A logon was attempted using explicit credentials. Subject: Security ID: MYCOMPANY\crmsystem Account Name: crmsystem Account Domain: MYCOMPANY Logon ID: 0x317662 Logon GUID: {4ab09159-73b4-2217-2308-0c433e9b7334} Account Whose Credentials Were Used: Account Name: CRMSERVICE Account Domain: MYCOMPANY Logon GUID: {a22f2838-12fa-8e66-6624-abd40dfa34b2} Target Server: Target Server Name: localhost Additional Information: localhost Process Information: Process ID: 0x9dc Process Name: C:\Users\CRMSYS~1\AppData\Local\Temp\MSCRM_{0C855F92-AB7B-4450-971B-246B69F6EF74}\Microsoft.Crm.Setup.Server.exe Network Information: Network Address: - Port: - This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Wednesday, March 23, 2011 6:07 PM -
I'm still not sure what was causing this issue but we were able to run the installer successfully under the domain administrator account.
- Marked as answer by Chris the CRM User Thursday, March 24, 2011 1:23 PM
Thursday, March 24, 2011 1:23 PM