Preview and publish shows error after a while

Dec 07, 2022

Since recent or maybe past 2 updates, my storyline started to give an error on preview/publish after a while of working in project. These functions stop working until restart of the storyline. Forced to restart every 30 minutes takes a lot of time... After first occurence of error when trying to preview, the function doesn't even respond to click, nothing happens.

It happens in fresh, newly created projects and in the old ones also. I got that problem in every project I opened past two weeks (20 or so) after some time inside the project. Does anyone else have such a problem? I don't think this is realted to .story file itself, as after restart everything works fine for some time.

24 Replies
Robert Hoisan

OK, so  I wrote the above message, uninstalled SL, reinstalled and now just got an error...

<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<UserId>aid|21f367ac-768f-4425-b8bc-4448468d265f</UserId>
<HardwareId>KQYWV-MHKL3-F911A-UUVVT-1PRFH</HardwareId>
<Message>The system cannot find message text for message number 0x%1 in the message file for %2.
</Message>
<StackTrace> at void System.IO.__Error.WinIOError(int errorCode, string maybeFullPath)
at string System.IO.File.InternalCopy(string sourceFileName, string destFileName, bool overwrite, bool checkHost)
at void System.IO.File.Copy(string sourceFileName, string destFileName, bool overwrite)
at bool Articulate.Design.Publish.Player.PlayerImageBase.a(string A_0, IAsset A_1)
at string Articulate.Design.Publish.Player.PlayerImageBase.b(string A_0, IAsset A_1)
at string Articulate.Design.Publish.Player.PlayerImageBase.SaveToFile(string fileName, bool html5)
at async Task Articulate.Design.UI.PlayerProperties.PlayerLayout.PlayerLayoutTab.bj()
at async void Articulate.Design.UI.PlayerProperties.PlayerLayout.PlayerLayoutTab.LoadData()
at void System.Runtime.CompilerServices.AsyncMethodBuilderCore.ThrowAsync(Exception exception, SynchronizationContext targetContext)+(object state) =&gt; { }</StackTrace>
</ErrorReport>

Not sure what can cause these errors. I'll open a support case soon hopefully this can be fixed. But maybe other users can see this and write if they get strange errors recently.... For me it happens more when trying to preview but also when clicking on the player. 

Robert Hoisan

I have sufficient space, around 200GB on C: but I have Dropbox on a separate SSD internal drive (I save all my SL files directly on DB). I wonder if having DB on the main C drive will solve the issue. I know Storyline has issues with external drives but I use an internal SSD... 

The thing is these errors are mainly when previewing and / or accessing the Player, not that often when saving...

Robert Hoisan

All with audio. No JS, simple triggers. 

My guess it's my system (although new). Articulate fixed a bigger issue I had when trying to save (Fixed: Project files might not save due to low system memory on computers with Intel Iris Xe Graphics hardware - September 20, 2022 (Build 3.68.28773.0)

I even disabled the Intel Iris Xe Graphics card as I use a dedicated Nvidia MX but since that update in September I get these strange errors while previewing or getting into the player - one recent error attached. 

Mateusz, is you graphics card also an Intel Iris Xe?

 

Jürgen Schoenemeyer

here is the source code of the problem (-> Articulate.Design.dll)

private static bool a(string A_0, IAsset A_1)
{
if (!string.IsNullOrEmpty(A_1.WorkingFilename)
&& File.Exists(A_1.WorkingFilename))
{
File.Copy(A_1.WorkingFilename, A_0, overwrite: true);
return true;
}
return A_1.SaveAssetToFile(A_0);
}

storyline want's to overwrite an existing image and this is not possible at this moment*

*overwriting/deleting files is not easy in windows

Robert Hoisan

I think it's solved as I am not getting the errors for a while now. 

But I am not sure what was the problem or how it got solved. I tried all the steps below (mostly suggested by John Carlo from the support team) -  one or ore must have helped somehow. 

1) Close the Articulate 360 desktop app by right-clicking the Articulate icon in your computer's system tray (by the clock) and choosing "Quit."

2) Go to your Control Panel and uninstall all Articulate 360 apps, including the Articulate 360 desktop app, Peek 360, Replay 360, Storyline 360, and Studio 360.

3) Download and extract this zip file on your computer: http://articulate-360-kb.s3.amazonaws.com/360cleanup.zip

4) Right-click the 360cleanup.bat file and choose "Run as administrator." The script should only take a few seconds to remove all the Articulate files and registry keys from your computer.

5) Reboot your computer.

6) Download the latest Articulate 360 desktop app here: https://360.articulate.com/downloads

7) Right-click the articulate-360.exe file and choose "Run as administrator."

8) Launch the Articulate 360 desktop app and click "Install" beside each authoring app you want to install.

9) Reboot your computer and test your Articulate apps.

---------------------

1. Right-click the Storyline icon on your desktop and click Properties. If you don't have the icon on your desktop, search for it in the Start Menu instead and right-click. Choose Open File location. From there, right-click the Storyline icon and choose Properties.

2. Go to the "Compatibility Tab" and tick "Run in Compatibility" mode for Windows 8.


3. Save the changes and test Storyline 360.

If the issue persists, consider creating a new user profile on your machine in case it's an issue with the current user's settings.

---------------------


I also disabled my secondary graphics card in device manager. See attach. 

---------------------

Articulate also released a few updates in the meantime maybe that helped as well. 

Luciana Piazza

Wonderful news! Glad to hear you're no longer having this issue.

Thanks so much for sharing in the thread, Robert! I'm sure this will be helpful for others that come across this post!

If you have any other questions or discoveries, feel free to reach out in the E-Learning Heroes Community!

Have a great start to your week! ✨