I'm getting a warning while running discovery the CI which is getting this warning is also getting updated to the CMDB as well needed resolution.

Aayush Jain1
Kilo Contributor

The CI is also getting updated but finding this warning in discovery logs 

 Command [snc-decode-command JiB7IGV4ZWN1dGVXTUlSdW5uZXIgLXVzZVRhcmdldFBvd2VyU2hlbGwgJHRydWUgLXdtaUZldGNoRGF0YSAnV2luMzJfUHJvY2Vzcy5DYXB0aW9uLFdpbjMyX1Byb2Nlc3MuQ29tbWFuZExpbmUsV2luMzJfUHJvY2Vzcy5DcmVhdGlvbkRhdGUsV2luMzJfUHJvY2Vzcy5EZXNjcmlwdGlvbixXaW4zMl9Qcm9jZXNzLkV4ZWN1dGFibGVQYXRoLFdpbjMyX1Byb2Nlc3MuTmFtZSxXaW4zMl9Qcm9jZXNzLlBhcmVudFByb2Nlc3NJZCxXaW4zMl9Qcm9jZXNzLlByb2Nlc3NJZCxXaW4zMl9Qcm9jZXNzLlByaW9yaXR5JyAtZmlsdGVySG90Zml4ICR0cnVlIC1vdXRwdXRGb3JtYXQgJ3htbCcgfSB8IE91dC1TdHJpbmcgfCBGb3JFYWNoLU9iamVjdCB7IFtDb25zb2xlXTo6V3JpdGVMaW5lKCRfKSB9 | invoke-expression] timed out after PT16M40S

Needed a resolution for that

1 ACCEPTED SOLUTION

Mahak2
Kilo Guru

Hello,

Please do the following:

1.Have you tried increasing wmi_timeout ?

Please see this link it will be helpful

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/mid-server/reference/mid...

 

2. 

 

A simple Powershell WMI query directly from the MID Server to the remote machine can be used to test access and permissions. 

Open a PowerShell command line on the host where the MID server is being used and run the following:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Substitute LOCALDOMAIN\mid by the credential to test, and 192.168.200.14 with the target IP address. The expected result would be similar to:

SystemDirectory : C:\Windows\system32
Organization    :
BuildNumber     : 6001
RegisteredUser  : Windows User
SerialNumber    : 12345-OEM-1234567-12345
Version         : 6.0.6001


Kindly Mark  Correct and Helpful if applicable., So that others get benefited in future for similar issues...

View solution in original post

4 REPLIES 4

Mahak2
Kilo Guru

Hello,

Please do the following:

1.Have you tried increasing wmi_timeout ?

Please see this link it will be helpful

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/mid-server/reference/mid...

 

2. 

 

A simple Powershell WMI query directly from the MID Server to the remote machine can be used to test access and permissions. 

Open a PowerShell command line on the host where the MID server is being used and run the following:

gwmi win32_operatingsystem -computer 192.168.200.14 -credential 'LOCALDOMAIN\mid'

Substitute LOCALDOMAIN\mid by the credential to test, and 192.168.200.14 with the target IP address. The expected result would be similar to:

SystemDirectory : C:\Windows\system32
Organization    :
BuildNumber     : 6001
RegisteredUser  : Windows User
SerialNumber    : 12345-OEM-1234567-12345
Version         : 6.0.6001


Kindly Mark  Correct and Helpful if applicable., So that others get benefited in future for similar issues...

I tried this thing previously i was getting near about 100+ errors but now we are getting about 40 so any other thing that we need to try

sdse33
Kilo Contributor

One in keeping with precedence so we get separate rating for each Priority personally help. Note that we could also have made a Priority breakdown and used it however, allow<s preserve it simple for now.

phil50
Tera Contributor

i have a similar issue.

When running the credential test script i get an RPC error.

This happens when I run if from an older mid-server but not on a newer server.

 

Command: gwmi win32_operatingsystem -computer (ip provided) -credential (cred supplied)

Error: gwmi : The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)