Publish Failed: Captivate 7.0

Published the file to swf yesterday. Worked great. Today it' won't work. Made only minor text change

Hi There,
Can you please confirm exact version of Captivate 7 by going to Help > About Adobe Captivate ?
Try to launch Captivate in an admin. mode by right click on it and choose run as administrator, also try to copy all the slides and paste in a new blank project and then try to publish a SWF.
You can also try to hide those slides on which you have done the minor text change and then try to publish a SWF in order to identify the issue.
Regards,
Ajit

Similar Messages

Publish Failed: Captivate 6.1, Mac OSX 10.8.5

I am experiencing the dreaded and unhelpful "Publish Failed" error message as well. I receive the message only when I am publishing a project with a quiz; projects without quizzes publish without any issue. I am publishing only to SWF output. I am running the latest build of Captivate: 6.1.0.319. I'm running a MacBook Pro Retina on OSX 10.8.5.
Reading through similar previous threads, I saw mention of a file named "Default.html" to be found in ../Publish/SCORM/Default/1_2.
But the file I find residing there is named "Default_HTML5.html". I don't know if this makes any difference.
I have deleted the plist file as well. Still no joy.
Please, I am open to any suggestions. Thanks in advance.

Hi There,
Greetings from Adobe.
Please try the below steps and see if it works for you:
It seems that Defaul.htm is missing from your SCORM folder . I am sending you the Zip file. Please unzip it and replace it with the SCROM folder already located on Captivate installed location. Please follow the below steps:
Download the zip file from the following link - https://workspaces.acrobat.com/?d=pjLGDuZsiduZy79qoEcDEw
Unzip it.
Take the backup of the SCORM folder present at “/Applications/Adobe Captivate 6/Templates/Publish/”
Replace the one with the unzipped folder.
Re-launch the captivate.
Open the captivate project which has SCORM1.2 reporting.
Re-Publish it.
Let me know if you still face the same issue.
Regards,
Mayank

Preview/Publish Fail & Freeze in Captivate 5

I'm experiencing freezing & "publish failed" messages when I attempt to preview or publish my project. My project contains 1 slide with a text caption and 40 slides recorded as a demo with no audio. I've attempted:
clearing the cache
reducing the project size
copying recorded slides to a blank presentation
installing the latest Captivate 5 update
I have many other similar projects without this problem. Nothing seems to be working!

I had a similar problem when I tried to publish a project in Captivate 5 that I had first created in Captivate 3. This problem did not happen with every 3 --> 5 conversion, only in some projects. Very mysterious.
For me, I noticed that it ALWAYS froze during each Publish attempt at EXACLTY the same spot around 41%, so that caused me to become suspicious: What was around 41% of the way through my slideshow that was unique/different/unusual?
Finally I realized that there was a slide part way through the project in which I had used a quiz feature in Captivate 3 that was not available in Captivate 5, So, when I deleted that slide and re-did it in Captivate 5, the publish worked fine.
Just thought I would throw this in for consideration in case:
your project was actually created in Captivate 3 first and now you are publishing in 5.
if your project freezes at exactly the same spot during each publish, you can investigate slides around that area to determine if there is anything unique/different/unusual

Why do I get Publish Failed Error Message when trying to publish a project to SWF. I am using Captivate 6 (32 Bit) Version 6.0.1.240. I have tried clearing the Cache and renaming my Preferences folder

Why do I get Publish Failed Error Message when trying to publish a project to SWF. I am using Captivate 6 (32 Bit) Version 6.0.1.240. I have tried clearing the Cache and renaming my Preferences folder

Try the troubleshooting tips here:
http://www.infosemantics.com.au/adobe-captivate-troubleshooting/basic-troubleshooting-tech niques
You may have something in your project on one of the slides that is tripping up the publishing process.

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

Publishing in Captivate 5

I've been attempting to publish a Captivate 5 project using any of the publishing features available and nothing will publish. I'm receiving a "publish failed" for the SWF file, the exe won't execute and the F4v file locks up at 41%. I'm running a Windows 7 machine and have cleared the cache among other suggestions I've read on this site. Nothing seems to be working. Any suggestions? Thank you.

I attempted this and yes, it finally worked. Thank you so much! I was losing my mind. Have a great day. Sharon

Error when publishing in Captivate 7

