We have a VB6 application that uses a COM object to communicate with an email package. The app runs autonomously and every once in a blue moon the COM DLL seems to become unregistered. A quick call to RegSvr32 and the system is back to happy.
We tried implementing a quick fix that registers the DLL every time the application is going to need it, but that doesn’t seem to have worked.
This has become quite an annoyance.
In case you are wondering the app just calls a shell command.
Shell "regsvr32 /s " & """" & pathName & """"
Does anyone have a idea of what can cause a COM DLL to become unregistered?