I recently had this common error message while working with WCF, entity frame work and SQL server.
Experienced asp.net developers maybe recognise this straight away as a connection string problem, but to me it wasn’t that obvious. On my travels I can across a great resource about connection strings, that is worth checking out if you’re new to microsoft development, or of you’re stuck on a possible connection string problem.
Today I’ve been trying to instantiate an asp.net component from classic ASP using a Server.CreateObject, but I kept getting an error:
Microsoft VBScript runtime error ‘800a01ad’
ActiveX component can’t create object
This ranks up there with some of my most frustrating times, so I have to share this in case anyone else has this problem. I’m running iis 7 and the solution is to select advanced properties of your application pool and set Enable 32-Bit Applications to True. Some people had suggested that Managed Pipeline might need to be changed to ‘Classic’, so that might be another thing to try should your problem persist.
