WRN message on all scripts

PowerShell Universal
1

Hi all.

I am getting this message always on all scripts:

[6:08:48 PM] [WRN] Call failed. An error occurred while sending the request. GET https://localhost:443/api/v1/Job/329
[6:08:48 PM] [WRN] Call failed. An error occurred while sending the request. GET https://localhost:443/api/v1/Script/18

Previously, I created SSL certificate and signed it with my Active Directory Certificate Authority. Afterwards I configured PowerShell Universal to use that script in appsettings.json file. Everything works fine, and I am able to open PowerShell Universal from my computer by https://myserver.domain.com link, and browser shows certificate as valid.

I am not sure if this is a reason for that behavior. According to error, may be server can not access itself as localhost link? When I open PowerShell Universal from the browser on server via https://localhost , I get browser error message that this address is no trusted because of the wrong certificate.

How can I add my Active Directory Certificate Authority root certificate into PowerShell Universal? My root certificate is already installed in my local computer trusted root certificate store.

Thanks in advance.

Product: PowerShell Universal
Version: 1.4.7
2

Hi @AMustafayev,

You will need to provide the API URL to the configuration settings. I’ve created a KB article about this since you’re not the first to ask: https://support.ironmansoftware.com/portal/en/kb/articles/warn-call-failed-an-error-occurred-while-sending-the-request-message-in-all-jobs

1 Like
3

Thanks for the information, but after configuring API link, restarting service I still get error:

[6:23:52 PM] [WRN] Call failed. An error occurred while sending the request. GET https://my_server/api/v1/Job/331
[6:23:53 PM] [WRN] Call failed. An error occurred while sending the request. GET https://my_server/api/v1/Script/18

4

Can you verify that the call works in PowerShell itself?

Import-Module Universal
$AppToken = 'tokenvalue'
Get-UAJob -Id 331

Another issue we’ve run into recently is that if you are running jobs in Windows PowerShell, it may be a problem with TLS. We will need to fix this issue within PSU since we are calling the Universal cmdlets internally.

Either way, I’ve opened an issue for this particular warning as we should be able to adjust how the jobs receive this information so that it’s not necessary to call the REST API but rather use our internal IPC.

5

Import-Module Universal

And I got next error:

Import-Module : The specified module ‘Universal’ was not loaded because no valid module file was found in any module directory.

I checked C:\Program Files (x86)\WindowsPowerShell\Modules and C:\Program Files\WindowsPowerShell\Modules folders, there is no such folder Universal. Seems like PowerShell Universal did not install modules, however no errors were shown during installation process.

Either way, I’ve opened an issue for this particular warning as we should be able to adjust how the jobs receive this information so that it’s not necessary to call the REST API but rather use our internal IPC.

That`s great! Is it known when we shall get this feature?

6

It should be available in 1.4.8 which will be out next week sometime.