April 2, 2002 at 11:58 am
I just hope that someone in the DMO section is familiar with this issue.
Our programmers wrote a COM module to access a database. Whenever they need to install an updated version of the COM module they have to stop the server, install the Com object, and restart the server. Not good for a production server. Does COM+ have the same limitation?
Bill
April 2, 2002 at 1:56 pm
Yes, it is the registry entries that cause this. And once the file is in use the OS won't let it go until process using it stops. I have not seen any COM product that doesn't use the registry.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 10, 2002 at 8:34 pm
Is the COM module running in a sql job? If so try stoping the Sql Server Agent, upgrade the COM module then re-start Sql Server Agent
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply