Troubleshooting API Management from 23.2

Error Message / ProblemPossible ReasonSolutionFurther Information
You cannot re-register a client (version).
  • It is not allowed to delete contracts if the client has been modified.
  • It is not allowed to re-register a client version that contains a contract with a retired API
  • Unregister the client.
  • Delete the contract.
  • Re-register the client.
You cannot delete a contract.It is not allowed to delete contracts if the client has been modified.
  • Check if the client is question is in state Unpublished Changes.
  • Check if you are able to register (or re-register the client).

Troubleshooting API Developer Portal

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Error Message / ProblemSolutionFurther Information

A client in your My Clients tab of the API Developer Portal is marked as Ready, while it must be Registered to use it.

If a client is not yet registered, you will find the icon Register Client next to the label Ready. Click it to register the client.


The Developer portal shows no data. The network tab from the development tools of your browser (accessible via F12) displays:

The current user is missing client role view-profile from the account group. To check this do the following:

  1. Login to Keycloak.
  2. Select Users from the menu of the Apiman realm.
  3. Click View all users.
  4. Click Edit on the affected user.
  5. Switch to tab Role Mappings.
  6. Select account from drop-down box Client Roles.

  7. If the user has no view-profile role assigned, select this role and add it to the list of Assigned Roles.

Troubleshooting API Management up to 23.1.1

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Error Message / ProblemSolutionExampleFurther Information
Failed to register client.

Remove the old contract (API version 1.0). Afterwards, you will be able to re-register your client.

Best Pratice

If you break the contract to API version 1.0, the end user will not be informed anymore that the API has been retired.
Instead he will get the following if accessing API version 1.0:

{"responseCode":404,"message":
"No contract found between Client Test-Client and Test-API."}
Thus, we recommended to create a new version of the client and register the new client to the new version of the the API.

This is mostly caused by the fact that a contract to an API that has been retired.

Imagine you have a contract to an API in version 1.0. After retiring the API, the contract is still active. The end user will get a message like this:

{"responseCode":410,"message":
"API Test-API in Organization RD has been retired."}

This will lead to the mentioned error: Failed to register client.

The API requires an API-Key header. This header is not passed from Swagger UI to the API because it is replaced automatically with the X-API-Key required for API Management.Use the API-Key-Policy to make API Management pass the API-Key to the API. Refer to API Key to read more about how to configure this policy.
You have imported a BRIDGE xUML service via the API Catalog. You know that the WSDL of a service is accessible on the BRIDGE via a link something like <service link>?wsdl. You try to use this method with API Management, and you add ?wsdl to the API endpoint of the service.

The service's WSDL is also imported from the catalog, namely to the API definition of the service. You can access the WSDL via the dedicated link provided by API Management (see orange box).

Still Need Help?

  1. First of all you can consult our complete technical documentation.
    The documentation is divided into several guides:
  2. If you can't solve your problem with help of the documentation, you can file a ticket to our support team at support@scheer-pas.com.
    All mails to our support mailbox will open a ticket in our service desk.
    Optionally, you may use our service desk portal. There, you can manage your tickets and raise new support requests. Using the portal requires you to register your email address, which will not take much time.

  3. To help you with your problem, our Support team needs some information on your software and environment. Please refer to Information to Include in a Support Request for more details on this.

On this Page:

Related Documentation:
  • No labels