"[WARN] Call failed. An error occurred while sending the request." message in all jobs
Version: Any
Root Cause
When PowerShell Universal starts a new job, it uses the Management API to retrieve job information from the server. It does this over HTTP and will generate a Read-Only app token for the identity of the user that started or scheduled the job. The web server uses internal APIs to determine the URL of the management API. If PowerShell Universal is hosted behind a remote proxy, like IIS, or cannot determine the web server URL, it will fail to connect and report the warning message:
[6:08:48 PM] [WRN] Call failed. An error occurred while sending the request. GET https://localhost/api/v1/Job/329
Resolution
To resolve this issue, you will need to configure the application settings. This can be accomplished be editing the appsetting.json file, environment variables or command line arguments. You can learn more about application configuration settings on the documentation.
When using the appsettings.json file, you will need to update the API \ URL property to include the root of your web server address. For example, if your web server was listening on https://ironmanpsu:448,/ you could updated the JSON file like this.
- "Api": {
- "Url": "https://ironmanpsu:448"
- },
Instead of trying to determine the API URL via internal APIs, PowerShell Universal will now pass this value to all PowerShell Environments (including jobs) so that the cmdlets use the proper URL.
Related Articles
KB0018 - An anonymous request was received in between authentication handshake requests.
Symptom #1 PowerShell Universal returns a 500 error when visiting the website that is using Windows Authentication. Symptom #2 When viewing the log file in C:\ProgramData\PowerShellUniversal or within the admin console under Settings \ General ..."Did not receive port from client process." when running jobs
Version: Any Problem: When executing jobs, jobs can fail without starting the PowerShell script. Within the PowerShell Universal logs, you will see an error that states: Did not receive port from client process. Root Cause: When running in ...KB0059 - Error During PowerShell Universal Install or Upgrade
Affected Versions - All PowerShell Universal Versions Problem When running the PowerShell Universal MSI on a system that had an older version of the product installed, the user will see an error message that states "The folder path 'C:' contains an ...IIS: HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure
Applies to: PowerShell Universal 1.4 or later When configuring PowerShell Universal to run under IIS, you may be presented with an error that states ANCM Out-Of-Process Startup Failure. This error can be presented for a variety of reasons but the ...KB0057 - Scheduled Jobs are Not Shown in the Script \ Jobs Tab
Affected Versions - PowerShell Universal 4.2.0 - 4.2.4 Problem When viewing a script's jobs within the script's page, scheduled scripts will not be shown. Root Cause A change was introduced to allow for filtering out scheduled jobs. The script's page ...