Re: Create Object Error

rrubin128 — Thu, 19 Mar 2009 00:41:37 GMT

I'm still stuck. I am attempting to instantiate a custom object via Server.CreateObject( "ISDBCom.ISDBManager" ) in the Application_onStart in global.asa. This is working on several other Windows Server 2003 installations. I haven't figured out what's different about this one. I'm getting:

Microsoft JScript runtime error '800a01ad'
Automation server can't create object

The DLL is present, and regsvr32'ed successfully. Possibilities:

File system security related. I've used procmon in the past to troubleshoot file access issues. Using procmon, I see the ProcID is found in the registry. But I don't see where w3wp.exe even attempts to open the DLL. I do see the OPEN on the working servers. I've tried running the AppPool as "Local System", but it still fails.
Not all dependent components are present. Depends.exe returns similar results on both the working and non-working installations. If dependencies are missing will I even see an attempted open via procmon?

Any other troubleshooting ideas? Thanks in advance.

Robert

Script Time Out with no source

kmwise — Mon, 16 Mar 2009 14:37:35 GMT

I get the following error in my application log but can't figure out the source?

Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date:  3/16/2009
Time:  1:22:38 AM
User:  N/A
Computer: My Web Server

Description:
Warning: IIS log failed to write entry, Script timed out. The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools..

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Search results matching tags 'ASP Classic' and 'iis6'

Re: Create Object Error

Script Time Out with no source