Captivate 4, LMS, close project

Hello,
I am using Captivate 4 and Pathlore LMS. I have attached a Captivate quiz content object to the LMS as both an .swf and .exe. The .exe does not even launch (as I learned from searching that this is the normal behavior between LMS and .exe) and the .swf does not close.
I have attempted to use the "Close project" action and the error message, "Internet Explorer cannot download. Unspecified error." is launched. I have also tried to execute various JavaScript to close the window, to no avail.
I have searched the forum and the internet and cannot seem to find a solution to this.
Help please?
Thanks,
John.

Hi there
I'm surprised you missed seeing the sticky links on the Captivate forums landing page.
Click the image below for a possibly larger view.
Your answer would seem to be listed in the Frequently Encountered Issues link.
Click here to view
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

Similar Messages

Captivate CS4 - As3: Close Project problem

I've just built a project with some As3 animations. Hence I saved the project as an As3 project. The problem is that at the end of the last slide, the project freezes rather than shuts down. I have taken care to select the "Close Project " option rather than the Stop option. But the project does not close automatically. Also the Exit button does not work (as intended).
More details:
Captivate CS4
IE7 browser
I've looked at some previous queries too on this forum but none seem to have an answer to the problem.

Withdraw the question.
It seems to run fine on my LMS but the issue is with IE, I guess.

'Close Project' in Captivate 4 not working

Hi,
I have a number of projects where I set the preferences to close the project, and it works in some and not others.
I have a slide with a 'Done' button. When the user clicks it, it goes to another slide with nothing on it but the background and a text caption from the previous screen, and it is set for only one second. Some of these projects close perfectly; others delete the text caption and leave the project open.
Any ideas?
Thanks, as always.

Hmmm, it was intended to show you that you simply cannot rely on the different means of closing the window. Close Project and the Exit button are essentially the same action, no? Perhaps I should amend the note so it specifically also mentions the action of Close Project.
The thing is, unless you are presenting your Captivat using EXE format, you are seeing a very generic overall issue with closing a browser window. And closing browser windows is inherently fraught with issues and seldom works as one would expect. The only way to make it work as you want most of the time is to ensure you always open the window using JavaScript so it's a child window. When you open in this manner you have more control over the behavior of the child window and can usually close it at will.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

CP5: Close Project causing problems

I have two problems, which I think may be related.
In order to give users control over closing a project, I have a 'Finish' button on the second-to-last slide, which goes to the last slide, which is only 1/2 second long, and should then close, since the "end" preferences are set for Close Project. I did it this way because there is no action for "Close Project."
1. This worked fine in Captivate 4, but in CP5 the projects are not closing, and the X button on the Navigation bar doesn't work. The only way to close it is to close the window.
2. The LMS's don't recognize the project as complete.
Is this a bug, something I'm missing, or is it to do with SCOs vs. Courses?

Hi,
Just following up on Rod's post...
The problem I'm having with the LMSs doesn't happen with the projects created in Captivate 4 - they close correctly, and register in the LMSs as completed.
One LMS is a variation on Moodle; the other is one that is used primarily in law firms. Both (I think) run the content in a separate window - I know one does.
As I've said in my responses to Rick, I've run them from a web server as tests - mine don't close, and both his test projects did.
Any more suggestions? This is really serious for us.

Close project

We are working on a project and are relatively new to
Captivate. The last slide is set "Fade last slide" and "close
project". It doesn't close it. What do we do?
Mary

Hi Mary,
Do you have a button or click box that is preventing the last
slide from playing to the end of the project?
Also, when you say "close project", are you referring to the
Project End option in the Project preferences or something else?
If the answer is "something else", try setting the Project
End option in the Project preferences to "Close project" and then
letting the project run to the end on the last slide. This seems to
be the best way to ensure that a project closes.

"Close Project" to be made inactive until a particular phase is reached.

