Symptoms

1. When testing credentials it fails with Authorization error and throws the following in the mid logs related to credentials.psm1

05/31/19 10:07:56 (873) PowerConsole-923fbfb0db7dbf00c1b6e05c8a96195d>stderr DEBUG: STDERR: At D:\SOW\Installation files\New Dev Mid Server\agent\scripts\Powershell\WinRMAPI\Credentials\Credentials.psm1:70 char:16
 
05/31/19 10:07:56 (873) PowerConsole-923fbfb0db7dbf00c1b6e05c8a96195d>stderr DEBUG: STDERR: + ... $results = gwmi win32_operatingsystem -computer $computer -credentia ...
 
05/31/19 10:07:56 (873) PowerConsole-923fbfb0db7dbf00c1b6e05c8a96195d>stderr DEBUG: STDERR: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
05/31/19 10:07:56 (873) PowerConsole-923fbfb0db7dbf00c1b6e05c8a96195d>stderr DEBUG: STDERR: + CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException
 
05/31/19 10:07:56 (873) PowerConsole-923fbfb0db7dbf00c1b6e05c8a96195d>stderr DEBUG: STDERR: + FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommand&#13 

2. Testing the same credentials from the mid server using GWMI will be successful

Release

All releases

Cause

1. This can be caused if there is a customization in regards to Credentials.psm1 file. Customizing this file can cause issues with passing parameters to the credentials.psm1 powershell script.
2. These Credential.psm1 power-shell scripts are responsbile for testing the credentials and also while running discovery.

Resolution

Make sure both credential.Psm1 files are out of the box so that right parameters are passed to the script.