SWF Compilation error in Captivate 7

I use Captivate 7 on mac 10.9.2. I am getting that infuriating error message "SWF compilation failed: please verify if any of the actionscript keywords is used as a variable name" .I have successfully completed 5 projects and put them up to Blackboard using SCORM 2004 with no problem. This looks exactly the same but dies at the first slide which will not preview in webrowser, but from slide 2 it shows lots of five slides with no problem. There doies not appear to be any actionscript keywords as a variable name - only 5 user variables and they're all the pre-laoded ones. Any ideas? This seems to be a common problem but the forums don't seem to have an answer. If anyone can crack this they will be a small hero.

Don't believe everything you see in Captivate error messages. The issue may not necessarily be an actual variable name. It could be related to the name of an advanced action, a screen object, or even a slide. If the name of any object happens to transgress into territory of actionscript keywords it can cause an issue.
The other thing that can sometimes cause these errors is using punctuation characters in names or fields or even CC text.
From what you describe, the issue would appear to be related to something on either the first few slides or else something that gets loaded right at the start of the project.
What happens if you hide the first few slides? Does it then publish without issue?

Similar Messages

Unable to publish in Swf format. Get error message: 'Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name'. Anyone know how to fix?

Unable to publish in Swf format. Get error message reads: 'Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name'. Anyone know how to fix?

Hi There,
Can you tell me the Operating System and Captivate version you are using?
Also can you confirm if you are getting this issue will this one project or all the projects? Try to copy paste this project on a new blank project and then try to publish.
Regards,
Mayank

Getting "Swf compilation failed" error

Whether trying to publish a simple PowerPoint presentation from Captivate 6 or Captivate 8 (Trial), I am getting the following error:
Swf compilation failed.
Note: Please verify if any of the actionscript keywords is used as user variable name.
Does anyone know what this error means? I am not using any variables.
Gigi Weiss
[email protected]

Hi There,
Please try the below steps and check if it helps :
Go to C:/programfiles/Adobe/Adobe Captivate(version)/AdobeCaptivate.ini
Open the file with notepad and add the line Use32BitJVMForPublish=1
Save it and Try to publish the project .
Regards,
Mayank

When I publish a SWF/HTML5 module with Captivate 8 and try to run it using IE9 - I get the following error "The content you are viewing is not supported in the current Document Mode" - anyone know why?

When I publish a SWF/HTML5 module with Captivate 8 and try to run it using IE9 - I get the following error "The content you are viewing is not supported in the current Document Mode" - anyone know why?

TLCMediaDesign wrote:
I've seen a lot of threads about getting rid of these kind of messages. Those messages are there for a reason most of the time. If you have CSS animations or other HTML5 standards that cannot be rendered in IE9 they won't magically start working becuse you got rid of a message. I use IE9 since that is the minimum standard for the client. I have never seen that message publishing to HTML5 content.
IMO, if your client has IE9 I think that you should develop with IE9 in mind not IE11.
When you say "develop with IE9 in mind not IE11" do you mean use SWF instead of HTML5? I used the standard question types, and a converted PowerPoint presentation. I didn't add anything out of the ordinary.

When publishing a captivate I get the message "Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name." and it won't allow me to publish the Captivate, can anyone help?

When publishing a captivate I get the message "Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name." and it won't allow me to publish the Captivate, can anyone help?

Hi There,
Can you tell me the Operating System and Captivate version you are using?
Also can you confirm if you are getting this issue will this one project or all the projects? Try to copy paste this project on a new blank project and then try to publish.
Regards,
Mayank

Error: "SWF Compilation Failed"

I am currently working on updating an old CP4 file. While I can open and save the file in both CP5 and CP5.5, I am unable to preview in browser or publish the file. Instead, I receive the error "Swf compilation failed. Note: Please verify if any of the actionscript keywords is used as user variable name/"
After reviewing some of the discussion items on the forum, I was able to try some fixes, but with no luck. The project does not contain:
Double quotations anywhere in project information or name
User Variables
I also tried removing any text entry boxes, but that did not solve the problem either. Oddly, I have had several separate projects to update and only one has this issue. It is preventing me from updating the file.
Any help on how I can update and publish the file is appreciated.

