Skip to main content

Troubleshooting

This section lists error messages that you might encounter while running the enosix Connect console and describes how to respond in each situation. The messages are grouped by where they occur within the enosix Connect console.

APIs​

Message: At least one API must be selected {#message-at-least-one-api-must-be-selected}​

This message indicates that you clicked the API Selection wizard’s Confirm button, but no RIOs/RFCs were selected. Select at least one RIO/RFC before you click the Confirm button.

Apps​

Message: An App named ‘App name’ already exists {#message-an-app-named-app-name-already-exists}​

This message indicates that you attempted to deploy an App that has the same name as an existing App or an App that previously existed, but was removed. To deploy your App, chose a unique App name that doesn’t conflict with an existing or removed App name.

Message: App not connected {#message-app-not-connected}​

This message indicates that a Connection test failed in the Add Connection Settings dialog. The following list provides potential solutions:

  • This message may indicate that an App’s status is Inactive. In this case, wait for the App to transition to Active status, then try to add the Connection settings again.
  • This message may indicate that one or more of your Connection settings (Username, Password, URL, or Client) are invalid. Verify that your Connection settings are valid, then try to add the Connection settings again.

Message: No Connections are configured for the selected App. Please set up at least one Connection under the Configuration section for this App. {#message-no-connections-are-configured-for-the-selected-app-please-set-up-at-least-one-connection-under-the-configuration-section-for-this-app}​

This message indicates that you need to configure at least one Connection for your selected App. Follow the directions under Configure a Connection for an App in the Apps section of this documentation.

Message: Response status code does not indicate success: ‘code (status)’ {#message-response-status-code-does-not-indicate-success-code-status}​

This message indicates that a Connection test failed in the Add Connection Settings dialog. The following list provides potential solutions:

  • This message may indicate that one or more of your Connection settings (Username, Password, URL, or Client) are invalid. Verify that your Connection settings are valid, then try to add the Connection settings again.

The most common code here is a 401 (Unauthorized). This almost always means that the credentials on the cloud connector (or that were supplied on the connection configuration screen) are not valid SAP credentials. Note that the Cloud Connector connection test in SAP BTP does not actually validate the credentials that are stored on it - so that test may be successful and then this test can still fail due to invalid credentials.

Message: Service instance connectivity not found {#message-service-instance-connectivity-not-found}​

This message indicates that your SAP Business Technology Platform (BTP) Connectivity service is not working properly or has not been configured. Verify that your SCP Connectivity service is configured and running.

Message: Service instance destination not found {#message-service-instance-destination-not-found}​

This message indicates that your SAP Business Technology Platform (BTP) Destination service is not working properly or has not been configured. Verify that your SCP Destination service is configured and running.

Message: Something went wrong. Try again later. {#message-something-went-wrong-try-again-later}​

This message indicates that an unexpected error occurred. Wait a while, then repeat the operation that you performed.

Message: There are no available build agents {#message-there-are-no-available-build-agents}​

This message indicates that you attempted to deploy an App, but the Foreman service wasn’t running. This message is generally not seen in production or demo environments. In QA environments, you should redeploy the enosix Connect application.

Message: You have exceeded your space’s memory limit: app requested more memory than available. {#message-you-have-exceeded-your-spaces-memory-limit-app-requested-more-memory-than-available}​

This message indicates that you reached an SAP Business Technology Platform (BTP) memory resource limitation. You may need to log into your SCP account to delete a few Apps that were previously deployed, but are no longer needed.

Packages​

Message: Connection not configured for ‘App name’ {#message-connection-not-configured-for-app-name}​

This message indicates that you’re trying to publish a Package when the selected App has at least one unconfigured Connection. You can publish a Package that has unconfigured Connections, but you won’t be able to use the API endpoints that have unconfigured Connections.

You need to configure the unconfigured Connections in order to use their API endpoints. To configure a Connection (before or after you publish a Package), follow the directions under Configure a Connection for an App in the Apps section of this documentation.

Register Account​

Message: Account creation is taking extra time. Please return later. {#message-account-creation-is-taking-extra-time-please-return-later}​

This message indicates that you attempted to register an account, but account creation is taking longer than expected. Wait a while, then try to register your account.