Skip to main content
December 6, 2012
Question

Swf compilation Failed.

  • December 6, 2012
  • 1 reply
  • 2300 views

How do I get rid of this error!!!! I have read through your discussion thread for hours and see tons of people with this issue. I see no explanation of how to resolve it. What good is this program if I can't use it?

I have re-installed Captivate, Updated Java and Flash. I tried to even create a new project with only pages created from your templates and no outside info and I still get "Please verify if any of the actionscript is used as user variable name."

Some one said to remove the JAVA_TOOL_OPTIONS environment variable. I have no idea what that is or where I would remove it from. non of the other suggestions to fix this issue have worked.

    This topic has been closed for replies.

    1 reply

    Sankaram
    Adobe Employee
    Adobe Employee
    December 7, 2012

    Hi esilver35,

         SWF compilation can come for following reasons:

    1) If you use action script keywords in Captibvate project variables.

    Resolution: Make sure you don't use action script keywords.

    2) If you have invisible characters present in text fields.

    Resolution: Don't Copy/Paste text from some other application to Captivate text fields like Project information etc. Type with key board. Create a blank project and publish, if you still get SWF compilation issue then your 64 bit JVM might be corrupted.

    3) if your installation is 64 bit Captivate, 64 bit JVM might be corrupted.

    • Add  Use32BitJVMForPublish = 1  in AdobeCaptivate.ini  file
    • Close and Re-launch Captivate.
    • Re-publish the project

    Captivate ini file is present at “C:\Program Files\Adobe\Adobe Captivate 6 x64” location

    You can send me a mail at sankaram at adobe dot com if it still doesn't resolve the issue.

    Thanks,

    Sankaram.

    December 7, 2012

    JVM was corrupted. Thank you so much for the quick response and detailed resolution to my issue. Files are all previewing and publishing fine now.


    Thanks,
    Ethan