Hello,
Welcome to Adobe Forums.
Did you tried copy and pasting all the slide of this project to a blank project ?
Note : If the above step do not work, then try this :
1) Copy 5 slides and publish
2) If publish is successfull, try another 5 and publish again
By these steps you will find the slide which has issue.
Thanks,
Vikram

Swf compilation failed--error msg

This is an ordinary project with no user-made variables. I had been working for hours, adding effects to text when I got this msg which went on to say, "Note: Please verify if any of the actionscript keywords is used as user variable name."
I rebooted the project, and still got the message when I would try to save or preview.

Hi Lillbiri,
I am running into the same problem as mentioned above. When I try to publish as a SWF I get the warning
"swf compilation failed. Note: Please verify if any of the action script keywords is used as a variable name." When I asked Adobe chat about this they said it is caused by having a special character in one of my names. I went through each slide and do not have any special character in my slide names. Could it be caused from naming multiple slides the same thing?

Swf compilation Failed.

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.

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.

SWF Compilation Failure Note: Please verify...

I'm using Captivate CS6 on an MBP running 10.7.5. I am unable to publish files that I wsa able to publish just yesterday. I am getting the message "SWF Compilation Falure. Note: Please verify if any of the actionscript keywords is being used as user variable name."
I made sure Java was updated and on.
Any ideas?

Can you check a new blank project if that also gives you an error?
Please verify if you have any update pending to be installed for Java on your MAC?

SWF Compilation Failed with "Submit All" Option

Hi,
I am using Captivate 6.1 and created a quiz with single choice questions. When I turn on the "Submit All" option, I can not preview/publish the file anymore. It says "SWF Compilation Failed." and I am advised to check if any user variables contain AS keywords. I am not using any user variables in this project. Whenever I turn the "Submit All" option off, preview/publish are possible again.
When publishing to HTML5, the error does not occur.
Can you please help me with this issue, since I would appreciate using the "Submit All" option.

Hi
Check this forum : http://forums.adobe.com/thread/1111120?tstart=0
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
Thanks,
Vj

Flex 2 Compatibility? Seeing StreamingAMFChannel compile error

I have seen postings such as http://tjordahl.blogspot.com/2008/03/blazeds-and-flex-2-compatibility.html suggesting that BlazeDS is compatible with the latest versions of Flex 2 SDK. My experience shows that this may not be completely true. In Flex Builder 3, I have created a project using Flex 2.0.1 Hotfix 3 SDK. This points to: C:\Program Files\Adobe\Flex Builder 3\sdks\2.0.1 which is build 180927. I have code like this: public function sendRequest(): void { var ro:RemoteObject = new RemoteObject(); ro.addEventListener(ResultEvent.RESULT, resultHandler); ro.addEventListener(FaultEvent.FAULT, faultHandler); if (_channelId != null && _channelUrl != null) { var cs:ChannelSet = new ChannelSet(); var myChannel:AMFChannel = new AMFChannel(_channelId, _channelUrl); myChannel.pollingEnabled = true; myChannel.pollingInterval = 8000; cs.addChannel(myChannel); ro.channelSet = cs; } ro.destination = "myService"; ro.channelSet = cs; ro.myOperation(); } When compiling this I get the following error message: Channel definition, mx.messaging.channels.StreamingAMFChannel, can not be found. Even when I comment out the above code referencing AMFChannel, the compile error still occurs (even when doing a "clean" build). Here are the relevant compiler settings: <?xml version="1.0" encoding="UTF-8"?> <actionScriptProperties mainApplicationPath="client.mxml" version="3"> <compiler additionalCompilerArguments="-services "C:\tomcat_blazeDS\webapps\myservice\WEB-INF\flex\services-config.xml" -locale en_US" copyDependentFiles="true" enableModuleDebug="true" flexSDK="Flex 2.0.1 Hotfix 3" generateAccessible="false" htmlExpressInstall="true" htmlGenerate="true" htmlHistoryManagement="true" htmlPlayerVersion="9.0.28" htmlPlayerVersionCheck="true" outputFolderLocation="C:/tomcat_blazeDS/webapps/myservice/swf" outputFolderPath="bin-debug" sourceFolderPath="src" strict="true" useApolloConfig="false" verifyDigests="true" warn="true"> <compilerSourcePath/> <libraryPath defaultLinkType="1"> <libraryPathEntry kind="4" path=""> <modifiedEntries> <libraryPathEntry kind="3" linkType="4" path="${PROJECT_FRAMEWORKS}/libs/framework.swc" useDefaultLinkType="true"> <crossDomainRsls> <crossDomainRslEntry autoExtract="true" policyFileUrl="" rslUrl="framework_3.0.0.477.swz"/> <crossDomainRslEntry autoExtract="true" policyFileUrl="" rslUrl="framework_3.0.0.477.swf"/> </crossDomainRsls> </libraryPathEntry> </modifiedEntries> </libraryPathEntry> <libraryPathEntry kind="1" linkType="1" path="libs"/> <libraryPathEntry kind="3" linkType="1" path="myCore.swc" useDefaultLinkType="false"/> </libraryPath> <sourceAttachmentPath/> </compiler> <applications> <application path="client.mxml"/> </applications> <modules/> <buildCSSFiles/> </actionScriptProperties> Any comments on whether this should work, and is supported? If this is expected to work, I would also appreciate some ideas on work-arounds. Thank you, David

