Discovery: Get-CimClass : A security package specific error occurred

[dmatasek-cdw]

Getting the above error when running discovery for a Windows server.  We have verified the Windows password and the firewall team insists that nothing is being blocked between the MID server and the target server.

However, we ARE able to properly discover Windows Servers in the same subnet as the MID server.  It is only when we cross out of the network boundary that we receive this error.

Full error is:

<results error="Get-CimClass : A security package specific error occurred. At C:\Program Files\Mid\ServiceNow MID Server XXXX_MID_1\agent\scripts\PowerShell\WMIFetch.psm1:421 char:20 + ... $reg = Get-CimClass -Namespace "root\default" -ClassName "StdReg ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (root\default:StdRegProv:String) [Get-CimClass], CimException + FullyQualifiedErrorId : HRESULT 0x80070721,Microsoft.Management.Infrastructure.CimCmdlets.GetCimClassCommand + PSComputerName : 10.75.1.24 " probe_time="3403" result_code="62">

<result error="Get-CimClass : A security package specific error occurred. At C:\Program Files\Mid\ServiceNow MID Server XXXX_MID_1\agent\scripts\PowerShell\WMIFetch.psm1:421 char:20 + ... $reg = Get-CimClass -Namespace "root\default" -ClassName "StdReg ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (root\default:StdRegProv:String) [Get-CimClass], CimException + FullyQualifiedErrorId : HRESULT 0x80070721,Microsoft.Management.Infrastructure.CimCmdlets.GetCimClassCommand + PSComputerName : 10.75.1.24 "/>

[Pratiksha]

you need to troubleshoot it from the mid server.  Login to your mid and use the command given in the article. it will ask you to enter the password. Use the same creds which you saved in servicenow. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116898

Please mark it helpful and accept the solution. 

[rakshitadgaonka]

@dmatasek-cdw Were you able to figure out what was causing this error ?