KB0031 - Environment Not Found Error

KB0031 - Environment Not Found Error

Applicability

Users that have Git sync enabled may run into an issue where PowerShell Universal reports that an environment was not found. 

Root Cause

The root cause is currently unknown. We are currently investigating this issue. This article will be updated when a patch has been released. 

Workaround

To work around this issue, you will want to ensure that you have an environments.ps1 file generated in your environment. Click Settings \ Environments in the admin console. Next, click the pencil icon to edit the properties of one of your environments. We suggest changing a setting such as Max Runspaces, saving the setting, editing it again and setting it back to the default value. This will generate an environments.ps1 file in your environment. 
The issue is related to environment auto-discovery in PowerShell Universal. By creating an environments.ps1 file, it will no longer attempt to discover environments. 

    • Related Articles

    • HTTPS Certificate Not Found

      Version: Any Issue: After configuration the certificate for your PowerShell Universal and attempting to start the server, you receive the following error.  Unhandled exception. System.InvalidOperationException: The requested certificate ...

    • KB0045 - The requested certificate could not be found

      Problem When specifying a certificate for PowerShell Universal in appsettings.json, an error may occur stating that the certificate could not be found. 2023-09-06 07:52:06.376 -05:00 [FTL] Fatal error starting PowerShell Universal. ...

    • 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 ...

    • "[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 ...

    • KB0049 - Failure to login after changing security environment

      Problem Changing from a security environment, such as Windows PowerShell, to the integrated environment may cause users to fail to be able to login. The login button will appear to do nothing when clicked. Root Cause Changing the security environment ...