David,
Even when you comment out the channel (actually all channels) that has the
reference to mx.messaging.channels.StreamingAMFChannel this still doesn't
work?
Are you sure that FlexBuilder is pointing at the right services-config.xml
file when it compiles the MXML? It can't point at a BlazeDS 'default'
config.
It sounds like the problem is that the Flex2 libraries in the swf are trying
to load that channel class which is new for Flex3 and it isn't there.
Removing any and all references to this class in the config files used to
compile the swf should fix it.
Let us knwo if that isn't it.
Tom Jordahl

Flash limitations, Invisible Compiler Errors, swc files...

This question is for expert users of Flash CS4/CS5 and actionscript.   Please do not comment or offer suggestions if you have no experience with these errors or their causes.
===================================================
Question:
=======
Publishing an extremely complex file can sometimes result in a blank swf being created, and no compiler errors being shown even though some may exist.   Are there any suggested methods for dealing with this?
=======
Details:
=======
Those who have written flash files with large actionscript components will be familiar with needing to set the JAVA_TOOL_OPTIONS evinronment variable in order to prevent the Flash compiler from crashing due to memory limits. The majority of the files in question require this as a bare minimum in order to be compiled at all.
The project in question involves several main "launcher" components, in addition to hundreds of "modules". The modules themselves are being developed in a distributed manner by several programmers. Each module can be executed as a standalone swf, for testing and production purposes. Each module has a companion swc file which holds its assets and exports them. All of the modules make use of a shared custom code library that sits on top of actionscript.
The launcher program also uses the shared library code, and runs the modules (never more than one at a time, and clearing previously loaded ones before loading a new one) inside of itself. The launcher contains a reference file(the class names typed in an include file, referencing all of the available exported assets from the swcs) that makes all the necessary assets available to the modules, such that any module can be run at any time.
===========
The Error:
===========
Seemingly random in occurence, every now and then a file will "compile blank". Essentially, the compile time is very short, the swf pops up as a blank white box, and there is absolutely nothing listed in the "Compiler Errors" tab, nor in the output tab. Sometimes closing flash and relaunching it will bring the Compiler Error messages back, though usually not. More often opening the file on another computer in a different copy of flash and compiling it again will show the errors.   The original computer will still not show anything, but the other computer can be used to fix the error, and then the file will start reporting errors again properly.
However, sometimes, the file will "compile blank" on all computers, and all copies of flash. Then the only resort to find the hidden errors and fix them, is to comment out the entire file, and slowly uncomment out sections one at a time. In this manner, the area where the hidden errors are occuring can be determined, and the error found manually.
Obviously this is an extremely frustrating situation, but one that can be "worked around".
However, there are two more serious incarnations of this which cannot be as easily side stepped.
1.) Sometimes certain computers/copies of flash will "compile blank" a file that doesnt actually have errors in it. The same file will compile and work perfectly on one machine, and not on another.
2.) The most severe of all...The two more complex components compile fine in cs4, but always "compile blank" on cs5, no matter what. The module files all compile much faster on cs5 and work great. However, the shared code library and the launcher program cannot be compiled in cs5, though they compile fine in cs4.   Both compile blank every single time on cs5, with no errors reported.
--Just as a side note here are the compile times on two different types of computers, for cs4 and cs5, for the three types of compiled files:
=====================
CS4 Compile time averages:
=====================
Dual Core - Pentium 4:
        Module File = 1-4 minutes
        Shared Code Library = 10+ minutes
        Launcher Program = Unusable
