LTI errors and their solutions
Look up an LTI error message here: what it means, what causes it and what you can do about it.
When an LTI tool fails to launch, the LMS or Linqur shows an error message. Some messages come with a signature code, a long string of letters and digits that identifies the exact cause. This page lists the known messages with the cause and the solution for each.
Before you look up an error
- You don’t need to wait for a screenshot from your client. In the Debug assistant you can see the error messages of your own tools yourself, with the tool ID and the time.
- An error can be caused by a setting of the tool. What every setting does is in LTI tool settings explained.
Every error on this page has the same structure: the message as it appears on screen, the signature code if there is one, the cause and the solution.
Error: The ‘Publish as LTI tool’ plugin is disabled
Message: The ‘Publish as LTI tool’ plugin is disabled.
Signature: 1c8ac05364f4106084ccb06da45437744c5a27a3fc6e7f6c9e4140bc54104609
Cause: The LTI tool itself is disabled in the tool settings in Linqur.
Solution: This can’t be solved on the LMS side. Contact Linqur support, or ask the person who supplied the launch details to contact us. Put the Launch URL and the signature code in the e-mail, then we can resolve it quickly. This error should not occur, so if you see it, we want to know about it.
Your error isn’t in the list
- Check the settings of the tool first: edit the settings of an LTI tool.
- Test a Legacy (LTI 1.1) tool outside the LMS with Saltire. If the launch works there, the cause is in the LMS. Use the sample SCORM file for that test, so you know the package isn’t the cause.
- Send the message, the signature code, the Launch URL and the name and version of the LMS to support.
Found an error that isn’t here, or a better solution for one that is? Let us know and we’ll add it to this list and to the Debug assistant.