Error 800a01ad trying to instance COM component from ASP.NET on II



I have an ASP.NET 2.0 web service that runs on IIS and calls a VB6 dll which
has been registered with COM+.

The web service runs fine on all the servers that it has been installed on.
However, on a couple of servers, one is Windows 2000 and then other Windows
2003, if the server is restarted then when the web service tries to access
the dll, it reports the following error:

'Creating an instance of the COM component with CLSID {...} from the
IClassFactory failed due to the following error: 800a01ad'

All I have to do to clear the problem is run iisreset and it will be fine
until the next server restart.

Does anyone know why this is occuring and how to prevent it?




Walter Wang [MSFT]


Based on my understanding, you're experiencing some non-reproducible errors
which only exist on some of your servers.

Error 0x800a01ad means "ActiveX cannot create object", normally it's
because the the component is not correctly registered, required dll is
missing, or not accessible because of security settings. However, you
mentioned that doing iisreset will fix it, I doubt that it's one of these

I've searched in our support case database but didn't find any known issues
regarding such scenario.

Have you tried to set the IIS service's startup type to "Manual" and start
it manually after the server is restarted? If this fix the problem, this
might be a service startup order issue.

Based on my experience, troubleshooting such non-reproducible and
complicated issue is really not very appropriate and efficient in
newsgroup, if it's critical for your business, I suggest you contact
Microsoft Customer Support and Service for more prompt and efficient help.

Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

Get notification to my posts through email? Please refer to
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at

This posting is provided "AS IS" with no warranties, and confers no rights.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question