Error Handling Deployments

Errors may occur while working in Scheer PAS. To facilitate troubleshooting, corresponding error and notification messages are displayed in the application. The overview of error messages allows you to identify possible causes and possible solutions. It also refers to documentation pages that contain further details.

Deploying a project is only possible via the projects catalog. For errors during the deployment process, refer to Error Handling Projects Catalog.

General Errors

Problem or Error Message

Possible Reason

Solution

Further Information

Access denied

Your account does not have permission to perform this action.

Ask your administrator for the required permission.


No connection, check your internet connection and try again

The Control Hub could not reach the platform.

Check your connection, then reload the page or apply your change again.


Service temporarily unavailable, try again later

The platform service performing this action is temporarily unavailable.

Wait a moment, then reload the page.


Unexpected error, try again

An unexpected server error occurred.

Try the action again. If the problem continues, contact your administrator.


Monitoring Deployments

The following problems can occur while you monitor your deployments:

Problem or Error Message

Possible Reason

Solution

Further Information

No deployments yet. Go to the Catalog to deploy your first project.

Nothing is deployed yet, or no deployment matches the current search and filters.

Clear the search and the filters. If nothing is deployed yet, select the Catalog link to deploy a project.

Deploying a Project

A deployment or a component you expect is missing from the list.

A search term or a filter is active, or the deployment is listed on another page.

Clear the search and the filters, then move through the pages of the list.

Working With the Control Hub

The Deployments view shows an error message with a recovery action.

The list of deployments could not be loaded.

Select the recovery action to load the view again. If the problem continues, contact your administrator.

Working With the Deployments View

Operating Deployments

The following problems can occur while you start, stop, restart, or delete a deployment or a component:

Problem or Error Message

Possible Reason

Solution

Further Information

Conflict detected, reload and try again

Another update changed the deployment.

Reload the Deployments view, then try the action again.

Working With the Deployments View

Deletion not possible, try again

The delete request did not complete.

Try the deletion again. If the problem continues, contact your administrator.

Deleting a Deployment

Configuring Deployments

The following problems can occur while you view or change the configuration of a deployment or a component:

Problem or Error Message

Possible Reason

Solution

Further Information

Changes could not be saved, try again

The platform could not store the configuration.

Apply the change again. Your edits are kept, so nothing is lost. If the problem continues, contact your administrator.

Configuring a Deployment

Conflict detected, reload and try again

Another update changed the deployment while you were editing its configuration.

Copy your text, reload the page, then apply your change again.

Configuring a Deployment

Content not found, may have been removed

The deployment or the component no longer exists.

Return to the Deployments view and reload it.

Working With the Deployments View

Fields contain invalid or missing values

The configuration is valid JSON, but the platform rejected values it contains.

Correct the reported values and apply again. Compare your values with the Initial configuration to see which values the deployment expects.

Configuring a Deployment

Invalid JSON

The text in the Custom Changes panel cannot be read as JSON.

Correct the text. Apply becomes available again as soon as the text is valid. Use Discard to return to the values last stored.

Configuring a Deployment

Invalid request, check your input and try again

The configuration does not match the structure the platform expects. Text that is valid JSON is not necessarily a valid configuration.

Compare your values with the Initial configuration, correct the structure, and apply again.

Configuring a Deployment

Loading took too long, try again

The configuration could not be loaded within the expected time.

Reload the page. If the problem continues, contact your administrator.


Service temporarily unavailable, try again later

The platform service that holds the configuration is temporarily unavailable.

Wait a moment, then reload the page.


Both editors are empty and read-only, and a message is shown below the text.

The configuration could not be loaded. All three parts are loaded together, so one failure concerns all of them.

Resolve the problem the message reports, then reload the page. Nothing can be edited until the configuration loads.

Configuring a Deployment

The Apply button is not offered.

There are no unsaved changes, the text is not valid JSON, or an apply is still running.

Check the status below the text. If it reports Invalid JSON, correct the text. If the button reads Applying …, wait until the apply has finished.

Configuring a Deployment

The format action is not offered.

The text is already formatted, or it is not valid JSON.

Correct the text if it is invalid. Otherwise there is nothing to format.

Configuring a Deployment

Discard and Apply are not available and the text cannot be edited.

An apply is in progress. The values the platform reports back replace what you sent, so an edit made in between would be lost.

Wait until the apply has finished. Both actions are available again afterwards, whatever the outcome.

Configuring a Deployment

Inspecting Logs

The following problems can occur when you want to open the deployment or component logs:

Problem or Error Message

Possible Reason

Solution

Further Information

A legacy standalone service offers no logs action.

Legacy standalone services cannot be managed from the Control Hub.

Use the PAS Resource Monitor directly to read the logs of a legacy standalone service.

Inspecting Logs

The Open Logs action is not displayed.

The PAS Resource Monitor is not configured for your installation, or the deployment has no components.

Ask your administrator to configure the PAS Resource Monitor.

Inspecting Logs

📗
📘

Related Documentation: