Article ID: 3851, created on Feb 8, 2008, last review on Apr 18, 2012

  • Applies to:
  • Helm 3

Resolution

 
Problem
 
When adding a domain to Helm, it appears to add, but domains are still showing as zero on the left side panel even though I actually have a number of domains in Helm. Also, I see errors similar to this in the Helm error logs:
 
2005-04-29 12:44:02 HELMDA:modDataAccess::Execute Execution failed. SQL was:
SELECT Count(HostDomain.DomainId) as NumDomains FROM HostDomain, Package, Account WHERE HostDomain.PackageId = Package.PackageId AND Package.AccountNumber = Account.AccountNumber AND HostDomain.domainaliasid = 0 AND HostDomain.subdomainid = 0
(Invalid column name 'domainaliasid'.)
2005-04-29 12:44:02 DomainData.Count Execution failed. SQL was:
SELECT Count(HostDomain.DomainId) as NumDomains FROM HostDomain, Package, Account WHERE HostDomain.PackageId = Package.PackageId AND Package.AccountNumber = Account.AccountNumber AND HostDomain.domainaliasid = 0 AND HostDomain.subdomainid = 0
(Invalid column name 'domainaliasid'.)
2005-04-29 12:44:02 CDomain.Count Execution failed. SQL was:
SELECT Count(HostDomain.DomainId) as NumDomains FROM HostDomain, Package, Account WHERE HostDomain.PackageId = Package.PackageId AND Package.AccountNumber = Account.AccountNumber AND HostDomain.domainaliasid = 0 AND HostDomain.subdomainid = 0
(Invalid column name 'domainaliasid'.)
 
Solution
 
1.) Are you using SQL Server to run your Helm database? If so, check in Enterprise Manager to see what instances you have set up. What you need is a default instance of SQL to be present (this is selectable from the actual install of SQL Server). For instance, you may have something like:
 
SQLSERVER\\HELM
SQLSERVER\\SQL 2000
 
but no default instance, which would just be:
 
SQLSERVER
 
Without the default instance, Helm won't be able to access SQL Server correctly, and you will have problems similar to the one above. Adding a default instance should fix the problem. If not, go to step 2.
 
2.) If you still experience the issue with MS SQL, or you are using MSDE, it is likely to be a problem with the collation language of either application.
 
- If you are using SQL Server you will need to alter the database instance collation language to be English (US or UK) - refer to the SQL Server documentation for details on how to do this.
 
- If you are using MSDE you will need to uninstall MSDE, first backing up the Helm database to a safe place. Then you need to download a clean instance of MSDE which has correct collation language settings. One such instance can be found here:
 
 
Install this version, and then create a new Helm database by using the Test Connection button in the Helm Configuration Tool. Then go to this folder:
 
[INSTALL FOLDER FOR Microsoft SQL Server]\\MSSQL$HELM\\Data
 
and delete the Helm database you just created, and copy in the old database you backed up earlier. Go to the Helm Configuration Tool and click the Test Connection button again. It should successfully connect. Now login to Helm - the number of Domains in Helm should display correctly on the left.
 
If this does not solve your issue, contact your support provider.

110556ad4b9f1c73a3682661cd1dca89 152090ff5e9a05ea7e1cf0c248449638 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF