Helm3 Unable to Load Helm Extensions Icon

If you are using HELM 3 with Helm Extensions and if you getting error of “Unable to Load Helm Extensions Icon” once logged into the HELM Control Panel, something would be wrong from your Helm extensions configuration.

With the above symptom, you might also getting the following error when you hitting the website setting from each of your domain,
===============
Microsoft VBScript runtime error ‘800a01a8’
Object required: ‘HexMain’
/hex/include.asp, line 52
===============

To fix this problem, you may refer to the step as below.
1. Go to Windows Start button, seek for Administrative Tools and hit on Components Services.
2. Expand Component Services -> Computers -> My Computer -> COM+ Applications.
3. Right click on Helm Extensions, click on Properties.
4. Select on Identity tab, re-enter the HELM_Admin Password and save it.

HELM3 Subdomain not working

Today, I was asked by HaoSiaoKing aka Kwan for this case and I am now sharing the solution.

Scenario: When create a subdomain from HELM3 but all of the script mapping is not created automatically. I tried to use a alternative way to make it working as solution below.

Resolution:
1. The workaround I am using is to replace all of the script mapping back to the subdomain where is it not created by the subdomain.
2. Open IIS6, you shall see the hostname and right click then select the properties.

3. Check the checkbox of “Enable Direct Metabase Edit” and press OK.
4. Go to the directory of “C:\WINDOWS\system32\inetsrv”.
5. Backup the file named MetaBase.xml.
6. Open the file with notepad.
7. Find the domain name from the MetaBase.xml file.
8. Copy the line as below.

ScriptMaps=”.aspl,C:\Perl\bin\PerlEx30.dll,5,GET,HEAD,POST
.cdx,C:\WINDOWS\system32\inetsrv\asp.dll,5,GET,HEAD,POST,TRACE
.cer,C:\WINDOWS\system32\inetsrv\asp.dll,5,GET,HEAD,POST,TRACE


*,C:\ColdFusion8\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll,0,GET,HEAD,POST,TRACE”

9. Find the subdomain.
10. Paste the copied line and replace the ScriptMaps.
11. Restart IIS.

FrontPage Users cannot login by using HELM

There is a known issue with HELM 3 with Frontpage extension that the Frontpage user not able to login if the account have been recreated through the HELM system.

This is because the fp_ prefix user is not added correctly, to resolve this issue, you may refer to the step as below.

1) Login to the server using Terminal Services Client
2) Open Computer Management
3) Go to Local Users and Groups -> Groups
4) Expand the description field. Look for the group that contains the domain name that was readded the in the description field. The group name will end in _AdvAuthor. Double click this group
5) Add the domain_fp user to this group, click OK.

HELM 3 Not able to add FTP account

When you tried to create FTP account through HELM 3 and you might not able to create the FTP account, check with your HELM Error Log.

If you got the sample error as below, do the following step.

Sample Error:

2009-08-25 14:10:00 modNTFS::SetFolderSecurity 0-2147219579: SetACL failed for User Account: exatest1 (“C:\Program Files\WebHost Automation\Helm\\System\setACL.exe” -on “\\MICKGENIE\c$\domains\mickgenie.com” -ot file -actn ace -ace “n:MICKGENIE\myftp;p:change;m:set;w:dacl” -silent -silent){0}
2009-08-25 14:10:00 FTP.IFTP_Execute 0-2147219579: SetACL failed for User Account: exatest1 (“C:\Program Files\WebHost Automation\Helm\\System\setACL.exe” -on “\\MICKGENIE\c$\domains\mickgenie.com” -ot file -actn ace -ace “n:MICKGENIE\myftp;p:change;m:set;w:dacl” -silent -silent){0}
2009-08-25 14:10:00 CFTP.AddFTPAccountEx 0-2147219579: SetACL failed for User Account: exatest1 (“C:\Program Files\WebHost Automation\Helm\\System\setACL.exe” -on “\\MICKGENIE\c$\domains\mickgenie.com” -ot file -actn ace -ace “n:MICKGENIE\myftp;p:change;m:set;w:dacl” -silent -silent){0}

Resolution:

1. Login to the server as console or RDP.
2. Go to the services or run ‘services.msc’
3. Restart ‘Server’ services.
4. Well Done, you have fixed the issue.

Parallels HELM not working after applied ASP.Net 3.5 Framework

If you found Parallels HELM or previously called HELM4 not working after installed ASP .Net 3.5 Framework, and HELM Configuration Tool not working as well, you might use the following patches to fix the problem.

Affected Versions:
Please take note this patches only use for Parallel HELM 4.0 and 4.1 only.

Download:
HelmConfigurationTool.exe
Helm_KB951847_Patch.exe

If you have old version of HELM 4.0 (older than 4.0.20), please downlaod latest Helm Configuration Tool named HelmConfigurationTool.exe version 4.0.20(with Download section above), copy/replace it to ..\Helm4\Tools folder.

Launch the HELM_KB951847.Patch.exe command line tool on the affected server. If after this procedure Parallel Helm still not work, launch Configuration Tool and proform Helm update.