Discussion:
MS SQL Server management pack failed
(too old to reply)
Will
2007-06-11 14:35:01 UTC
Permalink
After upgrading from WSUS v2 to v3 MOM is complaining with the following
message: The "Microsoft SQL Server" management pack failed to execute the SQL
Server 2005 Service Availability script successfully. The following error
event was returned "Unable to open WMI Namespace
'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagement'.
Check to see if the WMI service is enabled and running, and ensure this WMI
namespace exists.".

Any suggestions?
--
Will Wesley
Anders Bengtsson
2007-06-11 19:35:31 UTC
Permalink
Hi Will,

Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?

---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se

W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W> 'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagemen
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Will
2007-06-11 20:02:02 UTC
Permalink
Thanks for your response. I actually found a simple solution that has worked
for me. Because the the database was upgraded to the Windows Internal
Database, MOM started to recognize the server as having SQL 2005 installed. I
then performed a clean install of WSUS v3 in a lab environment and noticed
that the namespace for SQL was also missing.

So in short, I used the MOM Admin Console to located the event rules
(Microsoft SQL Server -> SQL Server 2005 -> State Monitoring and Services
Discovery) and enabled "rule-disable overrides" for this rule which allowed
me to specify which server(s) to exclude from receiving alerts.

This turned out to be just a reporting nuisance...the installation was
smooth and WSUS is currently running with no issues.
----
Will Wesley
Post by Anders Bengtsson
Hi Will,
Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W> 'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagemen
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Nico
2007-08-21 11:56:03 UTC
Permalink
Post by Will
Thanks for your response. I actually found a simple solution that has worked
for me. Because the the database was upgraded to the Windows Internal
Database, MOM started to recognize the server as having SQL 2005 installed. I
then performed a clean install of WSUS v3 in a lab environment and noticed
that the namespace for SQL was also missing.
So in short, I used the MOM Admin Console to located the event rules
(Microsoft SQL Server -> SQL Server 2005 -> State Monitoring and Services
Discovery) and enabled "rule-disable overrides" for this rule which allowed
me to specify which server(s) to exclude from receiving alerts.
This turned out to be just a reporting nuisance...the installation was
smooth and WSUS is currently running with no issues.
----
Will Wesley
Post by Anders Bengtsson
Hi Will,
Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W> 'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagemen
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Nico
2007-08-21 12:10:03 UTC
Permalink
I had the same problem, and created an attribute "WSUS Server" to recognise
WSUS servers using key SOFTWARE\Microsoft\Update Services and then removing
them in the formula for Microsoft SQL Server 2005 like so:

(AttributeValue(Microsoft SQL Server 2005) OR MemberOf(Microsoft SQL Server
2005 Discovered Group)) AND (NOT (AttributeValue(Virtual Server Type) OR
AttributeValue(IsHostingMSCS)) Or MatchRegEx(AttributeValue(Virtual Server
Type), "(^|,)SQL[ ]Server(,|$)")) AND (NOT AttributeValue(WSUS server))

It looks like a bug in the management pack though as the reg key used to
identify SQL 2005 also exists for WSUS.
Post by Will
Thanks for your response. I actually found a simple solution that has worked
for me. Because the the database was upgraded to the Windows Internal
Database, MOM started to recognize the server as having SQL 2005 installed. I
then performed a clean install of WSUS v3 in a lab environment and noticed
that the namespace for SQL was also missing.
So in short, I used the MOM Admin Console to located the event rules
(Microsoft SQL Server -> SQL Server 2005 -> State Monitoring and Services
Discovery) and enabled "rule-disable overrides" for this rule which allowed
me to specify which server(s) to exclude from receiving alerts.
This turned out to be just a reporting nuisance...the installation was
smooth and WSUS is currently running with no issues.
----
Will Wesley
Post by Anders Bengtsson
Hi Will,
Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W> 'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagemen
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Anders Bengtsson
2007-08-21 13:05:00 UTC
Permalink
Hi Nico,

If you think you have found a bug, please report it to Microsoft, http://connect.microsoft.com/site/sitehome.aspx?SiteID=209


-----
Regards
Anders Bengtsson
Microsoft MVP - MOM
http://www.contoso.se


