Credit Hound v3-5 to Credit Hound v6

To move Credit Hound to a new server while at the same time upgrading it from v3-5 up to v6

Step 1

Ensure all necessary backups are taken before the move:

• Backup the shared Credit Hound Data folder on the old App server (let's call it APP01)
• Backup the SQL Credit Hound COMP000x Database(s) on the old SQL server (SQL01)

Step 2

• Install the Credit Hound server component to the new App server (APP02).
• Run the wizard to create a new bare company, and new Credit Hound Data folder.
• Rename the newly created Credit Hound Data folder to Credit Hound Data.old.
• Restore the previous Credit Hound Data folder from APP01 to APP02.
• Restore the Credit Hound COMP000x database to SQL02.
• Copy Configuration.mdb from Credit Hound Data.old to Credit Hound Data.

Step 3

• Open Credit Hound Manager, you will be prompted to update the configuration database.
• Test the connection to the database on SQL02.
• Test the connection to the ERP on APP02.
• Install the Credit Hound client component to APP02 and run it.
• You will be prompted to update the Credit Hound COMP000x database.
• Finally upgrade all client PCs to v6 using the Credit Hound client installer.

Credit Hound v6 to v6 - Server move only

Step 1

Ensure all necessary backups are taken before the move:

• Backup the shared Credit Hound Data folder
• Backup the SQL Credit Hound Comp000x Databases

Step 2

• Restore the Credit Hound Data in the required location
• Restore the Backup of the SQL Credit Hound companies
• I assume the ERP DB will also be on the new SQL DB
• Ensure the CreditHoundSU user has been setup previously as a domain account (The installer will create a DOMAIN account if being installed on a Domain Controller, otherwise a LOCAL user is created)
• Add this user to the IIS_USRS group

If the account is not configured correctly you may run into the following issues, we have KBA's for this, see below:

KBA-03-03-013 - Failed to Communicate with the Credit Hound Web API

KBA-03-03-017 - Failed to Connect to Credit Hound API - Permissions

Step 3

Install Credit Hound Server element onto the new Server, however we don't want to go through the initial setup wizard. In this process click on cancel and it will prompt you not to run through the wizard again This is what we require as we want to point this to the path which has been moved across.

Please proceed to change the "Shared Path" to location as required and click on save.

Open up the SQL Server where the CreditHound DB has been restored, add the CreditHoundSU domain login, as shown below

Ensure the CreditHoundSU user has the following permissions

Once these permissions are given, please go back into Credit Hound Manager.

As you are moving SQL companies in credit hound manager. companies, click on company and edit:

The Database Connection button and the Override Sage 200 connection details checkbox (replaced with a button in version 6.23 onwards)of Credit Hound Proefessional) will both open a connection window for the SQL database. 

Database Connection is used to configure the connection between the Credit Hound application and the Credit Hound database (COMP000n). 

The Override Sage 200 connection details is used to configure a direct connection between the Credit Hound application and the Sage 200 database in the SQL server.

In order to change the connection to the Sage 200 database, please check this box - if it is already checked (indicating the connection details have been changed before) please un-checkl and re-check this box. As mentioned previously above, this is replaced by a button in versions 6.23 onward.

Knowledge Base Article Details