I am having an issue when trying to publish a file in any format other than PDF.
We have a CornerStone LMS system which we would like to be able to publish in a SCORM 2004 format but when we go through and set all of the configurations to publish in this format the publish will get to about 28% and return an error message of "Publish failed." with no further explanation.
Could anyone help???

Totally spitballing here...I have run into this as well. Have you tried removing the ampersand from the name of the file you are publishing. I have had problems in the past with captivate and characters.

Why do I get "Publish Failed" when I select F4V with fixed frame rate?

I have created several projects from scratch in Captivate 5. My publishing functionality seems to be increasingly impaired. I have rebooted and uninstalled + reinstalled Captivate 5.
In the beginning I got this message when I was publishing a specific project with the media option F4V with fixed frame rate, but now I am getting it on all my projects regardless of my publishing selections.
I am running on Windows 7, and I think it is Windows that is suggesting that I 'debug' the program. Clicking 'Debug' takes me to a dialog box where I can choose between Visual Studio 2005 or Visual Studio 2008, none of which seem to be a good solution.
Here is a print of my publishing options:

Chinmay Baid,
Thank you for your reply - over the past few days I have been able to
narrow the problem down a little more.
When working with Captivate 5, I am able to work with and open any
published file until I turn that file into a Zip file. Upon unZipping,
the file becomes unusable by my computer and by my LMS (Cornerstone).
I am using Adobe Flash Professional CS5 and I am able to run any SWF file
on my machine if the file has never been zipped. I am using Captivate 5
in administrator mode. Somehow, the zip process is making the files
unusable, and my LMS requires that files be zipped before they can be
uploaded.
Thank you for any advice or help you may be able to offer.
Daniel Spray
Instructional Design Specialist
United Spermarkets, LLC
806.791.6329
From:   Chinmay Baid <[email protected]>
To:     Daniel Spray <[email protected]>
Date:   03/03/2011 05:09 AM
Subject:        Why do I get "Publish
Failed" when I select F4V with fixed frame rate?
Hi,
Can you please give the following details :
Can you please check and tell the Flash player version
(plugin,activex,standalone) installed on your machine?
Also, are you able to play the standalone SWF on your machine?
Did you launch Adobe Captivate 5 in administrator mode?
Above information might be helpful for further investigation.
Regards
Chinmay Baid
http://blogs.adobe.com/captivate

AppV5 Office 2013 (Visio) couldn't get published (failed configuration in folder ProgramData\App-V 0x7D401F30-0x5)

Environment:
Server: AppV 5 SP1 Pub and Mgmt server (no Hotfixes applied)
Client: Windows 7 SP1 x64 with AppV 5.0 SP2 client (tried RTM and with HF5)
Created a Visio 2013 package with ODT (latest version). Only Visio, no other products added. Used the PACKAGEGUID to specify a custom PackageGUID.
Configuration.xml;
<Configuration>
<Add SourcePath="C:\Temp\" OfficeClientEdition="32" >
<Product ID="VisioStdVolume">
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="fr-fr" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="VisioStd2013Setup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="PACKAGEGUID" Value="0123e69c-b152-4c70-b178-41be0d2b7d1b" />
</Configuration>
Adding and Publishing locally with Powershell works like expected. But using the App-V 5.0 Mgmt/Publishing server it fails on all clients.
Package is published to computers.
Domain Computers have READ permission on the AppV Content share.
Previously Office 2013 packages could be published without any errors.
AppV logs:
Event ID: 19104:
Part or all packages publish failed.
published: 0
failed: 1
Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.
Event ID: 1008
Package {0123e69c-b152-4c70-b178-41be0d2b7d1b} version {5197e402-1206-4940-bd96-a0597e7d4b1f} failed configuration in folder 'C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F' with error 0x7D401F30-0x5.
Event ID: 4001
The App-V client failed to create a process for machine script event AddPackage with command line: '"C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=0123e69c-b152-4c70-b178-41be0d2b7d1b PackageRoot="C:\ProgramData\App-V\0123E69C-B152-4C70-B178-41BE0D2B7D1B\5197E402-1206-4940-BD96-A0597E7D4B1F\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=FN8TT-7WMH6-2D4X9-M337T-2342K,YC7DK-G2NP3-2QQC3-J6H88-GVGXT,C2FG9-N6J68-H8BTJ-BW3QX-RM3B3 PRIDName=VisioStdVolume'. Windows error: Access is denied.. The path must be a Windows application (.exe file).
Analytic and Debugs logs aren’t very helpful (Client-Publishing):
No package published.
Published: false
Failed: 0
So, Access denied (0x5) on Integrator.exe in ProgramData? As we have AppLocker in place, checked the AppLocker logs. But no trace in there.
Other AppV5 applications does work
Tested on two different App-V 5 Pub Servers (5.0 SP1 and SP1 with HF4), same behaviour.
Tested on three Win7 SP1 x64 clients, same behaviour.
EnablePackageScripts (client config) is enabled on all clients.
Issue was
reported before on the forums, but Domain Users and Domain Computers have already READ permissions to the AppV Content Share (NTFS permissions) where the .appv file is stored.
Added (as a test) Domain Computers and Everyone Full Control to c:\ProgramData\App-V, doesn’t solve it.
Cannot use ProcMon, because the Publish event occurs before user login.
I’m out of ideas. Someone that could assist me please?

