Is it possible of creation object 

"Microsoft.XMLHTTP" in windows 2008 server 64 bit?

Dani AI

Generated

Yes — creating an XMLHTTP COM object on Windows Server 2008 x64 is possible. The common pitfalls are bitness mismatches and using an unversioned or client-only ProgID. As hinted, IIS settings can block creation; and is correct that it can work — but use an explicit server-side ProgID and check your process bitness.

Use a versioned, server-safe ProgID and avoid legacy client aliases. For Classic ASP the recommended pattern is:

Set xhr = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")
xhr.open "GET", "http://example.com", False
xhr.send
Response.Write xhr.status

Notes and troubleshooting checklist:

  • Prefer MSXML2.ServerXMLHTTP.6.0 (uses WinHTTP, suited for server apps). MSXML2.XMLHTTP.6.0 is the versioned XMLHTTP; unversioned names are ambiguous.
  • If you see "ActiveX component can't create object" or "Class not registered", you have a registration or bitness mismatch. On x64 Windows there are separate registries for 32-bit and 64-bit COM objects.
  • Check the IIS application pool: if the code needs a 32-bit COM, set the Application Pool's "Enable 32-Bit Applications" appropriately. If you need 64-bit, leave it off.
  • To re-register MSXML6 manually (if needed), run the appropriate regsvr32 for the bitness you need (System32 for 64-bit, SysWOW64 for 32-bit).
  • Ensure the app pool identity has outbound network permissions and that firewall/proxy settings allow the request.
  • For new development on the server platform, prefer native APIs (.NET HttpClient) or versioned MSXML ServerXMLHTTP. Avoid relying on legacy client objects.

This addresses the IIS/bitness gap behind 's suggestion and expands on how to make creation reliable on 64-bit Server 2008.

You may have to enable it in IIS Admin

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.