6 Core AMD w 16 GBs of RAM:
         Module File = less than 10 seconds
         Shared Code Library = approx. 1 minute
         Launcher Program = 15-25 minutes
=====================
CS5 Compile time averages:
=====================
Dual Core - Pentium 4:
        Module File = less than 20 seconds
        Shared Code Library = 2-4 minutes
        Launcher Program = Compiles blank
6 Core AMD w 16 GBs of RAM:
         Module File = less than 10 seconds
         Shared Code Library = less than 30 seconds
         Launcher Program = Compiles blank
========================================
Summary:
========================================
1.) Large and complex files in cs4 or cs5 can sometimes false compile, showing a blank swf, and no errors.
2.) Large interlinked projects containing many swcs that can compile on cs4 always compile blank on cs5
The issues involved "appear" to deal with interlinked swcs and swfs, memory, and compiler messages.
The best solution i can think of would be some sort of verbose mode setting, where the cs4/cs5 compilers can be set to trace all the actions they are taking, either to a log file, or to the screen. Rather than simply giving a summary of the results, a real-time display of what is occuring might lead to the actual bugs/issues.
Eisley79

For the future people who come searching this forum and find my thread.
http://kb2.adobe.com/cps/405/kb405257.html
Above is a link to adobe's official version of admitting this situation exists(and its true for cs5 as well).
If you are reading this, and simply have a single large file that won't compile. Attempt their solutions suggested. Also, click the link in the comments by the user refering to a blog that helped him.
That will explain the JAVA_TOOL_OPTIONS memory issue (which you can find many explanations on google as well).
If however, you are working with a large number of separate swf's that load each other, and share assets and are getting the REAL problem, neither adobe's solutions, nor the JAVA_TOOL_OPTIONS will correct the problem for you. My best suggestion to you is, have one SWF launch the next one, and break your project into pieces. Whatever the parent SWF needed to have, can be either copied into all the children SWFs, or into several "brother" SWFs which share the loaded children SWFs, (and can actually be successfully compiled). Then as you move from brother to brother, they can be made to appear as if they were actually ONE file, loading the children, instead of several launching each other, and sharing the loading duties.
and as far as adobe is concerned, if i told you what i thought of you, i would get this post deleted...and myself banned.
Anyone considering doing Enterprise level projects in Flash, DONT. I wanted to use JAVA, but my company went with flash. I am stuck working around it constantly, and would have been better off coding foundation classes to mimic whatever functionality we needed from flash into java.
Maybe when actionscript 4 comes along, it will magically bring with it true object oriented programming, and Adobe will spend the time and money to make a real working compiler. Somehow i doubt it.

SWF import error message

Hello again
I have a flash anination that works perfectly fine when
tested as stand alone, but when imported into Captivate give an
error message:
TypeError: Error #1009: Cannot access a property or method of
a null object reference.
at Testx_fla::MainTimeline/MouseClick1()
what should one be looking into to understand the possible
cause?
many thanks