The above fix was a lucky shot.
This solved it (hopefully) for good;
http://www.the-d-spot.org/wordpress/2014/11/05/appv5-office-2013-package-cannot-be-published-access-is-denied-on-integrator-exe/

Publish failed (when using Calendar instead of GregorianCalendar..)

I have a web service written in Workshop 9.2.2 running on a WLS9.2 Server.
One attribute in my web service is of type java.util.Calendar. Now when I try to publish that I get a "Publish Failed" almost immeditately.
HOWEVER, when I change the type of the attribute to java.util.GregorianCalender, the publish works fine...
This seems like a bug to me, as the WLS doc says that I should use Calendar as a data type for dates in web services and it clearly supports it.
Can I upgrade to the latest version of Workshop and continue using WLS9.2?
Here's the log file:
!ENTRY com.bea.wlw.server.core 1 2000 2008-03-19 15:35:59.994
!MESSAGE Releasing deployment manager @0
!ENTRY com.bea.wlw.server.core 1 2000 2008-03-19 15:35:59.994
!MESSAGE Publishing finished.
!ENTRY org.eclipse.wst.server.core 4 0 2008-03-19 15:36:00.10
!MESSAGE Publishing failed
!SUBENTRY 1 com.bea.wlw.server.core 4 0 2008-03-19 15:36:00.10
!MESSAGE Error with publish task 'WebServicesProjectBuildTask'.
!SUBENTRY 2 com.bea.wlw.webservices.core 4 4 2008-03-19 15:36:00.10
!MESSAGE Error while compiling web services in WL92WS.
!STACK 0
com.bea.wlw.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\bea\user_projects\w4WP_workspaces\WSTest\WL92WS\src\webservices\contentreceiver\ContentReceiverService.java
     at com.bea.wlw.webservices.core.compiler.WebServiceCompiler$3.invoke(WebServiceCompiler.java:249)
     at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.accessCompiler(WebServiceCompiler.java:291)
     at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile0(WebServiceCompiler.java:244)
     at com.bea.wlw.webservices.core.compiler.WebServiceCompiler.compile(WebServiceCompiler.java:202)
     at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.build0(WebServiceProjectCompiler.java:157)
     at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.access$0(WebServiceProjectCompiler.java:119)
     at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler$1.run(WebServiceProjectCompiler.java:92)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1721)
     at com.bea.wlw.webservices.core.compiler.WebServiceProjectCompiler.build(WebServiceProjectCompiler.java:108)
     at com.bea.wlw.webservices.core.publish.WebServiceProjectPublishTask$WebServicesBuildOperation.processWebServices(WebServiceProjectPublishTask.java:119)
     at com.bea.wlw.webservices.core.publish.WebServiceProjectPublishTask$WebServicePublishOperation.processWebModule(WebServiceProjectPublishTask.java:53)
     at com.bea.wlw.server.core.model.WeblogicWebPublishOperation.processRootChildModule(WeblogicWebPublishOperation.java:118)
     at com.bea.wlw.server.core.model.WeblogicWebPublishOperation.processRootModule(WeblogicWebPublishOperation.java:84)
     at com.bea.wlw.server.core.model.WeblogicPublishOperation.execute(WeblogicPublishOperation.java:72)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.performTasks(WeblogicServerBehaviour.java:786)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:434)
     at com.bea.wlw.server.internal.core.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:332)
     at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:803)
     at org.eclipse.wst.server.core.internal.Server.publish(Server.java:791)
     at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\bea\user_projects\w4WP_workspaces\WSTest\WL92WS\src\webservices\contentreceiver\ContentReceiverService.java
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:471)
     at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:439)
     at com.bea.wlw.webservices.core.compiler.WebServiceCompiler$3.invoke(WebServiceCompiler.java:247)
     ... 20 more
