Questionmark Publishing Error

Report · May 17, 2012

Good morning everyone,

Still having problems when publishing a Captivate 5.0 module with reporting enabled for Questionmark Perception.

The problem occurs right at the very end of the progress bar for publishing when I get the dreaded "Captviate 5.0 has encountered a problem and must shut down". This means I can't create the .qml file to upload to Questionmark.

The module it is occuring on right now is 69 slides in length with a file size of 4.04MB. I think the issue has something to do with file size but normally don't have a problem with those in the 50 to 60 slide size area.

Adobe offered to help and then vanished on me when I sent them a file to test. Haven't heard a word since then.

Any ideas what the heck is occurring here? I'm attaching my 'preferences' so you can see my settings.

Thanks a bunch and a nice bottle of wine to anyone who can fix this issue. I'll even pay for shipping!

Chuck

Report · May 18, 2012

Hi Chuck,

Is it happening with all the projects/Quiz? Can you please try it with some test quiz.

Also try copying all the slides of the project and paste them in the new project and then try to publish it with same preferences.

There is no such issue with Captivate not publishing the QML file. I just tried it with a bigger project and that worked fine.

Please let me know if this helped you, or else we will try some other things.

Report · May 18, 2012

Good morning AK,

Thanks for taking the time to respond. I appreciate it.

This is NOT happening with all projects. Although I can't tie it to a specific event or file, it seems to occur when my modules/files grow past the 60 slide mark. Others are publishing just fine.

I have tried a few work arounds to include the one you suggested of copying and pasting to a new project. Still no luck. I had figured that during the creation process (deleting slides, objects, etc.) that some residual mess may be causing the problem but that's not it either.

Even created a project to final status and then reaccomplished it without having to edit/delete anything...still got the error.

What happens is that when I click 'Publish' it will run throught the Generating Slides, Saving SWF Files, Compressing SWF Files, gets to 99% and then gives the error message shown below. I'm going to try and add an .avi I recorded of what is happening too.

https://plus.google.com/u/0/100892292792661351211#100892292792661351211/posts

Report · May 18, 2012

Let me try this with another test project with 60+ slides.

The video showed that when you were trying to publish the course you got the warning message, "The File already exist. Do you want to overwrite?", which means that there is already a published file at the location. can you check that location and see if there is already a published file there. If yes, please check if that file contains the .qml file.

I also checked that the publishing process actually showed 100% and then you got the error message.

Can you also share the project with us, which gives you the error while publishing.

Report · May 19, 2012

Can I also suggest that you try disabling all compression options in Preferences to see if turning them off allows your project to complete successfully?

There are three compression options on this section. Turn all of them off and see if you can publish correctly.

Report · May 21, 2012

Rod,

I appreciate the idea. I gave it a shot and still received the same error.

Sent Aditya the Captivate file itself and hoping he will be able to troubleshoot and figure out what is going on. I'm wondering if I should have my IT department reinstall my Captivate software?

I'm at a loss to figure out why this only occurs when the file reaches a certain length or size; although, I can't determine where that 'line in the sand' is at this point.

It's a very frustrating error that causes me extra work and time spent coming up with a split module or other type of work around.

Chuck

Report · May 21, 2012

Another thought: Your issue might be related to one or more questions being corrupted in some way. You can try to find out which slides are causing the issue by simply hiding the first half of all slides and republishing. If successful, then hide the second half of all slides and see if the first half will fail to publish. Proceeed this way using trial and error to narrow down to the actual slide/s where the issue occurs. This may allow you to finally get a solution.