Attaching documents to Storyline

May 06, 2013


I'm having a problem where the documents that I hyperlink to continue to name the path with double slashes and then the page cannot be found.  Even after I correct the slashes, they revert back to double slashes.  Any help would be appreciated.  Kathy

C:\\eLearning\\PHY-100DE\\DOE Area Types.docx

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Please try the following:

  • Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
  • If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.
  • Click the Back button to try another link.

HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)

Technical Information (for support personnel)

  • Go to Microsoft Product Support Services and perform a title search for the words HTTP and 404.
  • Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Web Site Setup, Common Administrative Tasks, and About Custom Error Messages.
5 Replies
Kevin Thorn

Hi Kathleen,

There's two common ways to handle hyperlinked documents: 1) As a hyperlink to the document that lives on a web server (website) somewhere, or as a hyperlinked document as an attachment to the course.

If there's no reason for users to edit the docx, I'd suggest is to convert your docx to a pdf. 

Next, try renaming  your file without spaces. Instead of "DOE Area Types.docx" add dashes or underscores such as "DOE_Area_Types.docx"

Sometimes browsers get all wonky trying to interpret spaces.

If this document was hyperlinked from a path on your computer when you published, check the published output folder, "story_content > external_files." The document should be in there.

Peter Anderson

Hi Kathleen, 

We're aware of an issue where double slashes are added to file paths, but typically it doesn't affect functionality.

Thanks for clarifying that you have indeed published and uploaded the course to its intended environment, and just to confirm, you see the same issue in a testing server like Tempshare

If you'd like, we'd be happy to take a closer look at it. Can you please go ahead and open a ticket with our support team, including the .story file, so they can take a closer look at what's going on?



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