In Content Controller, when you want to start allowing a new LMS to access your content, you'll need to share a package (or what we often call a proxy file) that points to the content hosted on your servers.
Is the launch failing? Is the third party LMS having issues getting a completion or some other piece of reporting data? Do you need to troubleshoot SCORM API access issues (Access Denied)? Then, we need a way to discover why. This is where a debug log from the LMS side can be helpful.
Let me walk you through how to generate a debug package and what to do with it.
Let me walk you through how to generate a debug package and what to do with it.
1. Navigate to the Account you need to troubleshoot for.
2. Select the course you'd like to use to debug
2. Select the course you'd like to use to debug
3. Click `Troubleshooting'
4. Click the arrow to expose your options
5. Click `Create Debug Package'
5. Select the specification you'd like to share the course in.
6. Click `Download'. This will download the zip to your machine. *links to download a debug dispatch are not supported. You will need to send the zip file to the client.
7. Have the client upload the course into their LMS and launch.
When they launch the course, there will be a new window that shows detailed information about the interaction between the content running in Content Controller and the target LMS. This should allow you to pinpoint the root cause of the error.
As always, if you have questions or need help deciphering a debug log, please feel free to reach out to us at support@rusticisoftware.com