Introduction
In some instances when installing Credit Hound V6, you may get the following Error. This KBA addressed the permissions aspect of the configuration:
We need to establish if the CreditHoundSU user is setup as a domain account or a local account
Applies to
Credit Hound V6
Resolution
Domain\CreditHoundSU (A domain account is created if the SQL Server and the Credit Hound data reside on different Servers
Local\CreditHoundSU (A local account is created if the SQL Server and the Credit Hound data folder reside on the same Server
If you look at the Credit Hound Manager text file you will see following error:
"\\192.168.9.250\eit\Admin\CreditHound\Configuration.mdb. It is already opened exclusively by another program"
This tends to denote a permissions issue is in play, which is the cause of the API issue when trying to access Credit Hound V6 client application.
The CreditHoundSU user will require the following permissions (check NTFS permissions and also Share permissions):
Program Data Folder
Credit Hound SQL Database
Credit Hound Data Folder & the share the Credit Hound Data resides in
You will need to navigate to the CreditHound data folder and add the Service user to the Security Group:
If the CreditHoundSU user is a Domain account
If SQL and the app data are on 2 different servers then the CreditHoundSU user will need to be a domain user. Please ensure the Credit Hound API in IIS is running as the correct user
Domain\CreditHoundSU (A domain account is created if the SQL Server and the Credit Hound data reside on different Servers)
If the CreditHoundSU has been changed please update these details in in the client configuration file in the shared credit hound data path and in the C:\ProgramData\Draycir\Credit Hound
As you see below, the following Web configuration identities for the WebAPI & WebUI need to be changed to match the Domain account which have been used for the CreditHoundSU
You will need to also access the ClientConfiguration XML in the Data path:
The <WebAPIPoolIndentity> will have amended with the domain account details as highlighted below:
The Credentials which have been setup for CreditHoundSU user also need to be changed in IIS to match the account created
Credit Hound v6.4 and above:
Additionally, change the Credit Hound Data Path in C:\ProgramData\Draycir\Credit Hound \Configuration.xml to use the local Windows drive letter instead of the UNC path:
If you're still having issues with accessing Credit Hound V6 Client, you can look at the following KBA
Knowledge Base Article Details
Related Product | Credit Hound V6 |
Ref Number | KBA-03-03-017 |
Document Date | 12-1-2018 |
Original Author | Vijay Mistry |
Document Version | v1.1 |
Last updated | 1-3-2019 |
Update Author | Vince Hodgson |