Skip to main content

How to throw error to browser (client) for classic ASP?

Because of security concerns, IIS 7.0 has since turned off ASP's default behavior of sending script errors (including line number and code snippet to the browser. A generic error is now shown on browser for classic ASP, something like this:
An error occurred on the server when processing the URL. Please contact the system administrator.
To revert back to earlier IIS behaviour, do this on command prompt (Administrator rights may be required):

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

cscript adsutil.vbs set w3svc/AspScriptErrorSentToBrowser true
Hope this is helpful.

Popular Posts

Ho Ching named 5th most powerful and is mistaken as first lady by Forbes

Forbes named Singapore Prime Minister wife and CEO of Temasek Holdings, Ho Ching, as the 5th most powerful woman in the world. Ho Ching is mistaken as Singapore's first lady! OMG!

I wonder how can Forbes makes such a blunder. For a complete list, refer to here.

How to stop FortiClient from starting automatically?

Installed FortiClient recently but the challenge in disabling the application/service from running automatically on every start-up annoyed me. Attempt to stop 'FortiClient Service Scheduler' only return 'Parameter is incorrect' error message.

An article on Technet help solve my trouble. To stop FortiClient from starting automatically, try the following:
Shut down FortiClient from the system tray.
Run net stop fortishield on command prompt.
Run msconfig.
On msconfig, switch to the Services tab. Clear the FortiClient Service Scheduler check box and click Apply.Run services.msc on command prompt to open up show all available services.Look for FortiClient Service Scheduler. Switch Startup type to Manual.Restart your computer. FortiClient should not be running automatically the next time round. Hope it helps.

Photo of NSman carrying field pack himself is fake

Read more on Stomp [via]