What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Microsoft SQL Server 2016 (8004100E: The namespace specified could not be found)

Votes:

0

We just set up PRTG to evaluate it. Added a SQL Server and after enabling WMI firewall rules, the auto-discovery worked fine and added a few sensors.

However, when we try to manually add the WMI Microsoft SQL Server 2016 sensor, we get the error:

8004100E: The namespace specified could not be found

Version is PRTG Network Monitor 22.3.79.2108 x64 running on Windows Server 2019 Datacenter

prtg sql wmi

Created on Sep 22, 2022 3:17:16 PM



8 Replies

Votes:

0

Hello,

each SQL server version uses a different WMI namespace. The question would be if the SQL Server 2019 does work, or not.

Created on Sep 23, 2022 2:05:37 PM by  Arne Seifert [Paessler Support]



Votes:

0

Hi, I have tried 2014, 2016 and 2019 sensors, they all throw the same error. The actual SQL version on the server is 2016.

Created on Sep 23, 2022 2:53:25 PM



Votes:

0

Hello,

for checking, please use the WMI Tester, and set the namespace to root\Microsoft\SqlServer\ComputerManagement13

Then, use the tab "Advanced" to paste this custom query:

SELECT ServiceName, DisplayName FROM SQLService WHERE SQLServiceType = 1

Do you get a result table or an error?

Created on Sep 26, 2022 2:16:32 PM by  Arne Seifert [Paessler Support]



Votes:

0

Hi, I just completed this test and get the exact same error as mentioned above

Created on Sep 26, 2022 2:38:23 PM



Votes:

0

Hello,

in that case, the sensor cannot work, and the issue cannot be fixed through PRTG.

Please check if you can repair the WMI instances.

Created on Sep 26, 2022 3:37:01 PM by  Arne Seifert [Paessler Support]



Votes:

0

So I used the following command to see the actual namespaces containing *SqlServer*:

Get-WMIObject -Namespace root -ClassName *SqlServer* -list -recurse -EA 0

Turns out, the namespace we have on this server is ComputerManagement14, not 13 as mentioned above:

root\Microsoft\SqlServer\ComputerManagement14

Using that namespace in the utility, it works. So can the sensor be forced to use that namespace instead?

Created on Sep 28, 2022 2:26:42 PM

Last change on Sep 29, 2022 6:11:28 AM by  Felix Wiesneth [Paessler Support]



Votes:

0

So it turns out it was SQL 2017 on that server, and that sensor does work.

We have a SQL 2014 Server and that sensor still doesn't work, but we the error:

"The specified class is not valid"

Created on Sep 28, 2022 2:43:39 PM



Votes:

0

Hello,

for this please copy the ServiceName property, then change the namespace back to root\cimv2 and run:

SELECT Name, UserConnections, LoginsPersec, Timestamp_Perftime , Frequency_PerfTime, LogoutsPersec FROM Win32_PerfRawData_ServiceName_SqlServerGeneralStatistics

"ServiceName" has to be replaced with the actual name.

Does that work?

Created on Sep 29, 2022 1:26:46 PM by  Arne Seifert [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.