When using the Microsoft.XMLHTTP component, my ASP script hangs

All application pools run in 32-bit mode for the highest level of compatibility on our Windows 2008 64-bit servers. While most ASP components are only available in 32-bit mode, the Microsoft.XMLHTTP is available on these servers only in 64-bit mode.

One way to resolve this issue is to ask the support staff to change your application pool to 64-bit mode. However, this has proven to break other parts of the application as many ASP components do not have a 64-bit version available. A workaround to this issue is to alter your script to use the Msxml2.ServerXMLHTTP or MSXML2.ServerXMLHTTP.4.0 components which are available in 32-bit mode.

Please contact our support if you have further questions in regards to this issue.


  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

I am receiving System.Security.SecurityException or That assembly does not allow partially trusted callers.

When running your application you may see: That assembly does not allow...

How can I redirect one URL to another on ASP .NET?

Our ASP plans have the following installed:...

Cryptography with ASP .NET

A customer received the following error when attempting to create a RSACryptoServiceProvider from...

I am getting a 404 error on the secondary pages of my MVC application. Why?

To resolve the 404 error issues on secondary pages of a ASP .NET MVC applications, you will need...

My site is showing the following error: HTTP Error 503. The service is unavailable.

The error HTTP Error 503. The service is unavailable. generally means that your application pool...