Storyline 3 not exporting SCORM 1.2 correctly

I had this installed on my work PC yesterday, using the most recently available download, and cannot make a working SCORM 1.2 package. It first failed on our new VLE (canvas), which was having other import trouble yesterday anyway so I blamed it on that. But having tested the same package on our current moodle site (v3.1), it is rejecting the file too.

I definitely choose LMS > SCORM 1.2 in the publish window.

If this is not a known bug, how do we get it fixed?

6 Replies
Dave Perry

I have worked out what was wrong - lack of disk space on my network drive (where My Documents is mapped to, by IT's policies).

Storyline 2 was ropey on detecting 'out of disk space' (some parts of the development/build process could detect it and provide a helpful error message, but others can't/don't). This has clearly not been addressed in 3 - how do I file a bug?

Matthew Bibby

Articulate advises people not to use network drives as they can introduce a number of issues.

When publishing, change the publish location to your local hard drive (if possible). If not, let IT know that Storyline doesn't work well with network drives and see if they can change things on your profile so you can publish to the local drive. 

FYI, you can contact Articulate Support here.

Matthew Bibby
Dave Perry

I have never seen this advise before - where is it? I have a local hard drive, luckily, but very few staff in the entire institution do.


See the article recommended workflow for collaborative network environments where it says:

After creating, editing, or publishing a Storyline project on your local hard drive, copy the project file to your network drive for storage and sharing. [...] By working with the project files on your local hard drive, you'll prevent loss of resources, file corruption, and other erratic behavior that can occur due to network latency.

Also the article create, edit, and publish Articulate Storyline courses on your local hard drive:

Always save and publish to your local hard drive (typically your C: drive). Working on a network drive or an external (USB) drive can cause erratic behavior due to latency, such as file corruption, an inability to save changes, and loss of resources.

If you need to place a copy of your project on a network drive or a USB drive for backup or versioning purposes, it's fine to do that after you've closed Storyline. Avoid reopening the project again until you've copied it back to your local hard drive.

Similarly, hosting published output on a network drive isn't supported. Instead, place your content in the location for which it was published. For example, if you published for web, upload your content to a web server; if you published for LMS, upload your content to an LMS, etc.