Caused by: weblogic.wsee.tools.WsBuildException: java.lang.IllegalArgumentException: 'java.util.Hashtable<java.util.Locale,int[]>' does not name an array
     at weblogic.wsee.tools.jws.WebServiceInfo.createBindings(WebServiceInfo.java:219)
     at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.process(WsdlBuilder.java:41)
     at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:36)
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:467)
     ... 22 more
Caused by: java.lang.IllegalArgumentException: 'java.util.Hashtable<java.util.Locale,int[]>' does not name an array
     at com.bea.util.jam.internal.elements.ArrayClassImpl.normalizeArrayName(ArrayClassImpl.java:100)
     at com.bea.util.jam.internal.JamClassLoaderImpl.loadClass(JamClassLoaderImpl.java:80)
     at com.bea.util.jam.internal.classrefs.QualifiedJClassRef.getRefClass(QualifiedJClassRef.java:80)
     at com.bea.util.jam.internal.elements.FieldImpl.getType(FieldImpl.java:89)
     at com.bea.staxb.buildtime.Java2Schema.isJaxRpcEnumType(Java2Schema.java:1646)
     at com.bea.staxb.buildtime.Java2Schema.checkPropertyConstructors(Java2Schema.java:1829)
     at com.bea.staxb.buildtime.Java2Schema.processProperty(Java2Schema.java:1753)
     at com.bea.staxb.buildtime.Java2Schema.bindProperties(Java2Schema.java:1368)
     at com.bea.staxb.buildtime.Java2Schema.createBindingTypeFor(Java2Schema.java:855)
     at com.bea.staxb.buildtime.Java2Schema.findOrCreateBindingTypeFor(Java2Schema.java:676)
     at com.bea.staxb.buildtime.Java2Schema.createBindingTypeFor(Java2Schema.java:804)
     at com.bea.staxb.buildtime.Java2Schema.findOrCreateBindingTypeFor(Java2Schema.java:676)
     at com.bea.staxb.buildtime.Java2Schema.internalBind(Java2Schema.java:440)
     at com.bea.staxb.buildtime.BindingCompiler.bind(BindingCompiler.java:125)
     at com.bea.staxb.buildtime.BindingCompiler.bindAsExplodedTylar(BindingCompiler.java:161)
     at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1311)
     at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:214)
     at weblogic.wsee.tools.jws.WebServiceInfo.createBindings(WebServiceInfo.java:215)
     ... 25 more
!SUBENTRY 1 com.bea.wlw.server.core 4 4000 2008-03-19 15:36:00.72
!MESSAGE Error(s) occurred during publish assembly. No modules will be published.

Hi
This looks like a known issue. I see that its fixed in Workshop 10.0 onwards.
If you want a fix for 9.2 version please open up a BEA support case at http://support.bea.com . Please refer to the Cr's CR340337, CR360247 when opening the case.
Can I upgrade to the latest version of Workshop and continue using WLS9.2?Yes, you can. With the latest version of workshop you can develop applications against WLS9.2.x and WLS10.x. So you would be able to use the same app on 9.2 on the latest workshop version.
Vimala-

ICal Publish failed

After starting a new .Mac family pack membership. I changed my .Mac user/pass in System Prefs, and "unpublished" the calendars in iCal.
Now, when I go to Publish them I get
Publish failed for calendar 'Main'.
Request to the server failed.
Which seems like a connectivity problem but I can Sync perfectly with .Mac and also access my iDisk ok.
I have tried deleting a calendar and re-creating it. I also tried publishing a brand new calendar. Those gave the same errors, so I don't think the problem is in the calendar itself.
This is lame of course, because a main reason for my changing to the family pack was so my workgroup could all publish for group calendaring.
Any help would be greatly appreciated, thanks.
David

