Resources attached to courses give error message from LMS

Jul 16, 2019

Pat McNurlin
By Pat McNurlin

I have 94 courses, all of which should have documents (PDFs) attached. I attach them and get no error messages. I publish the course and then upload to the LMS. Out of 94 courses, 14 had resources that gave me the attached message. Sometimes I get it on 1 of 2 documents for a course, sometimes for both documents, sometimes both documents work. I have cases where a document is available in 1 course but not available in a 2nd course. Once I get the error in a course, I always get it. When I go back to Storyline, delete the resource, the re-add it and publish, I get the error again.  So far my best answer has been to remove the resource from the course so the user doesn't see the error, but the resources are an important supplement to the course. What is happening here, and is there any way to tell if the situation is gong to happen before it gets to the LMS?

 

5 Replies
Charlie Kayley
over 3 years ago09/30/20 at 10:19 am (UTC)

I'm having this issue, I've tried the steps above but it is still giving me an error message

 

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>F78DA44A31C565A5</RequestId>
<HostId>L5nT75DhcbwFuj7i+GNaI1uZ3Bo+evOWPgfCaL4PsqJZGcf5CQHFJ6uK7M3tvQaFXxYZic6wAr8=</HostId>
</Error>

Can anyone help please

Katie Riggio
over 3 years ago10/01/20 at 2:30 pm (UTC)

Hey there, Charlie!

Thanks for writing in! A few basic questions that I don't want to overlook:

  • Are the document file names long, or do they include special characters, accents, or symbols? If yes, shortening the file names or removing the special characters and then republishing should help.
  • Where are your documents stored? If on a network drive, try moving them to a local c: drive along with the Storyline course.
  • If you could share the project file for testing, that would be gold. Use this case link to share it privately with our team.

This discussion is closed. You can start a new discussion or contact Articulate Support.