Search Engine: Elastic

Article ID: 3655, created on Feb 8, 2008, last review on May 10, 2014

  • Applies to:
  • Helm 3


When logging into the CP you receive the following red error message:

"Unable to log in due to a configuration problem"

This could be due to a number of reasons, so you need to check the Helm Error Logs at [Helm installation folder]\\Helm\\Logs\\Error
1.) The following error may be found in the error log

modSecurity.Login Execution failed.
(Method '~' of object '~' failed)

This is usually due to the Server in the Helm Configuration Tool (under the System Database tab) being incorrect. Ensure the server is correct.


2.) The following page may be reached when attempting to log in:

Server object error 'ASP 0177 : 8000401a'

Server.CreateObject Failed

/default.asp, line 49

The server process could not be started because the configured identity is incorrect. Check the username and password.

There will be nothing relating to this in the error log.

The problem is usually due to the password of the admin account being different to the password in the Helm Config Tool (in the System Identity tab).

To synchronise the passwords, go to Start -> Settings-> Control Panel -> Administrative Tools -> Computer Management then Local Users and Groups -> Users

Right-click the Admin account you are running Helm from (this is the same as the one listed next to "User" in the Helm Config Tool under the System Identity tab) and choose Set Password. Choose a password, then update this in the Helm Config Tool to be the same.


3.) The following error may be found in the error log:

(Login failed for user 'helmdbuser'. Reason: Not associated with a trusted SQL Server connection.)

This is because the SQL server needs to be changed to mixed mode security and not just trusted connections only.

To do this, go to Enterprise Manager, go to the server you are running Helm on, and right-click -> Properties. Go to the Security tab and you'll see that Authentication is set to Windows only. Change this to SQL Server and Windows.

Now try and login to the control panel.
4.) The following error may be found in the log:

2003-09-08 08:39:46 ValidateLicenceEx Invalid licence key. Invalid server id.

This means that the license is being used on another machine. Licenses can only work on one machine at one time. If you need it reset, follow these instructions:
It is now possible for you to reset your Helm licences yourself via our members login area. You may need to do this if you move a licence to another server or if you have problems with your licence key.

1. Log into the members area at
2. Click on 'View licences' to see a list of licences in your account
3. Click on the licence key that needs resetting
4. Click the 'Reset Licence' button.
1. Go into the Helm Configuration Tool
2. Go to the Licence Information tab
3. Click the Update button that you see there.

If you still have problem with your licence after resetting please contact support at

5.) The following error may be found in the log:
2003-09-08 08:39:46 ValidateLicenceEx Invalid licence key. Licence has expired.
This is to do with Internet Explorer settings and the solution to this problem can be found here:

110556ad4b9f1c73a3682661cd1dca89 152090ff5e9a05ea7e1cf0c248449638 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF