AI Workbench Error Codes Reference

Error Message:

An unexpected filesystem error occurred in the CLI component.

OS/Location:

Explanation:

Error Message:

An unexpected internal error occurred in the CLI component.

OS/Location:

Explanation:

Error Message:

The attempted remote update failed after starting install process.

You can manually complete the update in two different ways:

1. Run ‘nvwb install —upgrade <context-name>’ from your local CLI
2. SSH to the remote and run ‘nvwb install —upgrade’

OS/Location:

Explanation:

Error Message:

An unexpected network error occurred in the CLI component.

OS/Location:

Explanation:

Error Message:

Download did not start for the Workbench binaries.

Make sure you’re connected to the internet and try re-running the Workbench install.

OS/Location:

Explanation:

Error Message:

Failed to fully install and configure Workbench on the Brev host.

Check the logs on the remote to diagnose and potentially fix this: 1. Open a terminal and run ssh <hostname/IP>. 2. Then run tail -n 30 ~/.nvwb/logs/workbench.log on the host to see the last output from the failed install. 3. If you need to see more logs to diagnose, increase the number 30 or cat the file.

While there are various failure causes, a common one is the CSP has pinned the NVIDIA container toolkit version.

If that is the case, fix this on the remote with: sudo apt --only-upgrade --allow-change-held-packages install nvidia-container-toolkit nvidia-container-toolkit-base.

OS/Location:

Explanation:

Error Message:

Failed to fully install and configure Workbench on the Brev host.

Check the logs on the remote to diagnose and potentially fix this: 1. Open a terminal and run ssh <hostname/IP>. 2. Then run tail -n 30 ~/.nvwb/logs/workbench.log on the host to see the output from the failed install. 3. If you need to see more logs to diagnose, increase the number 30 or cat the file.

While there are various failure causes, a common one is the CSP has pinned the NVIDIA container toolkit version.

If that is the case, fix this on the remote with: sudo apt --only-upgrade --allow-change-held-packages install nvidia-container-toolkit nvidia-container-toolkit-base.

OS/Location:

Explanation:

Error Message:

Brev is not currently supported for remote installs from Windows.

OS/Location:

Explanation:

Error Message:

A Workbench binary did not completely download. Check your internet connection and retry the installation.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

An unexpected error happened when Workbench tried to read the Project spec file that is needed to manage the repository.

Investigate and fix this by doing the following: 1. Open a terminal to the project repository and run git status to see if .project/spec.yaml file has been changed 2. If it has been edited, restore the previous version with git restore .project/spec.yaml

If it’s a remote project, open a remote terminal in the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

Workbench can’t fully process the project spec file (.project/spec.yaml) because it has a YAML syntax error.

Typical YAML errors are incorrect indentation, missing colons, unquoted special characters, or tabs instead of spaces.

Fix this by editing and then validating the spec file. 1. Get the line number for the error from the system error message below 2. Open .project/spec.yaml in a file editor, go to that line, fix the error and save the file. 3. Then open a terminal into the project folder and run nvwb validate project-spec to verify your changes. 4. Finally, refresh the project tab with Ctrl+r

If it’s a remote project, open a remote terminal in the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

The project spec file is of an unsupported version and must be updated.

OS/Location:

Explanation:

Error Message:

The project spec file contains validation errors. Run nvwb validate project-spec to see all errors, then edit .project/spec.yaml to fix the reported issues.

OS/Location:

Explanation:

Error Message:

Workbench could not detect the .project/spec.yaml file needed to manage the repository. This happens when the file is accidentally deleted, renamed or moved.

Fix this by restoring the committed version: 1. Open a terminal into the project repository. 2. Check to see if the file was removed or altered with the command git status. 3. Restore the committed version with git restore .project/spec.yaml. 4. Refresh the project tab in the Desktop App with Ctrl+r.

If the project is remote, you should open a remote terminal into the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

An unexpected validation error occurred in the CLI component.

OS/Location:

Explanation:

Error Message:

Failed to verify integrity of a Workbench binary. Retry the installation.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

Could not complete the install of AI Workbench on the remote Brev host.

OS/Location:

Explanation:

Error Message:

Windows native upgrade is not supported with the CLI.

Windows is only supported with the Desktop application. Please use the Desktop application to upgrade.

OS/Location:

Explanation:

Error Message:

Desktop app detected. Please upgrade through the desktop application instead.

OS/Location:

Explanation:

Error Message:

The version of the AI Workbench server running in the remote location is incompatible with the client installed on this host. Update or re-install AI Workbench in this location to continue.

OS/Location:

Explanation:

Error Message:

Failed to start native application VS Code. Check that VS Code and the code CLI are installed.

OS/Location:

Explanation:

Error Message:

Failed to start native application VS Code. Check that VS Code and the code CLI are installed.

OS/Location:

Explanation:

Error Message:

Another user has an active AI Workbench session on this remote location.

You are blocked from using the location because only one user can have an active session at a time.

To use this location you can: 1. Contact the other user and ask them to deactivate their session 2. OR reboot the system

Then, try activating the location again.

OS/Location:

Explanation:

Error Message:

Workbench requires the location to be deactivated before you can update its information. Close the location window, then try modifying the location again.

OS/Location:

Explanation:

Error Message:

Invalid command for remote-only installation. This command is only available for full installations.

OS/Location:

Explanation:

Error Message:

An unexpected filesystem error occurred in the CREDENTIAL_MANAGER component.

OS/Location:

Explanation:

Error Message:

An unexpected internal error occurred in the CREDENTIAL_MANAGER component.

OS/Location:

Explanation:

Error Message:

Failed to parse JSON response from the external service. The response may be malformed.

OS/Location:

Explanation:

Error Message:

An unexpected network error occurred in the CREDENTIAL_MANAGER component.

OS/Location:

Explanation:

Error Message:

Unable to connect to the external service. This may be due to network connectivity issues or the service being temporarily unavailable.

OS/Location:

Explanation:

Error Message:

The request to the external service timed out. Check your network connection and try again.

OS/Location:

Explanation:

Error Message:

The external service is temporarily unavailable. Please try again later.

OS/Location:

Explanation:

Error Message:

Failed to complete OAuth authentication flow. This may be due to network issues or service problems.

OS/Location:

Explanation:

Error Message:

Failed to retrieve user profile information from the external service. Check your network connection and try again.

OS/Location:

Explanation:

Error Message:

Failed to refresh the authentication token. Check your network connection and try again.

OS/Location:

Explanation:

Error Message:

Failed to communicate with the integration API. Check your network connection and try again.

OS/Location:

Explanation:

Error Message:

An unexpected project specification error occurred in the CREDENTIAL_MANAGER component.

OS/Location:

Explanation:

Error Message:

An unexpected validation error occurred in the CREDENTIAL_MANAGER component.

OS/Location:

Explanation:

Error Message:

The provided credentials are invalid or have been revoked. Please reconnect to the integration.

OS/Location:

Explanation:

Error Message:

Access to the requested resource is forbidden. Check your permissions and try again.

OS/Location:

Explanation:

Error Message:

Your authentication token has expired. Please reconnect to the integration.

OS/Location:

Explanation:

Error Message:

The specified integration name is not recognized. Check the integration name and try again.

OS/Location:

Explanation:

Error Message:

A connection to this integration already exists. Disconnect first if you want to reconnect.

OS/Location:

Explanation:

Error Message:

The credential format is invalid. Please check the format and try again.

OS/Location:

Explanation:

Error Message:

Required arguments are missing. Please provide all required arguments.

OS/Location:

Explanation:

Error Message:

The provided URL format is invalid. Please check the URL and try again.

OS/Location:

Explanation:

Error Message:

