Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've just enabled ASP Classic on an IIS7 install on Windows 2008 and tried to move an ASP application previously running on IIS6 on Windows 2003 to the IIS7 server. I'm getting the following error:

Server object error 'ASP 0177 : 800401f3' 
Server.CreateObject Failed 
/Includes/SessionInclude.asp, line 3 

SessionInclude.asp line 3 is:

set Session = server.CreateObject("SessionMgr.Session2")

My first thoughts were that there were some permission issues or a DLL needed registering, but I would think that the SessionMgr being a basic function should already be registered as a default? Has someone ran into this issue before and would be able to shed some light on this issue? or the DLL I need to register?

share|improve this question

Your code is not using something that is built-in to ASP (hence the need to instantiate it like so). It is a replacement for the default ASP Session object that permits sharing of session state with ASP.NET. You apparently need to find the SessionMgr.dll (or SessionManager.dll) file and register it on the new server.

More info:

share|improve this answer
Good o'l DLL hell... – Mark Henderson Nov 22 '10 at 9:17
Managed to locate and register the appropriate DLLs and switched IIS to run in a 32-bit application pool. Have issues with ODBC drivers not being found even though they are there but that's another issue that I will through. Thanks for your help! – theblip Nov 23 '10 at 4:19
Glad to be of service! Don't forget to click the check mark next to my answer to select it as the solution! (we both get 'reputation' for that) – Andrew Barber Nov 23 '10 at 13:03
@Mark Henderson: We forget at times how easy we have it now, in the .NET world, I think! hehe – Andrew Barber Nov 23 '10 at 13:04

Can you try configuring the WebSite in Classic .NET AppPool and confirm if that helps. I would also run Process Monitor and check if there are any ACCESS DENIED or FAILURES.

Good thing is you also have Failed Request Tracing to assist you troubleshoot the issue.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.