ActiveX Issue on New Server

We recently migrated server and have an automated task setup. When we attempt to run it, we get this:

activex component can't create object

We're having a tough time cause we don't have the source code. Any ideas?

That error means that something is not installed (or at least not properly). It might be a .DLL that was provided with the program, a 'common' DLL, or an entire application like Excel.

To have any idea whatsoever what it might be, you need to know what the application needs... not having the code certainly doesn't help with that.

Note that if you have an installation package for the application, it is likely to contain the item.

Thanks for the reply. I know, not having the code makes it nearly impossible. I did try things like Process Monitor and Process Explorer to see if they would list the required dlls, but it's still difficult to figure out what's going on.

I did think about running the task from another server to see if that would work. It uses a DSN to connect to the server, but there's one drawback. The connection string in the code (I believe) is this:

Code:

---

    Dim objConn As New ADODB.Connection
    objConn.open "dsn=name;"

---

So if I try a sql server odbc connection with the sql login credentials on a separate server, it says login for user '' failed. Any suggestions would be appreciated.

If the item is early bound (using the References/Components menus in VB) then you can use a Dependency checker application to find out what it is. I think there is one on the VB CD.

As for the DSN issue I have no idea, otherwise I would have replied to your separate thread on the subject.

Ok I'll look around for that Dependency checker application. Thanks for the suggestion, I appreciate the help.