Forum Discussion

e-learningAcade's avatar
e-learningAcade
Community Member
3 years ago

error on Publish

This morning, I installed the latest update. From then on, when I try to Publish a story, the system gives me an error. "We're sorry, something went wrong ...." I click the 'send' button to send the 'information' but I have no reply and I cannot figure out what the problem is. The story(s) published fine last week. The only slide I changed was the last slide, in this case the RESULTS slide, I changes the font size and added an extra shape that exits the module when clicked.

What went wrong ? 

 

  • Hi e-learning Academy,

    I'm sorry for the issues with your publishing, but I'm happy to help! Can you tell me a bit more about your set up, such as: 

    • Are you publishing locally to your desktop or C: drive? 
    • Is this happening on all your files or just this particular project file? 

    If you feel comfortable sharing your project file in this thread, we'd be happy to take a look and replicate on our end. 

     Thanks!

  • Thank you very much for taking the time to help me.

    - I publish to my D drive because we cannot write on the C drive. 

    - it happens with ALL files I am working on for the moment.

    I have attached 1 file that published fine last week and it is in our LMS system. They asked me to change the last (result) slide.

    I also would like to know how the 'information' file can help me to solve this issue.

    Again, thank you very much! 

    Freddy LEMMENS

     

  • Hi,
    try to downgrade storyline to version Build 3.62 (March 30, 2022) and publish again.

    If that helps, I can probably fix the file.

    Jürgen

    PS: of course Storyline works without problems with any drive - local or on the server - as long as you mount the drive with a drive letter.

     

  • Thank you !

    I will ask our ICT dept. to downgrade because I cannot install/uninstall software on my pc.

    Do you have an URL / link where I can find Build 3.62 ?

     

  • Hi,
    open 'Articulate 260' and click on the symbol 'down'


     

    now install the version you need (there are alway 6 versions available)

    Jürgen

  • Wow > I received an email saying that I had to fill in a form and ask StoryLine to downgrade the software... I will try your suggestion.

    Thank you! 

  • OK > solved (more or less). I restored a previous version of the Story file and downgraded the software as suggested. Publish works again ... I can now start to redo the last modifications that I made after the backup of the file.

    Again - Thank you for your help!

  • I reported this error (case 03199180: svg publish -> 'out of memory') to Articulate at the beginning of May with an example - unfortunately there is no real solution to the problem yet.

    Jürgen

    • e-learningAcade's avatar
      e-learningAcade
      Community Member

      How do you know it is an out of memory problem ? Can you read this somewhere in the 'information' document that you can read in the 'error screen' ?

       

  • your error was not an memory error (as mine)

    <Message>The type initializer for 'NativeMagickImageCollection' three an exception</Message>

    but at the same function 'Articulate.Design.Shapes.Picture.AddVectorData' like my problem

    => svg export while publish

    with version 3.63 the import/export of images (and svg) was changed

    https://articulate.com/support/article/Articulate-Storyline-360-Version-History

    Fixed: We improved how Storyline 360 handles images during import and in the published output, resulting in crisper images.

    in principle a good fix, which finally solved the problems with PNGs without transparency

    before PNG (24 bit)  where imported as jpeg (quality 60) und exported as very big PNGs with transparency (and visible jpeg artefacts)

    it seems the many variations svg and the using svg  in storyline was not testet complete for this fix

    Jürgen

     

  • Thank you for time and effect in replying !

    And for the link with the version upgrades > I will a close eye on this one !

    Downgrading solved the problem, so I can keep my deadlines.

    Freddy