« Previous Next »

• 10-28-2008, 2:33 PM

  ds12will Joined on 07-02-2007, 7:10 PM Posts 2	Create Object Error Reply Contact I have this dll installed on numerous ways the same way and this specific server the same steps are followed but I'm recieving the following error: Microsoft VBScript runtime error '800a01ad' ActiveX component can't create object: 'NCryptoCOM.NCrypto' /testncrypto.asp, line 9   If it's not necessarly the dll and maybe the server what should I look for? any ideas?

• 10-28-2008, 3:19 PM

  In reply to

  tomkmvp Joined on 03-20-2003, 6:27 AM Central NJ Posts 6,188	Re: Create Object Error Reply Contact Start here: http://classicasp.aspfaq.com/components/why-do-i-get-800401f3/800a01ad-errors.html Tom Kaminski IIS MVP http://mvp.support.microsoft.com/ http://blogs.iis.net/tomkmvp/ http://www.linkedin.com/pub/8/690/408 http://www.bluesrepublic.org/

• 03-18-2009, 8:41 PM

  In reply to

  rrubin128 Joined on 03-18-2009, 7:47 PM Posts 3

  Re: Create Object Error Reply Contact 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

  Tags: ASPiis6500 internal server errorasp classic

• 03-19-2009, 1:23 AM

  In reply to

  steve schofield Joined on 06-10-2002, 8:54 PM MI Posts 3,890	Re: Create Object Error Reply Contact Auditing and process monitor is where I usually start. http://weblogs.asp.net/steveschofield/archive/2008/03/07/detecting-permission-issues-using-auditing-and-process-monitor.aspx Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 03-19-2009, 8:04 AM

  In reply to

  tomkmvp Joined on 03-20-2003, 6:27 AM Central NJ Posts 6,188	Re: Create Object Error Reply Contact Let's step back a second - are you sure you even want to do that? http://classicasp.aspfaq.com/components/should-i-store-objects-in-session/application-scope.html Tom Kaminski IIS MVP http://mvp.support.microsoft.com/ http://blogs.iis.net/tomkmvp/ http://www.linkedin.com/pub/8/690/408 http://www.bluesrepublic.org/

• 03-19-2009, 11:29 AM

  In reply to

  rrubin128 Joined on 03-18-2009, 7:47 PM Posts 3

  Re: Create Object Error Reply Contact Steve: Thanks for the suggestion.  I've tried procmon and Auditing as you suggested.  I don't see anything, which steers me away from permissions. Tom: Thanks for the link and concern.  The DLL is actually a free threaded veneer around the same code base as our standalone application server code.  Concurrency has not been a problem with storing in the Application object.  It's used to initialize and manage the lifetime of the application server code which is required for Sessions when creating other related objects from the DLL. We've been running smoothly in this configuration since 2001.  I have however learned my lesson with the Session object and the resulting serialization of session requests.  Ouch. One more difference between the target server and existing servers: this is the first installation on a 64-bit OS.  The other servers have been 32-bit.  But doesn't the DLL load when calling regsvr32?  The regsvr32 was successful.

• 03-19-2009, 4:29 PM

  In reply to

  tomkmvp Joined on 03-20-2003, 6:27 AM Central NJ Posts 6,188	Re: Create Object Error Reply Contact I've always found it painful to mix 32 and 64.  Not sure what else to tell you at this point except you may want to open a support case. Tom Kaminski IIS MVP http://mvp.support.microsoft.com/ http://blogs.iis.net/tomkmvp/ http://www.linkedin.com/pub/8/690/408 http://www.bluesrepublic.org/

• 03-19-2009, 8:54 PM

  In reply to

  steve schofield Joined on 06-10-2002, 8:54 PM MI Posts 3,890	Re: Create Object Error Reply Contact Try putting the DLL and registering in the Wow folder. http://weblogs.asp.net/steveschofield/archive/2008/08/18/getting-cdonts-to-work-on-windows-server-2008-x64.aspx c:\windows\SysWOW64 Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 03-24-2009, 10:24 AM

  In reply to

  rrubin128 Joined on 03-18-2009, 7:47 PM Posts 3

  Re: Create Object Error Reply Contact Got it. My IIS6 server is running on Window 2003 64-bit.  Hence, the w3wp processes and ASP dll are also 64-bit.  I was attempting to CreateObject() from a 32-bit DLL.  No can do. Even though I read that iis7 will allow you to define 32- vs 64-bit by Application Pool, on iis6 it's apparently all or nothing.  I'm lucky here: we're only running a single app on this web server. Here's what we did: Set W3SVC/AppPools/Enable32bitAppOnWin64 = true in the metabase Use C:\Windows\Microsoft.Net\Framework\v2.0.50727\aspnet_regiis.exe to register the 32-bit versions of ASP.NET instead of the 64-bit versions that were installed Even though our app is Classic ASP, this .NET version change (to 32-bit) got things working.  I don't know how useful this solution will be to others, but it got us over the hump.  It's encouraging to know that IIS7 will support mixing of 32-bit and 64-bit Application pools.  By the time we upgrade to IIS7, we'll probably have a 64-bit app too. Robert