Home / ASP

• Enable ASP Pages
• Turn on script executing
• Permit editing of metabase.xml
• The most commonly encountered problems
• Some additional links on this issue

Enable ASP Pages

By default ASP Pages are disabled. When you initially install IIS, the service is installed in a highly secure mode. ASP feature does not work unless enabled. If you do not enable this functionality after installing IIS, IIS returns a 404 error. You can serve dynamic content and enable these features through the Web Service Extensions node in IIS Manager.

Turn on script executing

You can create a virtual directory through IIS Manager or by using Windows Explorer.

For security reasons, when selecting access permissions, consider allowing only the default Read permission. Under Allow the following permissions you should select Run Scripts check box to prevent possible problems.

Permit editing of metabase.xml

To make the Metabase.xml file write-able, you need to go through the following steps:

• Go to the IIS control panel
• Right-click the server
• Select properties
• Check off the box that says "allow changes to MetaBase configuration while IIS is running".

The most commonly encountered problems:

• IIS 6: Cannot attach file "Operation Not Allowed"

In IIS 6.0, the ASPMaxRequestEntityAllowed value determines the maximum size POST to the website. If it isn't set high enough, it will prevent you from uploading files.

To solve this problem you have to change the ASPMaxRequestEntityAllowed to 1073741824 in the metabase.xml file (usually located in c:\windows\system32\inetsrv)

• IIS 6: Cannot open attachment "Response Buffer Limit Exceeded"

If you get the above error when you click on an attachment, the attachment is larger than IIS is configured to allow. Change the AspBufferingLimit setting in Metabase.xml to a larger size. The default value is 4194304, which is about 4 MB. Change this to whatever limit is reasonable for the types of files your users will be attaching.

• Application loses session variables sporadically.

This appears to be a common Windows 2003 IIS problem. Usually you have to do the following:

• In IIS Manager, expand the local computer
• Expand Application Pools
• Right-click the application pool
• Click Properties
• Flip to the Performance tab
• Under Web garden, in the Maximum number of worker processes box, type 1
• Click Ok

Some additional links on this issue:

 http://blogs.msdn.com/david.wang/archive/2005/09/19/Why_do_I_lose_ASP_Session_State_on_IIS6.aspx http://www.aspplayground.net/forum/m_385297/tm.htm
 http://www.experts-exchange.com/Web/Web_Languages/ASP/Q_21566348.html
http://support.microsoft.com/default.aspx?kbid=303881
http://support.microsoft.com/default.aspx?scid=kb;en-us;173307
 http://support.microsoft.com/default.aspx?scid=kb;en-us;281298

Back to top