J
Jenn
After weeks of troubleshooting an older vendor application that has
been hanging, the vendor has identified that the service that handles
connection pooling, etc. is being stopped. We are at the height of the
season for this application so we have two choices: 1)implement a new
service release by the vendor that fixes this situation (no on likes
this idea because of the timing) 2) based on what we see in the event
log, the service is being interrogated three times and then shuts down;
the vendor thinks we can disable the service that is doing the
interrogation as a temporary fix. He believes it to possibly be WMI
that is doing a check on all services and if it doesn't get a proper
response back, it shuts it off. Does this sound right? Would WMI do
this? Any help or thoughts would be greatly appreciated.
been hanging, the vendor has identified that the service that handles
connection pooling, etc. is being stopped. We are at the height of the
season for this application so we have two choices: 1)implement a new
service release by the vendor that fixes this situation (no on likes
this idea because of the timing) 2) based on what we see in the event
log, the service is being interrogated three times and then shuts down;
the vendor thinks we can disable the service that is doing the
interrogation as a temporary fix. He believes it to possibly be WMI
that is doing a check on all services and if it doesn't get a proper
response back, it shuts it off. Does this sound right? Would WMI do
this? Any help or thoughts would be greatly appreciated.