One of our instructional designers is experiencing a strange occurance with her published output, that our other Storyline licences can not reproduce. Has anyone experienced an issue that when publishing for LMS the output does not result in the standard "File Name Output" folder from which you can zip your files, but rather ONLY publishes a zip file?
That sounds pretty unusual. Can you confirm that your colleague is working exclusively from a local drive? Some things they'll want to keep in mind:
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
She is actually, not. That is a good point. She is publishing out to a network drive. I'll pass that on to our IT along with your other tips. I'll post if anything else come out of the troubleshooting process. I appreciate the help!
We have luckily found a resolution. Interestingly, it turned out to be what looks like an internal desktop (RAM) issue. We thought she was saving out to our network drive, but she was in fact saving it locally. The computer (yikes, dating our capacity) is older and must not have been able to keep up with output. She published it to our network folder and it is functioning a-ok, even with our LMS. However, we have noted that saving to a local drive works best, and hopefully she will also get updated technology!
5 Replies
Hi DeAnn, welcome to the community!
That sounds pretty unusual. Can you confirm that your colleague is working exclusively from a local drive? Some things they'll want to keep in mind:
1. Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
2. You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
3. Avoid using special characters, accents or symbols in your file names.
Thanks, Peter!
She is actually, not. That is a good point. She is publishing out to a network drive. I'll pass that on to our IT along with your other tips. I'll post if anything else come out of the troubleshooting process. I appreciate the help!
Sounds good, DeAnn - let us know
We have luckily found a resolution. Interestingly, it turned out to be what looks like an internal desktop (RAM) issue. We thought she was saving out to our network drive, but she was in fact saving it locally. The computer (yikes, dating our capacity) is older and must not have been able to keep up with output. She published it to our network folder and it is functioning a-ok, even with our LMS. However, we have noted that saving to a local drive works best, and hopefully she will also get updated technology!
We truly appreciate the help!
I'm so glad to hear you were able to isolate the problem, DeAnn
And yeah, I hope she gets a chance to update soon!
This discussion is closed. You can start a new discussion or contact Articulate Support.