Class not registered.

[miscellaneous]

Hi, firstly I am not a Delphi programmer. I have a Delphi reportserver application that was developed in in-house and we need to move it to another server. The problem is, it was developed by someone who has now left the company and whenever we try to run it on the other server, we get a popup error message that says:
Class not registered.

Now, according to the guy who made it, he said all you have to do is copy the folders from the old server to the new one and then register just one DLL.

I guess I am registering the DLL wrong? I just used regsvr32.exe and then the DLL name. Apparently it's supposed to create some registry entries. I could also copy the registry entry from the old server but I'm not sure what the IDs are. I think I can somehow extract this out of the DLL but I'm not sure how to do this and/or if this is even the right way to go about this.

If anyone has any pointers on how to fix this then it's greatly appreciated! Thanks.

 

[MagicFrisbee]

If you registered the server and got a message box saying that it was successfully registered, then I can only see one other problem: a dependency. What I think is happening is that this DLL is dependent on other COM objects or interfaces which are located in another DLL, or set of DLL's. Even though it's a report server, the dependency doesn't have to have anything to do with reporting. It may be a special ActiveX control, TCP/IP control, printing objects, etc. Sometimes that's even hard for the programmer to track down.

I would try doing some searches for programs that inspect files for their dependencies. I once had a program called DependencyLister which would list the DLL's and other files that a program would depend on, but I can't find it on the Internet right now.

GIS Programmer
City of Orem, UT

http://gis.orem.org

 

[miscellaneous]

Hi thanks for the reply.

Was it Dependency Walker that you were thinking of? Anyway I downloaded it and it does list the dependencies that the DLL requires however all dependencies seem to be satisfied.

It wouldn't have anything to do with the fact that one is Win2k (the one that works) and one is 2k3?

Maybe there are some other DLLs that need to be registered. There are a bunch of DLLs that are in the directory of our report server software but apparently they don't need to be registered. If I could compare registered DLLs from the old machine to the new one then that may be a starting point.