サポートと今すぐチャット
サポートとのチャット

Starling Connect Hosted - Troubleshooting Guide

Error 422 Unprocessable Entity

Error 422 unprocessable Entity occurs when the number of resources limit on account has been exceeded.

To rectify the error

  1. Ensure that the account has the ability to host additional user resources and group resources.
  2. Repeat the steps of provision by providing values for all the mandatory fields.
  3. Check and confirm that the resource has been provisioned.

Error 500 Generic Message

Different error scenarios associated with Error 500 Generic Message are listed below:

  • Internal Server Error

  • Unhandled Exception from Starling Connector

  • RSA Archer cloud application returns code 500 for all errors except 401 Unauthorized

The procedures to verify the error scenarios are detailed below.

Internal Server Error

To ensure that Starling endpoints are working

  1. Open a SCIM Client (for example, Postman).

  2. Perform a GET operation for endpoints mentioned below:

    • Schemas

    • ServiceProviderConfig

    • ResourceTypes

    • Users

    • Groups

  3. Verify the JSON response, to check whether it is successful.

Unhandled Exception from Starling connector

To ensure that Starling Endpoints are working

  1. Open a SCIM Client (for example, Postman).
  2. Perform a GET operation for endpoints mentioned below:
    • Schemas
    • ServiceProviderConfig
    • ResourceTypes
    • Users
    • Groups
  3. Verify the JSON response, to check whether it is successful.

RSA Archer cloud application returns code 500 for all errors except 401 Unauthorized

To ensure that Starling endpoints are working

  1. Open a SCIM Client (for example, Postman).
  2. Perform a GET operation for endpoints mentioned below:
    • Schemas
    • ServiceProviderConfig
    • ResourceTypes
    • Users
    • Groups
  3. Verify the JSON response, to check whether it is successful.

Error 502 Bad Gateway

The error scenario associated with Error 502 Bad Gateway occurs when the requests count is more than 730, and load balances are not available.

To ensure that Starling endpoints are working

  1. Open a SCIM Client (for example, Postman).

  2. Perform a GET operation for endpoints mentioned below:

    • Schemas

    • ServiceProviderConfig

    • ResourceTypes

    • Users

    • Groups

  3. Verify the JSON response, to check whether it is successful.

Error 503 Service Unavailable

The error scenarios associated with Error 503 Service Unavailable are mentioned below:

  • Cloud account instance not awake or active (for example, ServiceNow)
  • FunctionHost Down

The procedures to rectify the mentioned error scenarios are detailed below.

Cloud account instance not awake or active (for example, ServiceNow)

To rectify the error

  1. Log in to the cloud application instance.

  2. Navigate through the steps to reactivate or enable.

  3. Verify using the SCIM client (for example, Postman).

  4. Perform a GET operation for the endpoints mentioned below:

    • Schemas

    • ServiceProviderConfig

    • ResourceTypes

    • Users

    • Groups

  5. Validate the cloud application instance credentials.

  6. Edit and update the connection parameters for the connector at Starling subscription.

Function Host Down

To rectify the error

  1. Log in to the Azure portal with the available credentials.

  2. Navigate to the specific Function host and ensure that it is working.

  3. Start the Function host, if it has been stopped.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択