Execution of powershell script using MidServer (Test Credential failed)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2025 09:19 AM
Hi ServiceNow Community,
I came here with a belief that one of the community member will help me get through the issue I'm facing.
Recently, I decided to Invoke Mid-server into the Flow designer the idea is to run a PowerShell script that do a specific task on a server with the help of Mid-server and response back through an output result. In order to move forward with this idea I have installed a Mid-server on a server. I test the connection while installing also created a Local-User inside the server for my Service name and later validated it during the installation as well.
As I can see my Mid-Server is UP & validated then I Created Connections & Credential alias where I have put the local user credentials which I user as a service in the credential table as seen in the Screenshot attached I Made one script action and tried to Test connection by putting two inputs Connection alias and another is mid-server.
First I got an error Saying "Credential testing against localhost is not allowed"
Then, I change the host name to the my PC hostname now It is giving me this error..
"Connecting to remote server INL-2HCMBY3 failed with the following error message : Win RM cannot process the request. The following error with error code 0x80090311 occurred while using Kerberos authentication: We cant sign you in with this credential because your domain is not available. Make sure your device is connected to your organizations network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the Win RM Trusted Hosts configuration setting or use HTTPS transport. Note that computers in the Trusted Hosts list might not be authenticated. -For more information about Win RM configuration, run the following command: win rm help config. For more information, see the about Remote Troubleshooting Help topic.
'Connecting' is not recognized as an internal or external command,
operable program or batch file."
Kindly Please help me getting this fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2025 06:47 PM
Hi @K Arpit
From the error message I can see that you haven't configured domain controller in your network.
So, first configure the AD and domain controller. Then create one service account under the domain and use it.
Regards,
Siva