WMI is broken

[Guest]

I posted this earlier today on the Configuration and Management area, but
no-one there seems to have any intention of responding. This is a fairly
urgent matter that I need to resolve sooner rather than later.

I have been trying to start a SQL server 2005 instance and kept running into
what appears to be a WMI issue.

I am running on a WinXP SP2 PC (recently upgraded from Win2k Pro SP4).

When I select Properties in the WMI Control connector in Computer
Management, I see displayed the following message in the General tab in the
dialog box:-

Failed to connect to <local computer> because "Win32: Access is denied"

None of the remaining tabs on this dialog box are accessible.

When I select the "SQL Server Configuration Manager" connector in Computer
Management I see that the Connection failed with the explanation "Cannot
connect to the WMI provider. You do not have permission or the server is
unreachable."

Does anyone have any suggestions that would help me correct these issues?

 

[Kerry Brown]

I don't know the answer but you may want to try the sql groups. There are
many of them so I'm not sure which is the best one for your question. They
are microsoft.public.sqlserver.*

 

[Guest]

Kerry

Thanks for replying. However, having looked at the SQL Server groups, I am
convinced that the answer does NOT lie there. The WMI problem I am
experiencing is causing the issue with SQL Server and NOT the other way
around. If I can correct the issue with WMI, I am sure that the SQL Server
issue will go away.

I have rebuilt the WMI service following the instructions in
http://windowsxp.mvps.org/repairwmi.htm, but this has NOT corrected the
problem.

I am beginning to believe that I will have to completely reinstall WindowsXP
to mend this problem, something that I do not want to do, as I have then to
reinstall a lot of applications.

Hopefully, someone here will be able to point me in the right direction.

 

[Ramesh, MS-MVP]

Chris,

See if this helps.

Technical Weblog of Eric Charran : SQL Server 2005 WMI Provider Error:
http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Kerry

Thanks for replying. However, having looked at the SQL Server groups, I am
convinced that the answer does NOT lie there. The WMI problem I am
experiencing is causing the issue with SQL Server and NOT the other way
around. If I can correct the issue with WMI, I am sure that the SQL Server
issue will go away.

I have rebuilt the WMI service following the instructions in
http://windowsxp.mvps.org/repairwmi.htm, but this has NOT corrected the
problem.

I am beginning to believe that I will have to completely reinstall WindowsXP
to mend this problem, something that I do not want to do, as I have then to
reinstall a lot of applications.

Hopefully, someone here will be able to point me in the right direction.

 

[Guest]

Ramesh

Thanks for your response.

Unfortunately, as I said previously, this does NOT appear to be related to
SQL Server. It is WMI that is at fault. As a result, SQL Server does NOT work
properly. I tried to uninstall SQL Server and Windows refused to do even this
simple task because WMI was broken.

This problem is preventing me from installing a new program which depends
upon SQL Server and it is becoming more evident that I am going to have to
re-image this PC and then reinstall ALL the existing applications just to get
WMI working. That does seem to be OVERKILL, which in my understanding is
UNACCEPTABLE.

Can someone who has some understanding of WMI here please explain what I
have to do to repair the WMI application?

--
--
Chris Jones

Chris,

See if this helps.

Technical Weblog of Eric Charran : SQL Server 2005 WMI Provider Error:
http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


Kerry

Thanks for replying. However, having looked at the SQL Server groups, I am
convinced that the answer does NOT lie there. The WMI problem I am
experiencing is causing the issue with SQL Server and NOT the other way
around. If I can correct the issue with WMI, I am sure that the SQL Server
issue will go away.

I have rebuilt the WMI service following the instructions in
http://windowsxp.mvps.org/repairwmi.htm, but this has NOT corrected the
problem.

I am beginning to believe that I will have to completely reinstall WindowsXP
to mend this problem, something that I do not want to do, as I have then to
reinstall a lot of applications.

Hopefully, someone here will be able to point me in the right direction.