OAuth authentication is not supported for this integration. Please use a personal access token instead.

OS/Location:

Explanation:

Error Message:

The OAuth authentication flow failed. Please try again.

OS/Location:

Explanation:

Error Message:

The provided token is invalid. Please check the token and try again.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while in the Desktop Application.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while quitting the Desktop Application.

OS/Location:

Explanation:

Error Message:

An unexpected filesystem error occurred.

OS/Location:

Explanation:

Error Message:

Could not create the .nvwb/bin directory

OS/Location:

Explanation:

Error Message:

Could not move the AI Workbench Service binary (wb-svc) to the .nvwb/bin directory.

Restart your computer and try again.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

Could not move the AI Workbench CLI binary (nvwb-cli on macOS/Linux/WSL; nvwb-cli.exe on Windows) to the .nvwb/bin directory.

Restart your computer and try again.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

Could not move the AI Workbench Credential Manager binary (credential-manager on macOS/Linux; credential-manager.exe on Windows) to the .nvwb/bin directory.

Restart your computer and try again.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

Could not verify all the binaries were moved to the .nvwb/bin directory.

Restart your computer and try again.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

Failed to set ownership on the .nvwb/bin directory and the workbench binaries. This may be due to permission issues with your user account.

OS/Location:

Explanation:

Error Message:

Failed to set permissions on the .nvwb/bin directory and the workbench binaries. This may be due to permission issues with your user account.

OS/Location:

Explanation:

Error Message:

Could not locate the binaries in the application bundle. This may be due to permission issues with your user account.

If it fails again, contact support.

OS/Location:

Explanation:

Error Message:

AI Workbench was unable to confirm the status of your system.

OS/Location:

Explanation:

Error Message:

Failed to list the AI Workbench locations on your system

OS/Location:

Explanation:

Error Message:

An unexpected error occurred when migrating your data from Windows to the NVIDIA-Workbench distribution

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while trying to determine your installation type.

OS/Location:

Explanation:

Error Message:

The location that you are attempting to load could not be found. It may have been removed or renamed.

Please try again by selecting a valid location from the Locations Manager.

OS/Location:

Explanation:

Error Message:

An unexpected network error occurred in the Desktop Application.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while running the local installation.

OS/Location:

Explanation:

Error Message:

Failed to run the install hook for the AI Workbench CLI

OS/Location:

Explanation:

Error Message:

Failed to set the CLI Path in the cli.yaml file

OS/Location:

Explanation:

Error Message:

A required dependency failed to install during desktop setup.

1. Check your internet connection and proxy settings.
2. Rerun the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

There was an error interacting with AI Workbench’s configuration files.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while running the local installation.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while creating your local location.

OS/Location:

Explanation:

Error Message:

AI Workbench failed to connect to Docker Desktop in the allotted time. This may be an issue with Docker Desktop not starting. Try to start Docker Desktop manually and then activate the location again in AI Workbench. If Docker Desktop fails to start manually, you may need to complete onboarding steps. Docker now requires you to login before you can start Docker Desktop.

OS/Location:

Explanation:

Error Message:

An unexpected validation error occurred in the Desktop Application.

OS/Location:

Explanation:

Error Message:

An unexpected validation error occurred when checking your OS version and type for compatibility.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred when checking your UAC settings.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred when checking your admin settings.

OS/Location:

Explanation:

Error Message:

An unexpected error occurred when checking your virtualization settings.

OS/Location:

Explanation:

Error Message:

An unexpected WSL error occurred in the Desktop Application.

OS/Location:

Explanation:

Error Message:

Failed to download the NVIDIA-Workbench distribution

OS/Location:

Explanation:

Error Message:

Failed to install the NVIDIA-Workbench distribution

OS/Location:

Explanation:

Error Message:

Failed to set the workbench user in the NVIDIA-Workbench distribution

1. Unregister the NVIDIA-Workbench distribution:

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