Apple helped me finally fix this problem. Go into System Prefs, .Mac.
Go to the iDisk tab, and change your Public Folder settings to Read and Write. (This is a temporary change)
Next try several things to test it. Try opening your iDisk from the Finder. Try writing to the iDisk inside a folder such as "Documents".
When I had this problem, the iDisk would not allow writing, and would fail with a disk space error.
You can also test Backup, or Calendar publish now. If everything is working, you can reset the Public Folder settings to Read Only.
What Apple explained to me via phone, is that there was a permissioning error when the new account was originally set up. Somehow, setting it to Read/Write fixes these permissions, and then you can work with all .Mac features as intended. If you still further probs, I recommend requesting to Apple support that they escalate your request to a more highly qualified engineer, and arrange a phone call. That was the deal for me, and he had it fixed in 2 minutes, after months of frustration.
Best,
David
CEO, Clearlightpictures.com

NetStream.Publish.Failed

I'm trying to connect 2 swfs over Stratus and the second client is getting NetStream.Publish.Failed when I try to publish a stream. They both have connected to Stratus via the NetConnection and one can publish a stream but the second can not. I've made sue that each swf is using a different name to publish. I can't find this error listed anywhere in the documentation it only listed NetStream.Publish.BadName. I'm using the AIR 2 RC1 beta sdk from adobe labs set to publish for 10.1.
Are there any other reasons why i would be getting NetStream.Publish.Failed?

I found out why it was failing. I was entering the peerID I wanted to allow connection from instead of allowing any direction connection.
so I had:
stream = new NetStream(connection, farID);
stream.publish( channel );
where is should be:
stream = new NetStream(connection, NetStream.DIRECT_CONNECTIONS);
stream.publish( channel );
then the other client needs to use both my farID and name of my stream in order to connect

Every time I publish my captivate 6, the backgrounds change? Anyone have this problem? Or a solution

I am trying to publish my captivate 6 simulation. I just published it, the backgrounds keep changing or don't pull through and I have a blank screen. Any solutions to this problem?

Hello,
Is this 6.0.1.240? In that case check the slide quality, and if it is the default Low, change to Optimized (new default since 6.1.319).
Moreover uncheck all compression settings in Preferences, Project, SWF size and Quality. And check 'Force re-publish all slides' when publishing.
Lilybiri

Getting a black screen when publishing in Captivate 4.

I am getting a black screen when publishing in Captivate 4. I have noticed patches that care for this with later versions, but is there something available for version 4.

Thank you for your reply, I work for Citi and am personally unable to make decisions about updating our Flash player version. Is there a patch for this issue for Captivate 4?
Date: Mon, 4 Feb 2013 13:29:16 -0800
From: [email protected]
To: [email protected]
Subject: Getting a black screen when publishing in Captivate 4.
    Re: Getting a black screen when publishing in Captivate 4.
    created by Shekhar_Dhiman in Adobe Captivate - View the full discussion
Hi there, Thanks for reaching Adobe Community. Please accept my apologies for the same. Try updating your Flash Player to the latest version and then republish the project. This black screen issue was first discovered few months ago after the first Flash Player 10 release. The link to download the latest version of flash is here: http://get.adobe.com/flashplayer/ Newer versions of Flash Player do not result in the same issue. Thanks!Shekhar
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5047261#5047261
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5047261#5047261
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5047261#5047261. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Adobe Captivate by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Scheduled Publish failed

Hi,
i have a Scheduled realtime Publish,but it failed,could you help me?Thank you!
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event ApprovalQueue was not executed as another cluster member has executed it.
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:45:00 CST 2015
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event PublishEvent_1422966231808 was not executed as another cluster member has executed it.
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:35:00 CST 2015
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Event CacheServer was not executed as another cluster member has executed it.
[2015-03-04 16:30:04,674 CST] [INFO ] [ool-4-thread-1-Event-Heartbeat] [fatwire.logging.cs.event] Next attempt to run it will be around Wed Mar 04 16:35:00 CST 2015

Can you explain more about the failure? Are you saying the event did not run on time or the publishing failed?

Publish Failed: Captivate 7.0

Similar Messages

Maybe you are looking for