Captivate publishing errors in browser

Mac
Captivate 6
I don't know where to begin because I don't know what I did to get the following results. When I publish my files I now get the following error Error unable to acquire LMS API, content may not play properly and results may not be recorded.  Please contact technical support. Click OK to view debug information to send to technical support. First comes the Message Firefox prevented this site from opening a pop-up window. Then when I click allow I get the following message.So I will try to share files with your to show you what I'm getting.  Can anyone help? I'm totally at a loss for what to do at this point.

This error indicates you have your content set up to report to an LMS but you're not launching it from within the LMS environment.
Are you testing this content from your local hard drive or a LAN drive rather than uploading it to your LMS for testing from the web server?
If you're playing the content locally, then it's going to go in search of an LMS to talk to and find none out there.  I'd find that frustrating too.

Similar Messages

  • Adobe Captivate 6 Error when publishing

    Help!  I having trouble publishing a training that my employees can view.  When they open the project they are getting the first image here that is essentially blank.  I have attempted to reduce the size and save to different folders etc. but nothing seems to work. 

    Hi there,
    Could you tell me the complete version of Captivate (Help > About Adobe Captivate).  6.0.1.240
    Which version of Adobe Reader or Acrobat are they using?  Adobe Reader XI
    Can you publish this locally on your system (not to network drive directly), check force republish option also, and are you able to view it on your end?  I can pull up the file from my computer that is saved in the same drive that the agents are attempting to pull up.  But, I am not sure if it is viewing for me because I have it on my system.
    Re: Adobe Captivate 6 Error when publishing
    created by Varun Kalra<http://forums.adobe.com/people/Varun+Kalra> in Adobe Captivate - View the full discussion<http://forums.adobe.com/message/5855412#5855412

  • Publish Error after copying domain file from one mac to another

    Hello there,
    so here is the problem: I have had iweb installed on a MBP, and a website up and running. Now that I just bought an iMac I wanted to transfer all the iWeb over to the iMac and make it the main machine. I was doing all the transfer work manually rather than using the migration assistant or time machine.
    I have copied the domain file in the iWeb directory over to the iMac. iWeb starts and displays all the pages and sites normally, but when I try to publish I get the " Publish Error. An unknown error occurred" message.
    On the MBP everything was/is working normally.
    I have tried to copy the same file again, no change. I have deleted the preference file, no change.
    I have tried publishing to a local folder, and get the same error message.
    Does anybody have an idea how to get this fixed? I browsed through the discussions here but couldn't find anything regarding this specific issue.
    cheers
    grani

    Welcome to the Apple Discussions. Try the following:
    1 - delete the iWeb preference file, com.apple.iWeb.plist, that resides in your User/Library/Preferences folder.
    2 - go to your User/Library/Caches/com.apple.iWeb folder and delete the contents.
    3 - reboot.
    4 - launch iWeb and try to publish.
    If that doesn't help continue:
    5 - move the domain file from your User/Library/Application Support/iWeb folder to the Desktop.
    6 - launch iWeb, create a new test site and save.
    7 - go to the your User/Library/Application Support/iWeb folder and delete the new domain file.
    8 - move your original domain file from the Desktop to the iWeb folder.
    9 - launch iWeb and try again.
    OT

  • I keep getting the following error message while sharing my iMovie to iDVD.  "Unable to prepare project for publishing"  error (-2125).

    I keep getting the following error message while sharing my iMovie to iDVD.  "Unable to prepare project for publishing"  error (-2125).  I'm running iMovie 09 v. 8.0.6 on a iMac with OSX v 10.6.8, 2Ghz core duo, 1GB 667 Mhz DDR2 SDRAM.  Any ideas why?

    That particular error comes up for a number of reasons, sometimes it's the size of the movie you're trying to export. Bengt Wärleby a longtime contributor to the iMovie Discussion Group has advised a number of people on this error code, so I am going to link to his latest advice he's given to anyone trying to export to DVD from iMovie: Bengt's tips for great DVDs.
    Specifically, try bypassing Share to iDVD by using Share to Media Browser instead.
    In the Share to Media Browser dialog box choose the Large Size.
    When(If?) it gets through that process, quit iMovie altogehter then go to iDVD.
    Create a new project and click on the Media button near the lower right hand side of the Project Window.
    Then click the Movies button in the Browser window just above that.
    Under the iMovie star icon you should see the name of the project you shared out from iMovie.
    Drag that into the project and burn the DVD.
    If it's still to large or you get the same -2125 error code trying to Share using the Medium size instead. But again if you really get stuck consult Bengt Warleby's User tips:
    Bengt's tips for great DVDs

  • I tried to implement photo albums using iweb and got a publishing error.

    I tried to implement photo albums using iweb and got a publishing error. All was fine with my site until I added the photo album page. The software doesnt say what the error is exactly, only that it is a publishing error to my ftp
    Exact message "There was an error communicating with the FTP server. Try again later, or check with your service provider."
    If I reduce the albums inside to 1 then it seems to work but that takes away from the usefullness of multiple albums.
    my iWeb version is 3.0.4 (601)

    Publish your site to a folder on your hard drive to see if the publication will proceed successfully and open the site locally with your browser to confirm all of the alums are there and work.  If they do try the following:
    delete the iWeb preference files, com.apple.iWeb.plist and com.apple.iWeb.plist.lockfile, that resides in your Home() /Library/Preferences folder.
    go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
    Click to view full size
    launch iWeb and try again.
    If you're still not able to publish from iWeb to your server download and use the free  Cyberduck to upload your website files to the server. Users have found that CD has been successful when iWeb had problems.
    OT

  • PUBLISH ERROR in iWeb

    Hello. I just started using iWeb '08 2.0.2 a couple of weeks ago, and all was going well until...
    Now whenever I publish, I get an error message "Publish Error, an error occurred while publishing file ... Try publishing again later."
    Here's what I've done, based on advice in this message board:
    1) Tried again later. Error still happens.
    2) Publish All to .Mac. It took a long time, but still the same result in the end.
    3) Publish to a folder. I tried the entire site in the local folder, and it works fine. Then I manually copied the folders to the iDisk folder. (That copy was painfully slow, several hours!)
    Once copied to the iDisk, the website does not work properly. Specifically, the photo albums no longer appear on the photo pages. Viewing the page source of the photo pages when browsing on line, I see that all the java code is missing, whereas it is still there when I browse the version on my local disk from the "Folder" publish.
    Anyway, the website is now a bit crippled, and I can't really invest more time in it since the program is so buggy. Can anyone help?
    Many thanks.

    I've discovered something weird that I wonder if it has anything to do with not being able to publish. Since I upgraded to iLife 08 when I click "visit site" I get a web page that says the site doesn't exist. Yet when I go to my bookmark that I have for my site it shows up. The addresses are different. The address that iWeb is trying to go to is http://web.mac.com/username/site/page.html. My actual site address is: http://web.mac.com/username/iWeb/site/page.html.
    Is iWeb somehow confused? I did at one time copy off iWeb and delete the site of my iDisk and tried to publish all, but that didn't work, so I copied the site back to my iDisk.

  • TS2167 iWeb: publish by ftp to GoDaddy webhosting service - get "publish error" at end of ftp session - always 1-2 files not successfully transferred - Why?

    Why do I get message "Publish error There was an error communicating with the server.  Try again later, or check with your service provider" when i publish websites to webhosting service (GoDaddy.com) from iWeb 3.0.4  even though most webpages have been transferred and are marked blue?   There are always a few pages marked red after each ftp transfer?   It seems that the ftp session is terminated by web hosting service too fast for iWeb 3.0.4. to register that files have been transferred successfully.  When I check pages marked red in iWeb with browser, they are often available and functioning.     I have to add many extra webpages (which I do not want) to get iWeb to register all my pages as transferred (marked blue).  If I do not do this, all pages on website are marked "red" after I close iWeb and restart it.   This means that everytime i make one little change to one page on a website of 8-10 Gigabytes,  I often have to republish the entire site!  
    I think (without understanding enough/anything about ftp protocolls and termination negotiations) that iWeb is not getting enough time at end of each ftp session to register that all the pages have in fact been transferred successfully.   Could this be the explanation?  If so, how do I "slow down" the termination of ftp session by my web hosting service GoDaddy so that iWeb 3.0.4 can see that all files have been successfully transferred and therefore should be marked blue?

    You're rather prone to problems, aren't you. It's not the first time.
    2 months ago :
    https://discussions.apple.com/thread/3822198
    5 month ago :
    https://discussions.apple.com/thread/3664339
    Which is the culprit site :
         http://www.melissaveres.com
         http://www.mveres-engraver.com
    And since you do not use iWeb's ftp, but publish to a folder, iWeb's job is done.
    You are now 100 percent responsible for your actions.
    Upload the files properly. And if you're not blind visually challenged, you can see for yourself where the files are on the server. No need for GoDaddy eyes.
    And why not use iWeb's FTP. Then at least you eliminate the human error.
    And no, GoDaddy won't have to help you with iWeb, because there's nothing to fix.
    And practice FTP first on your computer :
    http://www.wyodor.net/Tutorials/iWebDemo/sFTP.html
    Good luck.

  • Constantly getting publishing errors in iWeb

    Has any one else experienced publishing errors when trying to publish to your ,mac account?

    Four things could be going on, but it's fixable.
    first.. make sure that your screen saver, and energy saver are turned off in your system preferences. iWeb had trouble with this in it's first version, but since the update it's supposed to be fixed, but I'd still do it.
    second, it's been my experience that iweb is affected by bandwidth issues while uploading. If you're using your browser, uploading or downloading anything else... you'll get the error message and that one file couldn't upload. Make sure that when you click on the publish button you walk away from the computer and don't use it. This appears to be a bigger problem for us G4 users than the G5 folks. Also, it's a memory hog, so seriously, when you publish turn everything else off except your computer and iWeb and walk away. Seems to work for me.
    Third... make sure your idisk is NOT loaded onto your desktop. If it starts refreshing and files are getting put there while you're uploading, iWeb will give you the dreaded error message.
    Finally, just keep republishing. iWeb seems to bog down when you publish sometimes. I re-uploaded my entire website last night, including 7 video podcasts and numerous other blogs that have audio and video in them. I had to publish and publish and publish.... it took four tries, but it finally finished. It seems that it gets farther and farther along each time. Anyway... it works.
    Hope this helps.
    Jim

  • Doesnt seem to connect when published in a browser

    Hey friends.. im a total newbie to Flash Media server.. i
    just started using this for the past 2 days..so, heres the problem
    im facing..i ve a simpleConnect component and a connectionlight
    component on my stage and i connect both of em..the connectionlight
    goes green when i test movie in flash(ie Ctrl+Enter).. but when i
    Publish(F12) it in a browser.. the light is red.. why isnt it
    connecting to the server when ublished in a browser?i hope u
    understand my problem..please Help me out..
    Cheers~~

    When published in a browser you need to adjust your Flash
    Player's security settings and allow outbound connections for files
    being in the directory where your swf file is. Remember: The html
    and the swf are served from the local file system (C:\path\to\swf)
    and the swf then tries to connect to your fms machine:
    (rtmp://yourserver/app). You should actually have seen an error
    message when you first tried.
    Alternatively you could put your SWF onto a web server (like
    your users would)

  • Publisher: Changing transfer/browser path? [Kaboom]

    Hello -
    We've been having a bit of a time with changing Publisher's transfer and browser path(s).
    * ALUI 6.0
    * Publisher 6.2
    - one master publishing node
    - 3 "read only" published content nodes
    * All content written to a Windows share
    * Publisher service(s) all execute as a Windows user with writes to the share
    Works great, but...We need to change path Publisher is referencing to write to / read from.
    EX: today it writes to "SERVER\OldShare\" - we want it to instead map to "SERVER\NewShare\"
    I'm not sure the appropriate way to go about this and the support team seems as stumped as we are.
    Steps we're going through now:
    * Open Publisher Administration portlet
    * Right-click on the top-level "Plumtree" folder so the context menu opens up
    * Choose "Publishing Target..."
    * We're using "Transfer Using: File Path" (Windows share)
    * Transfer path is set to "file://localhost///MyFileServer/publishedcontent/publish"
    * Browser path is set to "http://publisher.mycompany.com:7087/publishedcontent/publish"
    We want to modify this to be...
    * Transfer path is set to "file://localhost///MyFileServer/newpublishedcontent/publish"
    * Browser path is set to "http://publisher.mycompany.com:7087/newpublishedcontent/publish"
    Kaboom.
    Once I update these settings and click "Test Publish Target" I get the following:
    "Site specified by browser path does not match transfer path location."
    I don't get it. Not saying it doesn't make sense, but I certainly don't get why or what to do ;)
    Not even sure where to look on this one in terms of exceptions. I'm not seeing any exceptions in PTSpy (actually, I'm not seeing anything in PTSpy) and the logs only seem to contain basic info and no explicit "this was bad" messages.
    Any ideas on how to pursue this would be most appreciated :)
    Thanks,
    Eric

    Thank you for your reply :) You inspired me to validate everything and kind of revisit this from scratch. Instead of trusting the system I busted out Textpad and scanned ALL of Publisher's appilcation files for instances of my publishing path. That did the trick and I found where the little bugger seems to get some of its less obvious configuration values.
    * First I found...
    \\MyPublisherServer\d$\Program Files\Plumtree\ptcs\6.2\container\conf\jboss.web\localhost\publishedcontent.xml
    This looked promising, but it wasn't, really. This file will be rewritten by the jboss service startup, but it was an indicator of the issue as it contained the pesky (old) physical publishing path I wanted to replace.
    * Finally we hit gold
    \\MyPublisherServer\d$\Program Files\Plumtree\ptcs\6.2\container\deploy\jbossweb-tomcat50.sar\server.xml
    This file contains...
    <Context path="/publishedcontent" appBase=""
    docBase="//MyFileServer/publishedcontent" debug="99" reloadable="true">
    </Context>
    We changed it to something on the order of...
    <Context path="/publishedcontent" appBase=""
    docBase="//MyOtherFileServer/newpublishedcontentpath" debug="99" reloadable="true">
    </Context>
    OK - that actually seemed to help a LOT. Now I can get at the old content and Publisher seemed way, way happier. Cool!
    * Next we hit issues creating folders/portlets in Publisher -
    "Error: Portlet creation failed: Error accessing file in database ("Document not found: id=F046C0A1/D31E34DD.ACT"). "
    This is indicating that Publisher cannot find/access the files or folders from the document repository associated with the (original) Publisher folder structure. To get past this, find your new document repository and copy/restore the files to it from the old document repository.
    EX:
    FROM \\MyOldDRServer\H$\Plumtree\ptdr\documents\PTContent\Active
    TO \\MyNewDRServer\D$\Program Files\Plumtree\ptdr\documents\PTContent\Active
    That should do it :)
    For those needing to change paths, do a disaster recovery exercise or just find a less obtrusive way to move some things around environments (EX: prod->dev refresh) I hope this helps.

  • AS3 Works in Captivate, not Executing in Browser

    I have a swf file with AS3 coding. The file consists of a timeout timer in frame 1, then jumps to frame 10, where upon there is more AS3 sprite/movie clip animation coding that simply move MC onto the stage. 
    This code works fine when ran as a swf OR when tested in the Captivate environment.  
    However,  when published to a browser, the frame 10 code does not execute?
    Summary: The code works fine except in IE 8 browser.
    Any suggestions?
    Thank You
    iaustin

    im not an expert on this, but i have a similar problem.
    i know that there is a problem with the <applet> tag. I think its deprecated.
    Anyway, try using the the program installed with SDK to make the conversion from <applet> to <object>.
    its located in:
    ...\j2sdk1.4.2\bin\HtmlConverter.exe
    let me know how it goes.

  • Publish without showing browser information

    How can I record or publish without the browser information showing on the published version?  I've set my recording area to the application region and also tried with designating a custom area.  I'm using IE as the browser.  The browser and favorites bar doesn't appear in my recordings, but they do when I publish.
    Any help will be most appreciated.

    Screen capture would help here so we could see what you are seeing.
    But my guess is that you are seeing the browser that is actually presenting the Captivate. Same as you would see the browser when visiting any other web page.
    The only way I'm aware of to get rid of that is to press the F11 key to go into full screen mode, or publish the captivate as an EXE.
    Cheers... Rick

  • IMovie - Getting Error Message "Publishing Error -2125"

    I am getting the message "Publishing Error -2125" when I try to share my movie to i DVD in order to burn it to a disk.  I have no idea what this means.  What can I do?  Help!

    That particular error comes up for a number of reasons, sometimes it's the size of the movie you're trying to export. Bengt Wärleby a longtime contributor to the iMovie Discussion Group has advised a number of people on this error code, so I am going to link to his latest advice he's given to anyone trying to export to DVD from iMovie: Bengt's tips for great DVDs.
    Specifically, try bypassing Share to iDVD by using Share to Media Browser instead.
    In the Share to Media Browser dialog box choose the Large Size.
    When(If?) it gets through that process, quit iMovie altogehter then go to iDVD.
    Create a new project and click on the Media button near the lower right hand side of the Project Window.
    Then click the Movies button in the Browser window just above that.
    Under the iMovie star icon you should see the name of the project you shared out from iMovie.
    Drag that into the project and burn the DVD.
    If it's still to large or you get the same -2125 error code trying to Share using the Medium size instead. But again if you really get stuck consult Bengt Warleby's User tips:
    Bengt's tips for great DVDs

  • "Publish Error: Publish failed due to network error. Check your internet co

    I am using the very latest version of iWeb. I have had it for a week.
    First let me tell you the message that I got and then what I was doing prior to getting the message:
    It said: "Publish Error. Publish failed due to a network error. Check your internet connections and try again."
    I did check my internet connections and I called mt cable modem ISP. He put me through some tests and ascertained that the problem was not with the cable connection. I can connect to the web (of course) and I can send and receive email. The fellow at the ISP (Road Runner) told me that the uploading goes just fine but that the confirmation end of it is bad.
    I have made 9 pages for my website. I clicked the button to publish the 10th page and got the message at the top of this post.
    Then I called Apple Care and took advantage of the 90-day help warranty. The gal there had me try to publish to my private folder. That worked! I was able to publish to the folder and that message at the top of this post did not appear. It said that the page was published and did I want to visit it.
    I ended up deleting the page about my friend Lerma, since everything was going fine until I did that page. AS I recall, there was a mixup with the pages and I thought I had fixed it.
    Then I worked a little more on my husband's Memorial Site and tried to publish and got the same bad message as above, meaning that it wasn't just the page about Lerma but any page I might be doing since doing her page.
    NOW THIS IS THE ODD PART:
    I went to the website on Safari browser with the intention of checking out the other earlier pages, only to discover (happily) that my husband's memorial page (the beginning of it) WAS THERE even though I got that message saying that there had been a network error. Lerma's page, however, was NOT there.
    I am between happy knowing that a page can show up on the website even though I get a message saying that it did not, but anxious knowing that if I am getting Publish Error messages, something is screwy with the program.
    I will continue to try to publish to the Internet, but meanwhile I welcome any observations and happy accounts of how they got the same message but everything ended up fine after a while.
    Meanwhile I am going to be working on my pages even though right now I am getting those messages saying that they could not publish due to network error.
    I need a break.
    — Lorna in Southern California

    Hi Lorna!
    Sorry to hear that you're getting the dreaded
    "Publish Error" message from iWeb. Lots of people
    have reported getting this type of error...and I
    don't think it ever really has much to do with the
    network...at least nothing that can be fixed. The
    fact that you have been publishing just fine up until
    now is a good thing. Some people have NEVER been
    able to publish to the web. Hopefully this problem
    will clear itself up. Maybe it's just sunspots or
    something. Probably someone thinks you need a break,
    too.
    Is this the kind of thing that would warrant me going back to the Apple Store to get an exchange???
    — Lorna in Southern California

  • Publish Error whilst publishing to .Mac from iWeb

    Hello.
    I have suddenly started getting an error "Publish Error. An error occured whilst publishing file xxx" whilst trying to publish my website from within iWeb.
    I have the latest version of iWeb (1.1.2). It used to work OK and I have made no recent changes other than to add a new photograph page. I have plenty of free space on .Mac.
    I have tried the following:
    - Publishing to Folder (this works fine)
    - Deleting the offending file. I then get the error on another file.
    - Deleting the domain file and the com.apple.iweb.plist files in ~/Library/Application Support/iWeb and ~/Library/Preferences. I then tried uploading a default site template and got the same error.
    - Following the steps on http://karreth.com/iweb/22070571-B241-4C09-840B-288E0EC491F6.html. Same error.
    - Creating a new user account and publishing a default iWeb template. Same error.
    - Manually deleting all site and rss content from iDisk using Finder, then Publish All to .Mac. Same error.
    So, it seems that the error is not related to my web content, nor is it related to my iWeb configuration files. I can connect to my iDisk using Finder without problems and browse the contents, so it is not an issue with .Mac either.
    How can I fix this? The error message is useless and I can't find any more detail in the console logs.
    Thanks,
    Paul

    Apnewbie's got a bunch of publishing error tips here:
    http://web.mac.com/mark8heaton/iWeb/PublishErrorsHelp/
    You might check and see if there isn't anything you haven't tried yet.

Maybe you are looking for