The following is a list of HTTP error codes that you may receive while operating Datalink. Identify the specific error code or message you've received to find a technical explanation of the cause and some troubleshooting instructions!

• HTTP 302: Found
• HTTP 400: Bad Request
• HTTP 401: Unauthorized
• HTTP 403: Forbidden
• HTTP 404: Not Found
• HTTP 409: Conflict
• HTTP 500: Internal Server Error
• HTTP 503: Conflict

Please contact Customer Support if the included troubleshooting instructions do not solve your problem. In your message to Support, specify the troubleshooting steps you have already attempted.

HTTP 302: Found

Related error messages

• Failed to create an upload session with...

What's going on

A user permissions issue prevents Datalink from uploading data. Most commonly occurs when upload requests are sent to Apptio from third-party sources.

Solution

1. Verify that the destination user has the correct Role to access the workspace, project, and table that you wish to upload data to.
2. In the Apptio Destination settings of your connector, enable the Use SSL option and run the connector again.

HTTP 400: Bad Request

Related error messages

• HTTP 400: Not a valid project name
• HTTP 400: table is missing or empty
• HTTP 400: Not a valid table name
• Failed to retrieve upload session with HTTP 400: Not a valid upload session

What's going on

Datalink is unable to find the specified data. This is usually caused by invalid, missing, or empty project/table names.

Solution

1. Check the syntax of your requested resource and its data source. Assume all fields are case-sensitive.
2. Verify that the destination project has been successfully imported. A failed or incomplete import may omit the data you need.
3. Upgrade your DataLink instance to the latest version to resolve possible compatibility issues. Newer versions also include updated troubleshooting messages that may provide more details. 

HTTP 401: Unauthorized

What's going on

Your security credentials are invalid due to the configuration of your connector or security policies.

Solution

1. Verify the syntax and authorization of your credentials in the connector you are using.
2. Check the the security policies configured at the data source to ensure your credentials have authorization.

HTTP 403: Forbidden

What's going on

Your security credentials are valid, but the configuration of your connector or security policies is preventing full access.

Solution

1. Verify the syntax and authorization of your credentials in the connector you are using.
2. Modify the permissions of your credentials so it can access the requested data, or use different credentials that already have access.
3. Check the the security policies configured at the data source to ensure your credentials have authorization.

HTTP 404: Not Found

What's going on

The connector cannot find the requested information. Your error message may include details about the location the connector is trying to access.

Solution

1. Verify the syntax of the resource and data source you are trying to access.
2. Verify that your the data source contains the data you need.
3. Verify that the connector is pointed at the correct data source and destination. There may be a disconnect between where the data source is pulling from and where the connector is looking.
4. Verify whether the Power User role is allowed to access the project in Frontdoor.

HTTP 409: Conflict

Related error messages

• Upload Succeeded but failed to check-in with HTTP 409: Conflict
• HTTP 409: Data Validation Failed - [ERROR_CANT_FIND_COLUMN : DESCRIPTION : Column does not exist...
• HTTP 409: Document is currently locked for check-ins
  

What's going on

The validation process has found a major conflict in your data.

Solution

1. Verify that your destination project is Unlocked.
2. See Upload succeeded but failed validation explained.

HTTP 500: Internal Server Error

Related error messages

• HTTP 500: "error_message": "Loading table failed"
• HTTP 500: "error_message": "InternalServerException Something went wrong".
• HTTP 500: Unexpected exception occurred:
  

What's going on

• Uploading data during calculation or high network traffic.
• A difference in file format or naming convention between the uploaded file and destination.

Solution

1. Try uploading your data to another table to see if the issue persists.
2. Try your upload again while no calculations or other uploads occurring.
3. Ensure the document's file and name format match the destination table.

HTTP 503: Conflict

Related error messages

• Failed to retrieve upload session with HTTP 503: Service Temporarily Unavailable

What's going on

There may have been an Apptio service update, installation, maintenance, or outage in progress while uploading your file.

Solution

1. Ensure no service updates are planned or in-progress for your environment.
2. Verify that you can access the destination resource and try again.

See Multicloud Connector FAQ for more information. Need more help? Post your question to field suggestions from experts across the Apptio Community!