Failed to update packages; there may have been a network error during the installation of the NVIDIA-Workbench distribution

1. Unregister the NVIDIA-Workbench distribution:

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

Failed to upgrade packages; There may have been a network error during the installation of the NVIDIA-Workbench distribution

1. Unregister the NVIDIA-Workbench distribution:

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

Failed to install dbus package; there may have been a network error during the installation of the NVIDIA-Workbench distribution

1. Unregister the NVIDIA-Workbench distribution:

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

Failed to update iptables; there may have been a network error during the installation of the NVIDIA-Workbench distribution

1. Unregister the NVIDIA-Workbench distribution:

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

Failed to configure the NVIDIA-Workbench distribution; in this step we set up systemd

OS/Location:

Explanation:

Error Message:

Failed to download the manifest file for the NVIDIA-Workbench distribution

OS/Location:

Explanation:

Error Message:

The checksum for the NVIDIA-Workbench distribution did not match the expected checksum

1. Rerun the AI Workbench local installation flow

OS/Location:

Explanation:

Error Message:

The check to confirm the NVIDIA-Workbench distribution is installed failed

OS/Location:

Explanation:

Error Message:

The distribution NVIDIA-Workbench is not installed, running the WSL import command failed

1. Re-run the installation flow

OS/Location:

Explanation:

Error Message:

The NVIDIA-Workbench distribution failed to configure for an unknown reason

1. Delete the NVIDIA-Workbench distribution

wsl --unregister NVIDIA-Workbench

2. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

An error occurred while checking the status of WSL on your system

OS/Location:

Explanation:

Error Message:

An unexpected error occurred while installing WSL

1. Quit AI Workbench
2. Run the following command:

wsl --install
wsl --update

3. Restart your computer
4. Re-run the AI Workbench Local installation flow

OS/Location:

Explanation:

Error Message:

GitHub is rate limiting your requests. Please try again later.

OS/Location:

Explanation:

Error Message:

The check for Windows features (Virtual Machine Platform and WSL) timed out. This often happens when there are pending system updates that require a reboot.

1. Check for and install any pending Windows Updates.
2. Restart your computer.
3. Re-run the installation.

OS/Location:

Explanation:

Error Message:

The enabling of Windows features (Virtual Machine Platform and WSL) timed out. This often happens when there are pending system updates that require a reboot.

1. Check for and install any pending Windows Updates.
2. Restart your computer.
3. Re-run the installation.

OS/Location:

Explanation:

Error Message:

An unexpected filesystem error occurred in the SERVICE component.

OS/Location:

Explanation:

Error Message:

Could not delete the project because it has a protected file. This can happen if a container in the project ran as root. To fix, you must manually remove the repository.

• Open a terminal for the location
• Remove the repository with the command sudo rm -rf ~/nvidia-workbench/<project>
• Delete the project again

OS/Location:

Explanation:

Error Message:

An unexpected internal error occurred in the SERVICE component.

OS/Location:

Explanation:

Error Message:

The AI Workbench service failed to start. Check the service logs for more details and ensure all dependencies are properly installed.

OS/Location:

Explanation:

Error Message:

An error occurred while processing the GraphQL request. This may be due to an internal service issue.

OS/Location:

Explanation:

Error Message:

An unexpected network error occurred in the SERVICE component.

OS/Location:

Explanation:

Error Message:

The GraphQL request timed out. The operation may be taking too long or the server is under heavy load.

OS/Location:

Explanation:

Error Message:

Failed to establish WebSocket connection for GraphQL subscriptions. Check your network connection and try again.

OS/Location:

Explanation:

Error Message:

Git Repository is private and requires credentials to be able to clone. Connect to the appropriate 3rd party integration.

OS/Location:

Explanation:

Error Message:

Git Repository is either private or doesn’t exist. Check the URL and permissions to access the repository.

OS/Location:

Explanation:

Error Message:

