I am getting the following error in my regular ASP VB script section when I use the line
Server.CreateObject("dll name")

Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object

The dll I am using is registered on the server with no errors when doing so.

Does anyone know what can be done to fix the problem? Please can someone help.

Server is Win2003 64 bit SP 2

You can't simply create the object; you have to "assign" it to an object variable.

Example

Yes I know that, and I have done so ie:
Set obj = Server.CreateObject("DBExec.CExec")

The part that is falling over is the Server.CreateObject, that is why I only mentioned that part.

Where did you get this component?

Its possible you are trying to use a component that was not designed to be called in this manor.

The component works well on other servers. The only difference now is that the server I am trying to get this to work on is a Win 2003 x64, where the other had been Win 2000 x86, can this be the problem and if so is there a way for the object to work on a 64 bit server?

did you run the latest Mdac version think you need the 2.8 version

see allso :

http://msdn2.microsoft.com/en-us/library/ms945464.aspx

http://sleepyhead81.*************/200...ection-in.html

As far as I can establish the server does have the latest MDAC.

The component is a Microsoft component and the description of the component when looking at the properties is Help Desk Sample DB Executive Components

Are you able to create other objects (dll)

Otherwise see if you got the rights to call to the dll

I am able to create other objects and did have rights to the dll and in the end, a very long day yesterday, rewrote everything with a dll that would work and do what I needed. Thanks to all for your suggestions.

Very strange, the problem just went away after numerous reboots.....very strange.

You know you need to fix activex error when you see the message runtime error 800a01ad activex. So, you must check the health of your registry and do the necessary repairs. However, you should be knowledgeable on computers so you do not make things worse. Then again, you can always download a registry cleaner to clean up your registry. Just make sure that you get it from a reliable source.

Registry is fine, done a check. What I do not understand is how can it not work on one machine and on another, same specced, machine at the same time it does work? And the code is associated with the Session Variables.