Autotask Returns: 500 Internal Server Error

Autotask Returns: 500 Internal Server Error

If you see an error logged to a ticket or log entry by Rocketship that includes “500 Internal Server Error” for Autotask, that generally means that Autotask rejected our API call due to an API violation.

Data violation: This Role (Help Desk) cannot be selected because the Resource/Role is inactive.

Rocketship may report the error like so:

Error Updating Ticket 10851 to Resource ppierce/Role: Exec. Management; Autotask API Returned: Server error: `PUT https://webservices2.autotask.net/ATServicesRest/v1.0/Tickets` resulted in a `500 Internal Server Error` response:{"errors":["Data violation: This Role (Exec. Management) cannot be selected because the Resource/Role is inactive.","Err (truncated...)

This is a misconfiguration in your Autotask tenant. Specifically, you have an Autotask Resource set to have a Service Desk Role, but you the Service Desk Role is currently set to INACTIVE in Autotask. You need to set it back to ACTIVE.

  1. Note the Resource and Role in our log message to you.
  2. Log into Autotask as an Autotask Admin
  3. Go to Admin->Resources (Users)
  4. Find the Resource (which we provide to you in the error message) in your Autotask Users
  5. Go to the Associations tab, scroll to the bottom, and enable the Role needed

Note, the Role is the one used when you setup the Rocketship Team. That Team is using the specific Role listed in our error message and it is the Role you need to enable for the Resource in Autotask.

For example, let’s say Rocketship is trying to dispatch a ticket to Tier 1, to which you’ve assigned the Autotask Role “SW:Project Manager.” When Rocketship tries to update the Autotask ticket to the Resource using that Role, Autotask is reporting that in fact the Resource has that Role as inactive, as shown below:


    • Related Articles

    • Rocketship Ticket Insight Returns an Error

      You may see errors in the Ticket Insight in Autotask where Rocketship fails to read the ticket, as shown below.. The primary reason this occurs is that Rocketship does not “see” the ticket because its API user does not have the correct permissions. ...
    • Autotask API Ticket Description Error on Ticket Update

      Sometimes Rocketship can’t update an Autotask Ticket. When this happens, the Autotask API returns an error. We usually log that error to the ticket. Example: { "status": 37, "id": 67706, "httpCode": 500, "response": { "errors": [ "String value ...
    • Autotask Service Call Cleaner

      Rocketship has a tool to bulk close service calls. This tool is normally used by our support team when onboarding new customers, but is available to the client admin portal as well. The use case is that an Autotask user has used service calls in the ...
    • Troubleshooting Autotask Connections in Rocketship

      This article describes steps to take when the Autotask API connection fails. You will be alerted to Autotask API connections via Rocketship Admin, the Autotask Ticket Insights, and the WorkBoard when we are experiencing issues with your Autotask API ...
    • How to Clone a Ticket in Autotask

      You may need to clone tickets in Autotask, whether for your own use or perhaps this is a request by Giant Rocketship’s support team when troubleshooting a support request. To clone a ticket, you can use the built-in tool for this provided by ...