An unexpected error happened when Workbench tried to read the Project spec file that is needed to manage the repository.

Investigate and fix this by doing the following: 1. Open a terminal to the project repository and run git status to see if .project/spec.yaml file has been changed 2. If it has been edited, restore the previous version with git restore .project/spec.yaml

If it’s a remote project, open a remote terminal in the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

Workbench can’t fully process the project spec file (.project/spec.yaml) because it has a YAML syntax error.

Typical YAML errors are incorrect indentation, missing colons, unquoted special characters, or tabs instead of spaces.

Fix this by editing and then validating the spec file. 1. Get the line number for the error from the system error message below 2. Open .project/spec.yaml in a file editor, go to that line, fix the error and save the file. 3. Then open a terminal into the project folder and run nvwb validate project-spec to verify your changes. 4. Finally, refresh the project tab with Ctrl+r

If it’s a remote project, open a remote terminal in the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

The project spec file is of an unsupported version and must be updated.

OS/Location:

Explanation:

Error Message:

The project spec file contains validation errors. Run nvwb validate project-spec to see all errors, then edit .project/spec.yaml to fix the reported issues.

OS/Location:

Explanation:

Error Message:

Workbench could not detect the .project/spec.yaml file needed to manage the repository. This happens when the repository or the spec file is accidentally deleted, renamed or moved.

Fix this by fully deleting the repository in Workbench, or by restoring the committed version: 1. Try to open a terminal into the repository. If you can’t, it was deleted or moved. Remove it from the Workbench inventory by selecting delete in the project card in the location window. 2. Otherwise, run the command git status to see what happened to the file. 3. Restore the committed version with git restore .project/spec.yaml. 4. Refresh the project tab in the Desktop App with Ctrl+r.

If the project is remote, you should open a remote terminal into the project repository to edit the file and run the nvwb validate command.

OS/Location:

Explanation:

Error Message:

An unexpected validation error occurred in the SERVICE component.

OS/Location:

Explanation:

Error Message:

Managed installation on this OS is not currently supported. See https://docs.nvidia.com/ai-workbench/index.html for more information.

OS/Location:

Explanation:

Error Message:

Container runtime configuration failed during installation.

1. Ensure Docker or Podman is installed and running
2. Open Workbench and retry installation
3. Learn more: https://docs.nvidia.com/ai-workbench/reference/error-codes

OS/Location:

Explanation:

Error Message:

Git LFS installation failed during AI Workbench setup. Git LFS is required for managing large data and model files in your projects.

1. Ensure you have a stable internet connection.
2. Try running the installation again.
3. If the problem persists, install Git LFS manually: - On macOS: brew install git-lfs - On Ubuntu: sudo apt-get install git-lfs
4. After manual installation, run git lfs install to configure it globally
5. Learn more: https://docs.nvidia.com/ai-workbench/reference/error-codes

OS/Location:

Explanation:

Error Message:

The AI Workbench service is already running. Exit AI Workbench Desktop or deactivate and shutdown the local context

OS/Location:

Explanation:

Error Message:

The GraphQL request is malformed or contains invalid syntax. Please check the query format and try again.

OS/Location:

Explanation:

Error Message:

The requested GraphQL operation is not allowed. Only queries are permitted on this endpoint.

OS/Location:

Explanation:

Error Message:

Required arguments are missing from the GraphQL request. Please provide all required fields.

OS/Location:

Explanation:

Error Message:

The provided project ID is invalid or the project does not exist.

OS/Location:

Explanation:

Error Message:

The specified file path is invalid or the file does not exist in the project.

OS/Location:

Explanation:

Error Message:

Registry (e.g. docker.io) should be included in the Base Environment URL; expected format is <registry>/<image>:<tag>

OS/Location:

Explanation:

Error Message:

The build assistant has made changes to the project that have not been reviewed. Acknowledge the changes before building.

OS/Location:

Explanation: