Error Access Denied

May 10, 2019

Cailin Hochradel
By Cailin Hochradel

Hi all!

I am publishing a series of SCORM files and all of them have the same links to resources. However, one file is being very testy and giving me an access denied...

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>307362D3FC15251F</RequestId>
<HostId>
jLxPWf5OS5OgM7SPHLXuiahR3ngAjASjw05oZkcmGp31vomVApjkI0RNfEIDl/JM1XUlZm4fjQI=
</HostId>
</Error>

Any idea why when non of my other Storyline files functioned this way? I am publishing to Articulate Review to verify but attaching the doc here. 

 

The file is set up so that when you click the question mark in the GUI you can access the resources. (Created through the Master Slide) When you click the resources section you can see them but not when you click the link. 

 

Any ideas?

8 Replies
Leslie McKerchie
almost 5 years ago05/13/19 at 2:59 pm (UTC)

Hi Cailin, 

Thanks for sharing your .story file so that we could take a look.

It appears that you'd like to link to a .pdf file within your course. This article explains how you can do so easily when the document is included with the built-in Resources tab.

Based on the URL I see listed, this looks to be the intention.

If not, please be sure to link to a local file on your computer for it to be included. This reply by Wendy may be able to help with this set-up.

Alyssa Gomez
almost 5 years ago05/15/19 at 4:59 pm (UTC)

Hey Cailin! Happy to help you solve this. 

In the article Leslie shared here, step one says, "First, enable the Resources tab in your player and add the file attachment to your course."

When I opened the Resources section in Player Properties, I didn't see any resources added there. 

Try following the steps in this article, and let us know if you see an improvement! How to Link to a Resource in the Course Player

Lids Borden
almost 3 years ago05/04/21 at 3:49 pm (UTC)

Much appreciated for the reply...

Ren Gomez replied:

Hi Lids,

I'm sorry you see this error as well! It looks related to an outage yesterday that partially affected courses published to Review 360.

Articulate Status
Republishing should do the trick, but if you're still spotting this error, our support team can take a closer look!

Sign In to Reply