If Credit Hound server is installed to a Domain Controller,  you may encounter an issue with the IIS Application Pool not starting correctly in certain circumstances.

Applies to 

Credit Hound V6


This issue is unique to environments where Credit Hound Server is being installed on the domain controller itself. If you let the CH installer create the CreditHoundSU user as a local user on a domain controller, Windows will actually create a domain user(1) . However the installer will configure IIS to run as the (non-existent) local user.

For example, if the domain controller is SRV1 and the domain is CORP, by letting the Credit Hound installer create a local user, the account CORP\CreditHoundSU will be created but the IIS application polls will be running as SRV1\CreditHoundSU. Additionally, attempts to create SQL databases will also fail as the account does not exist. 


The simplest solution is to create a domain account prior to running the Credit Hound Server installer, and to specify this account during the installation. If you have already completed the installation, you will need to update the application identity the following locations

In IIS AppPool Advanced settings:

and in the following XML configuration files:

  • [Credit Hound Shared Data Path]\Credit Hound Data\ClientConfiguration.xml
  • C:\ProgramData\Draycir\Credit Hound\Configuration.xml
  • C:\ProgramData\Draycir\Credit Hound\Server\ClientConfiguration.xml

You may need to edit the user name more than once in each file, for example:

1) "..when a Windows server is promoted to a domain controller, the server no longer uses the local account (Security Accounts Manager [SAM]) database during normal operations to store users and groups. When the promotion is complete, the new domain controller has a copy of the Active Directory database in which it stores users, groups, and computer accounts. The SAM database is present, but it is inaccessible when the server is running in Normal mode."