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.

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.



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

Backup IIS 7 setting

Backup is very important especially for a productive server. We shall learned to backup everything to avoid any data missing.

For some reason, you might want to change the IIS 7 setting and do not want to mess up the setting in case you have modify any setting incorrectly.

To done this, simply run your command prompt with administrator privilege.

1. Navigate to your Windows button and right click to the command prompt then select on the “Run as administrator”.
2. Run the command line, “%windir%\system32\inetsrv\appcmd add backup mickgenie” without quotation.
3. You should be found the folder C:\Windows\System32\inetsrv\mickgenie\ and your configuration file is stored.

Classic ASP script error messages are no longer shown in a Web browser by default

With IIS 7.x, ASP error is disabled by default. Hence, the web programmer will not know what is the detailed error from your scripting and the following error shown.

An error occurred on the server when processing the URL. Please contact the system administrator.

To work around this problem, you could set the detailed error through IIS or web.config file.

Method 1:

1. Open IIS or run inetmgr.
2. Click on the websites.
3. Click on the ASP icon.
4. Expand the Debugging Properties.
5. On Send Errors To Browser parameter set to True.

Method 2:

Open your web web.config file, add the following command.

<asp scriptErrorSentToBrowser="true" />

Method 3:

Run the following command to enabled from server end.

%windir%\system32\inetsrv\appcmd set config -section:asp -scriptErrorSentToBrowser:true

Why my 3GP file not serve by IIS?

By default, 3GP file extension is not understand and serve by the IIS, hence you might get the error as below when you try to browse to your 3GP file from your IIS web services engine.

The problem is IIS handler mapping do not have 3GP file extension format by default. To get this fixed, you could add the extension through the handler mapping from IIS 7.x.

Alternatively, you may run the following command to add the extension.

%windir%\system32\inetsrv\appcmd set config /section:staticContent /+"[fileExtension='.3gp',mimeType='video/3gpp']"