N> I had the same problem, and created an attribute "WSUS Server" to
N> recognise WSUS servers using key SOFTWARE\Microsoft\Update Services
N> and then removing them in the formula for Microsoft SQL Server 2005
N> like so:
N>
N> (AttributeValue(Microsoft SQL Server 2005) OR MemberOf(Microsoft SQL
N> Server 2005 Discovered Group)) AND (NOT (AttributeValue(Virtual
N> Server Type) OR AttributeValue(IsHostingMSCS)) Or
N> MatchRegEx(AttributeValue(Virtual Server Type), "(^|,)SQL[
N> ]Server(,|$)")) AND (NOT AttributeValue(WSUS server))
N>
N> It looks like a bug in the management pack though as the reg key used
N> to identify SQL 2005 also exists for WSUS.
N>
N> "Will" wrote:
N>
Post by Will
Thanks for your response. I actually found a simple solution that has
worked for me. Because the the database was upgraded to the Windows
Internal Database, MOM started to recognize the server as having SQL
2005 installed. I then performed a clean install of WSUS v3 in a lab
environment and noticed that the namespace for SQL was also missing.
So in short, I used the MOM Admin Console to located the event rules
(Microsoft SQL Server -> SQL Server 2005 -> State Monitoring and
Services Discovery) and enabled "rule-disable overrides" for this
rule which allowed me to specify which server(s) to exclude from
receiving alerts.
This turned out to be just a reporting nuisance...the installation was
smooth and WSUS is currently running with no issues.
----
Will Wesley
Post by Anders Bengtsson
Hi Will,
Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W>
'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManageme
n
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Nico
2007-08-21 13:16:00 UTC
Permalink
I told my TAM :)
Post by Anders Bengtsson
Hi Nico,
If you think you have found a bug, please report it to Microsoft, http://connect.microsoft.com/site/sitehome.aspx?SiteID=209
-----
Regards
Anders Bengtsson
Microsoft MVP - MOM
http://www.contoso.se
N> I had the same problem, and created an attribute "WSUS Server" to
N> recognise WSUS servers using key SOFTWARE\Microsoft\Update Services
N> and then removing them in the formula for Microsoft SQL Server 2005
N>
N> (AttributeValue(Microsoft SQL Server 2005) OR MemberOf(Microsoft SQL
N> Server 2005 Discovered Group)) AND (NOT (AttributeValue(Virtual
N> Server Type) OR AttributeValue(IsHostingMSCS)) Or
N> MatchRegEx(AttributeValue(Virtual Server Type), "(^|,)SQL[
N> ]Server(,|$)")) AND (NOT AttributeValue(WSUS server))
N>
N> It looks like a bug in the management pack though as the reg key used
N> to identify SQL 2005 also exists for WSUS.
N>
N>
Post by Will
Thanks for your response. I actually found a simple solution that has
worked for me. Because the the database was upgraded to the Windows
Internal Database, MOM started to recognize the server as having SQL
2005 installed. I then performed a clean install of WSUS v3 in a lab
environment and noticed that the namespace for SQL was also missing.
So in short, I used the MOM Admin Console to located the event rules
(Microsoft SQL Server -> SQL Server 2005 -> State Monitoring and
Services Discovery) and enabled "rule-disable overrides" for this
rule which allowed me to specify which server(s) to exclude from
receiving alerts.
This turned out to be just a reporting nuisance...the installation was
smooth and WSUS is currently running with no issues.
----
Will Wesley
Post by Anders Bengtsson
Hi Will,
Is TPSESCMSRSS243 your WSUS server? Could it be to many connection against
it at the same time?
Also check the local event viewer for events. It it generating all the time?
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
W> After upgrading from WSUS v2 to v3 MOM is complaining with the
W> following message: The "Microsoft SQL Server" management pack failed
W> to execute the SQL Server 2005 Service Availability script
W> successfully. The following error event was returned "Unable to open
W> WMI Namespace
W>
'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManageme
n
W> t'. Check to see if the WMI service is enabled and running, and
W> ensure this WMI namespace exists.".
W>
W> Any suggestions?
W>
Gé Brander
2007-11-05 14:21:02 UTC
Permalink
Hi Will,

Did you solve this problem?

We are having the same problem here now.

Gr. Gé
Post by Will
After upgrading from WSUS v2 to v3 MOM is complaining with the following
message: The "Microsoft SQL Server" management pack failed to execute the SQL
Server 2005 Service Availability script successfully. The following error
event was returned "Unable to open WMI Namespace
'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagement'.
Check to see if the WMI service is enabled and running, and ensure this WMI
namespace exists.".
Any suggestions?
--
Will Wesley
b33zy
2007-12-13 16:54:05 UTC
Permalink
Same problem here as well. We opened a case with Microsoft support and they
are not interested in resolving the problem. WSUS install of SQL Express does
not create the namespace for some reason. I think Microsoft has the problem
fixed with their next version of WSUS and that is why they aren't fixing it.

don't quote me on that though ;)
Post by Anders Bengtsson
Hi Will,
Did you solve this problem?
We are having the same problem here now.
Gr. Gé
Post by Will
After upgrading from WSUS v2 to v3 MOM is complaining with the following
message: The "Microsoft SQL Server" management pack failed to execute the SQL
Server 2005 Service Availability script successfully. The following error
event was returned "Unable to open WMI Namespace
'winmgmts:\\TPSESCMSRSS243\root\Microsoft\SqlServer\ComputerManagement'.
Check to see if the WMI service is enabled and running, and ensure this WMI
namespace exists.".
Any suggestions?
--
Will Wesley
Loading...