Strange WMI error with Management Studio

Question

Strange WMI error with Management Studio

alen teplitsky

SSC-Dedicated

Points: 30014
More actions
May 9, 2007 at 7:32 am

#116900

I had this on two servers in the last few days. You can't connect with Management Studio, but you can run queries against the server and applications didn't lose connection.
Restarting WMI service fixed it.
The following is from the Error log but nothing written to the Windows Event logs. Has anyone else experienced this?
Date5/8/2007 7:10:01 PM
LogSQL Agent (Current - 5/8/2007 7:10:00 PM)
Message
[298] SQLServer Error: 22001, Error executing extended stored procedure: Invalid Parameter [SQLSTATE 42000] (ConnExecuteCachableOp)

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

MicMac Grasshopper Points: 17 More actions · Answer 1

Exactly same problem here... on both nodes on cluster servers.

Restarting WMI service resolved the problem. Does anybody know, what is the root cause to this problem? Is it expected that this will happen regularly? Any fixes to this issue?

alen teplitsky SSC-Dedicated Points: 30014 More actions · Answer 2

so far this has happened only one one server. it's a clustered instance. both nodes. funny thing is that when i first saw this we had 2 instances on the cluster. we took one instance off to make a new cluster. problem stayed with the instance and pops up once a month or so.

we are going to migrate this instance to a new cluster soon and will watch it.

lynetteb Newbie Points: 4 More actions · Answer 3

I know this question was posted a year ago, but I am hoping the solution I found helps someone (especially since Microsoft's recommendation is was to upgrade and patch the O/S, then upgrade and patch SQL Server--- a lengthy process which would not have fixed my issue.)

In my case, the BUILTIN\Administrators group had been removed from the instance Logins, but the SQL Server services were still running under the LocalSystem account. I changed the SQL Services so that they started under an account with sysadmin privileges on the instances (as well as server Administrator). Then, I shut down the SQL Server services. I had to reboot the server as well. Once the server was rebooted and the services running again, the problem was resolved.