I have a Com + dll sitting on a sql server box that consists of 3 classes. I'm pretty damn sure that is correctly set up in component services as it was all working before yesterday when we installed a new version of it. when any of the client machines try to access this remote dll it works fine with the first two classes, but as soon as you try create a new instance of the third class, the front end (VB) completly bombs out with a "projectname has generated errors and will be shut down" error.
If I have the dll running locally on my dev box, all is fine, so the only thing I can think is that the class in question has been corrupted somehow on the server. does unregistering it (regsvr32 /U) and then manually going through the registry to remove any instances of it sound like a good idea? and if so, what do I need to be carefull about going through the registry (ie is there a specific set of cls id's and such I need to delete, and anything I should avoid.
Thanks
Ian
Reply With Quote