Hi All ,
I am having requirement of making "Close Project" under Document tab in Document toolbaras inactive until the Project reaches the final phase of it.what I thght of it is like locking/inactivating the "Close Project" by scripting when the project is created and write the code to unlock/activating the "Close Project" in the Document Life cycle event context for a post phase change by checking if the current phase is the last phase of the Project.
But I didnt find any methods from RG to make the Close Project inactive... Did any one try this or suggest any methods from RG?.
(I guess in toolbar customizations you can only hide or rename the display names . I was able to only rename/hide the "Close Project"...).
Regards,
Uday

You're right, iCal is well suited for creating calendars for presentation purposes.
You should let Apple know what you think here:
http://www.apple.com/feedback/ical.html
Matt

How can I convert .cp projects from Captivate 2 to .cptx projects for Captivate 7?

How can I convert .cp projects from Captivate 2 to .cptx projects for Captivate 7? Do I have to use some other version between 2 and 7 to do this?

I doubt you are going to be able to find all those previous versions and the time it would take to install, open the project, verify it, and everything in between (and without license keys, they would only be saved from trial versions which would be an issue), it seems it would be better just to start with Cp7 and put the effort into that.
Completely off topic, one of the things I like about Authorware is that Macromedia provided previous versions that would allow you to open up and save the projects to get to version 7. It was a nice little touch they provided for developers. I don't believe that Adobe does this for Captivate though.
Dave

Premiere Pro CS6 6.0.2 hangs on Close Project

I have a project that I was working on today that seems to have somehow become corrupted. Everytime I open it, and then attempt to Close Project, premiere will stop responding.
I've tried creating a new project, and when I import the sequence from the older project file, save, and and attempt to Close Project, premiere stops responding...
A couple of other projects seem fine. So somehow, this project must have become damaged or something.
How can I debug this issue so i can get the sequence back to keep working?
Thanks,
-ken

I was able to find an auto-save version that only lost me some of the work I had done, so thanks for the suggestion.
As I began redoing the lost work, I reproduced the problem. So I spent the last hour narrowing down what is causing it, and have found that an audio track that I am imported will reproduce the issue every time.
I can even start a new project, and import that single audio track, and cause premiere to hang. It's clearly a bug, but I'm not sure how to figure out what's going on.
The track was an MP3, so I brought it into audition and exported it as an AIFF file. But importing that file causes the same issue.
What's the best way to get Adobe to look at this. It's a simple problem to reproduce, and since it causes the app to hang, it probably should be fixed. I also tried to just remove that audio item from the latest project file, but that doesn't help. Once I import the track, any attempts to save the project will result in a hang.
Thanks in advance,
-ken

Hi, OS 10.6.8 (2006 macbook pro) won't save, close projects, quit

