Connection failed (Cannot Connect)

qcjims

after some time I start getting these errors:

3 Dec 2010 11:52 AM WMI GetInstances: root\cimv2 select Name,State,StartMode from Win32_Service Cannot connect COMException

and then monitoring for a server stops.

I also see these errors all the time:

3 Dec 2010 11:52 AM WMI GetInstances: root\cimv2 select Handle,CreationDate,ProcessId from Win32_Process where CreationDate = '20101203195242.588801+000' and ProcessId = 8196 Cannot connect ManagementException Out of memory

Chris Spencer

Hi

We have a help page dedicated to troubleshooting our various data collection methods. It's worth trying the 'Testing WMI' section for any servers that are getting this problem. This should highlight whether it's a configuration issue or not.
http://www.red-gate.com/supportcenter/C ... 269935.htm

Hope this helps
Chris

hbuckner

What Server OS are you getting theese errors on? Windows Server 2008 R2 has a win32_service memory leak with that error. Look in the server logs and see if you see any wmi exceptions.

I can point you to a Microsoft hotfix if it is the same OS.

qcjims wrote:

after some time I start getting these errors:

3 Dec 2010 11:52 AM WMI GetInstances: root\cimv2 select Name,State,StartMode from Win32_Service Cannot connect COMException

and then monitoring for a server stops.

I also see these errors all the time:

3 Dec 2010 11:52 AM WMI GetInstances: root\cimv2 select Handle,CreationDate,ProcessId from Win32_Process where CreationDate = '20101203195242.588801+000' and ProcessId = 8196 Cannot connect ManagementException Out of memory

qcjims

yes it is win2k8 R2. i'll check for the KB article on the memory leak, but in case I can't find it please post the information you have. thanks.



-js

hbuckner

Here is a blog on the issue.


http://brooke.blogs.sqlsentry.net/2010/ ... -leak.html

http://blogs.technet.com/b/kevinholman/ ... gents.aspx

Here is the hotfix.

http://support.microsoft.com/kb/981314

qcjims wrote:

yes it is win2k8 R2. i'll check for the KB article on the memory leak, but in case I can't find it please post the information you have. thanks.



-js

qcjims

THanks Harold.

I grabbed that hotfix and have it applied. We'll see if the error goes away, but it definitely looks to be a match.

I also ran across this WMI memory leak article. http://support.microsoft.com/kb/977357



-js