It''s an ActionScript 3 compiler error as far as I can see.
Just checking but since this is an AS3 Flash component are you publishing your Captivate project as AS3?
/Michael

The mxmlc compiler displays the compilation errors in Japanese - and I want them in English!

Working in a Japanese company I have to use a machine with
Windows XP in Japanese. The thing is that I can barely read this
language so it's really depressing when most Java apps (and Flex,
through Eclipse, is one of them) outsmart themselves and default to
displaying their UI strings/messages in Japanese
without giving the user the ability to select another
language.
When compiling Flex apps using Flex Builder 2, the mxmlc
compiler is internally called by the IDE to perform the compilation
and then its output is displayed in the Problems View.
Well, the English version of mxmlc, has all its messages
(compilation warnings, errors etc) translated into Japanese (as far
as I can tell, they are hardwired into the exe). So although I'm
using the English version of the FB2,
with -locale en_US specified as an argument for the
compiler, all the compilation erros are reported in Japanese!
Even after changes in "flex-config.xml" and "jvm.config" as
you can see below, the compilation errors are still in Japanese. I
started to doubt that there's a solution to this problem but I
really hope there is one.
TIA,
.x.
Here are the relevant portions of my config files and an
example of mxmlc's output (Japanese might not display correctly):
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\frameworks\flex-config.xml --
<flex-config>
<compiler>

<accessible>false</accessible>

<locale>en_US</locale>
</compiler>
</flex-config>
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\bin\jvm.config --
# Arguments to VM
java.args=-Xmx384m -Dsun.io.useCanonCaches=false
-Duser.language=en
-- mxmlc invoked on the command line --
mxmlc -o ASCIIArt -locale en_US ASCIIArt.mxml
Loading configuration file C:\Program Files\Adobe\Flex
Builder 2\Flex SDK 2\frameworks\flex-config.xml
ASCIIArt\AsciiArtBuilder.as(7): col: 45 Error:
定義
com.example.programmingas3.asciiArt:BitmapToAsciiConverter
が見つかりません。
import
com.example.programmingas3.asciiArt.BitmapToAsciiConverter;
^
ASCIIArt\AsciiArtBuilder.as(8): col: 45 Error:
定義 com.example.programmingas3.asciiArt:Image
が見つかりません。
import com.example.programmingas3.asciiArt.Image;

inlineblue you are right about the "-locale" switch. I've
just found this page on live docs:
http://livedocs.macromedia.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=L iveDocs_Parts&file=00001500.html
with all the compiler options
I thought that "-metadata.language <code>" (alias
"-language") sets the language, but it seems that it's only for
metadata.
So -locale is out. Thanks for clearing this for me. There's
one more path left...
As I wrote in my first message, besides the "-locale en_US"
compiler option, I am also setting the "user.language" flag in
jvm.config to "en":
-- C:\Program Files\Adobe\Flex Builder 2\Flex SDK
2\bin\jvm.config --
# Arguments to VM
java.args=-Xmx384m -Dsun.io.useCanonCaches=false
-Duser.language=en
According to the docs:
http://livedocs.macromedia.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=L iveDocs_Parts&file=00001462.html
this is the standard (only?) way to pass arguments to the JVM. And
AFAIK "-Duser.language=en" is supposed to set the user language to
English. But it does not happen... I have to investigate this
more...

What triggers "swf compilation failed"?

Windows 8.1
Lenovo ThinkPad w540
Captivate 8
I can get HTML5 to publish but I cannot get ANY swfs to publish. Not even a single slide blank project? I didnt touch a single thing in it??
I have tried these options: Re: Swf compilation Failed.
I tried to uninstall and reinstall Captivate 8
I have also tried to uninstall and reinstall Java....64 bit version...
NaDa....Please help!

Hi There,
Please call us at 8008336687 or click on the link for Chat Support : Chat
with an Expert
Regards,
Mayank

SWF Compilation error in Captivate 7

Similar Messages

Maybe you are looking for