Hi, I recently upgraded my OS to 10.6.8 (my 2006 macbook pro - 2.16 intel core 2 duo - won't run anything beyond that), and now Logic will not close projects or save, and it won't quit until forced to!
If anyone has any advice I'd be very grateful.
Thanks

You need this fix!
http://support.apple.com/kb/TS3968
Follow the instructions exactly, there is also a link to get what you need to install.
Don't delete any more than the instructions call for.

Logic crashes when using the "Close Project without Saving" key command

The "Close Project without Saving" key command does not work in LP8. When I try to use it, Logic crashes. This is reproducible on my system. Can anyone try and confirm this?

For me this shortcut is quite important on stage when I have to switch songs as fast as possible. It also is foolproof because on stage I never want to save with all the controller changes I did during a performance.
Just hit the key command, load the next song, done.
Message was edited by: cronbg

Does " Close Project without Saving " key assignment work at all ?

I'm using Logic Express 8. I'd really like to be able to close a project without seeing the " do I want to save the project " box.
There is a function to do that in the Keypress Commands, but it seems broken. I've tried assigning several different keypress combinations to that function and all they do is crash Logic when I try to use them.
So, am I doing something wrong, missing something, or is that command broken ?
???

Come on, how hard would it be for someone out there to try this and let me know if it's my problem .. or a bug ?
Logic Express Preferences ... Key Commands .... Global Commands ... Close Project without Saving.... assign some key combo to that, then go back to a project and try it.
Oh, and then fill out the cute - report this to Apple- thing when it pops up after the crash so someone will fix this and I can move on

Close Project with partially confirmed network

Hello,
Is there a config setting which sometimes allows users to close a project with a network only partially confirmed ?
Seems this is happening occasionally instead of the system enforcing the network be finally confirmed.
Thanks,
Dave

Hi,
His requirement "Is there a config setting which sometimes allows users to close a project with a network only partially confirmed ?"
it seems he want to close project with partialy confirmations. anyway he can use one of those available options.
Thanks.
regards,
Sam L.
Edited by: sam Lesha on Mar 23, 2011 6:14 AM

Close project with not zero WBSs

Hi Gurus,
how can I close project with not zero WBSs? Client has a project wit not zero wbs a very old cost on wbs. Stores = wbs don`t exists no more and they can`t move the cost from wbs.
Could zou help me?
Thanks very much.
BR,
Martin

Hi,
yes I want to give status CLOSE to project and all wbs even though I have balance in it.
I moved cost with Tr. KB15N to cost center and in CJI3 I have zero balance for wbs. But by closing wbs I have error KO115 Balance is not zero.
BR,
Martin

Captivate 4: linked pdf file opens when published but closes project

I have linked a couple of pdf files (Live Cycle) to an Adobe Cap 4 project. When I published the Captivate file the pdf file opens and works well but once the user closes the pdf file to contine to the next slide the project closes. Does anyone know how I can correct this? (it works fine in preview but not when published) Thanks!

Hi there
How exactly are you opening the PDF? If you just linked to it without choosing the "New Window" option it will replace the Captivate project in the browser window.
Perhaps you should examine the configuration of whatever is triggering the opening of the PDF. You should also review the information provided at the link below.
Click here to view
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcererStone Blog
Captivate eBooks

Captivate 5.5 - SCORM Project won't run after Captivate 7 installation

Good afternoon,
I had completed a Captivate 5.5 project for a few months and as of about a month ago I have had Captivate 7 installed on the machine. Due to some widgets that are implemented in the project that only run in 5.5, I have not used Captivate 7.
I also have not had cause to reopen the project until recently to make some changes. However, now when I publish the files, package them in the MultiSCO Packager, and put them in CMS - it won't run.
I've verified that the CMS is not the issue: if I repost the pre-Captivate 7 version it works just fine and the only changes I made to the original files were cosmetic and minor.
Now when I republish the files in 5.5 and package them, the files look different, publishing all of the zips into a "Linear" subfolder. I couldn't help but notice that this is the same as Captivate 7 publishes except without any accompanying XML files. Why would Captivate 5.5 be affected by Captivate 7 being updated on the machine?
Is there any solution to this other than having to open the 5.5 files in 7 and replace every widget? This is a huge expenditure of time when I was under the impression that if 5.5 was still installed it would run completely independent of the Captivate 7 changes.
Any help would be appreciated,
Jaimeson

Don't be too quick to write off the LMS/CMS as the issue. You need to be aware that with Cp6 Adobe totally revamped their SCORM drivers so there is now little similarity between output of 5.5 to 7 in this area. It is also no longer possible to use Cp7 SCORMs in the Cp5.5 era Multi-SCORM Packager tool. They are not compatible. You must make sure the CP7 SCORMs are matched with the Multi-SCORM Packager that came with Cp7.
Once you get compatible SCORMs published, try uploading them to SCORM Cloud LMS to test. If they work fine on SCORM Cloud then they should work on your CMS (if it is truly SCORM compliant).
Your issue with the widgets not working in Cp7 might be resolvable if you update the widgets. Have you checked with the original widget developer to see if they have updates available? If you have several widgets of the same type and version in each project file, then there is a trick to updating all of them in one go (per project file).
See the heading in the lower part of this page:
http://www.infosemantics.com.au/adobe-captivate-widgets/widget-updates
But be warned that this only works if the widget filename is exactly the same, and you are doing this from the same computer that was used to originally insert the same widgets, because the path to the external widget file must be replicated.

Captivate 4, LMS, close project

Similar Messages

Maybe you are looking for