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.

Fixed DotNetPanel ASP.Net 4.0 not installed

Recently I found out when you have ASP.Net 4.0 installed from your server but your DotNetPanel do not show it is installed. To fix it, simply modify your MSSQL database data.

1. you should backup your MSSQL database.
2. Open table ServiceDefaultProperties.
3. Check for the ProviderID of 2 and 101 if contain AspNet40Path(32 bits server) or AspNet40x64Path(64 bits server).
4. If not, add them to the MSSQL and point to the path as below.
AspNet40Path -> %SYSTEMROOT%\Microsoft.NET\Framework\v4.0.30128\aspnet_isapi.dll
AspNet40x64Path -> %WINDIR%\Microsoft.NET\Framework64\v4.0.30128\aspnet_isapi.dll

Check if ASP.Net 4.0 show from your server setting. If not, you may proceed to the step below.

1. Backup MSSQL database.
2. Open table ServiceProperties.
3. Check if AspNet40Path and AspNet40x64Path existed for each of the ServiceID.
4. If you have multiple web server and do not know which server belong to which ServiceID, open table Services and Servers.
5. Check for Services table and look for ProviderID of 2(IIS6) or 101(IIS7). Check for the ServerID and verify the server from Servers table.
6. Add the record as below.
AspNet40Path -> %SYSTEMROOT%\Microsoft.NET\Framework\v4.0.30128\aspnet_isapi.dll
AspNet40x64Path -> %WINDIR%\Microsoft.NET\Framework64\v4.0.30128\aspnet_isapi.dll