Cp 5 crashes during publishing of large projects

I have large Captivate 5 projects with 300-450 slides divided into 2 to 4 slide groups.  When I publish the SWF file, the publishing process always freezes at 70% and the application crashes (can't hit Cancel in the progress window ). 
This is not due to any particular file; many of my large projects run into this problem.
This is probably not due to a particular slide since all the projects freeze at 70% and I can publish each slide group in its own project without any trouble.
The projects are straightforward demonstrations; no quizzing.
Scouring the net I've had trouble finding a resolution to the problem. I use Captivate 5.0.3.631
Hoping for ideas. Thanks for reading
-Patrick
PS.
I've tried:
> In publish dialog "Advanced Options", to enable "force re-publish all the slides"
> In Preferences > "SWF Size and Quality", to disable "Advanced Project Compression"
> In Preferences > "SWF Size and Quality", to disable "Compress SWF File"
> In Preferences > "SWF Size and Quality", to enable "Compress Full Motion Recording SWF file"
> to remove the slide groups and leave the slides ungrouped
> In Publish dialog, to publish as .f4v instead of swf
> to hide all the slides in a slide group in order to reduce the publish SWF to 200 or 250 slides.
None of these have worked.

Vikranth --
Through process of elimination, I have found the offending slide -- Slide 55 in the Captivate 5 version, which incorporates several fill-in-the-blank questions.  When I hide that one slide, everything previews and/or publishes as it should.  I had my colleague test her original Captivate 4 version in Captivate 4, and that slide worked just fine (it is however a slightly later slide number) -- the entire project previewed as expected.  I then had her import her orginal file into Captivate 5 and do the same thing, and it crashed for her as well.
So, it must be something about the way that particular slide is setup that screws up somehow in the conversion from a Captivate 4 file to a Captivate 5 file.  I'll just handle that question differently to fix the issue at hand, but do you have any idea why this problem might have occured in the first place?  It seems that the patch didn't correct this situation as it corrected most of the other Captivate 4 to Captivate 5 issues.
Thanks to everyone for their help.  I had to play detective and isolate the issue, and haven't solved it, but at least now I have a starting point to try and do the slide in a different way to work around the issue.

Similar Messages

  • Freezes on publish - too large project

    (sorry for my English)
    Flash Catalyst cs5.5 is freezing when iam trying to publish or run the project.
    Sometimes there is a message:
    "Flash catalyst cannot publish this project because it is too large. Try removing one or more media assets from your project and try again"
    When it is not fully animated it works with no problem but when everything is animated-all links it frreezes on "Run the project" or "cant publish.." on Publish.
    With 7 main menu links animated and 13 submenu (component) not animated it works
    With 7 main menu links animated and 13 submenu (component) animated it freez, program not responding.
    Iam on Mac OSX 10.6.8 but the same happens on Windows 7 64bit.
    iMac: i7 2.93, 10gb ddr3.
    Please help me with this.

    It does work
    See: http://bit.ly/bXR9z6
    Daniel C. Slagle
    Keeper of the "Unofficial" iMovie FAQ
    I may receive some form of compensation, financial or otherwise, from my recommendation or link

  • Captivate 5 Crashes During Publishing of Cap.4 file

    Hi All --
    So I'm trying to help a fellow co-worker out.  She needed me to clean up a Captivate 4 project for her in terms of quizzing and formatting, only I have Captivate 5, which of course makes this much easier, but I've tried publishing to .zip and .html about a dozen times and the publish crashes the entire Adobe Captivate 5 program, without fail, right around 31%.
    I've made sure that the 5.1 patch is applied (which was supposed to fix publishing issues from Cap. 4), I've dumped the preferences folder (I'm a pro at this by now), and I've tried on both a Macintosh OS X 10.6 system and a Windows 7 System, and it does the same thing, so I don't know what is wrong.  The project is a bit long at 168 slides, but there's no audio, and it's really a pretty basic project with the biggest interactivity being quizzes and rollover captions, so nothing as fancy as I usually do with advanced actions.
    I realize this might have something to do with a particular slide or something, so this file can be temporarily accessed off of my iDisk using this link (https://files.me.com/dancomins/p7njsq), it's about 4 MB, if that might help address the issue.
    I am a total loss -- I've had issues with Captivate before of course, but never at the publishing step -- so any help or suggestions would be most appreciated.
    Thanks so much!
    Dan

    Vikranth --
    Through process of elimination, I have found the offending slide -- Slide 55 in the Captivate 5 version, which incorporates several fill-in-the-blank questions.  When I hide that one slide, everything previews and/or publishes as it should.  I had my colleague test her original Captivate 4 version in Captivate 4, and that slide worked just fine (it is however a slightly later slide number) -- the entire project previewed as expected.  I then had her import her orginal file into Captivate 5 and do the same thing, and it crashed for her as well.
    So, it must be something about the way that particular slide is setup that screws up somehow in the conversion from a Captivate 4 file to a Captivate 5 file.  I'll just handle that question differently to fix the issue at hand, but do you have any idea why this problem might have occured in the first place?  It seems that the patch didn't correct this situation as it corrected most of the other Captivate 4 to Captivate 5 issues.
    Thanks to everyone for their help.  I had to play detective and isolate the issue, and haven't solved it, but at least now I have a starting point to try and do the slide in a different way to work around the issue.

  • Crashing during publishing

    All of a sudden, iWeb 08 is crashing in the middle of the task when I try to publish to a folder. I'm using Mountain Lion and haven't had a problem until today. Anyone know of a fix?

    iWeb '08 is known to be unstable when used with Mountain Lion. The problem appears to be with some incompatible files in the OS and it looks like you would need to either update to iWeb V 3.0.4 or run iWeb under Snow Leopard on a separate, bootable hard drive.
    The latter method makes more sense as it is hardly worth buying the iLife disk to update software that is now redundant. If you do want to consider this option you would need to purchase the iLife '09 or '11 disk from somewhere like Amazon.

  • Large captivate file crashes during preview

    Hi,
    I have a very large training -- 600 or so slides -- that I created in Captivate 6.  It is mostly made up of Power Point slides and demo videos. When I preview it using f8, it crashes at several points in the training, and always at the same spots.  When I preview using F10, it doesn't have this problem.  Luckily, the published version doesnt seem to crash, but I would like to preview the project with having to publish it.
    Let me know if you can help..
    Thank you!
    Ryan

    Ok.. Thank you!
    Re: Large captivate file crashes during preview
    created by RodWard<http://forums.adobe.com/people/RodWard> in Adobe Captivate - View the full discussion<http://forums.adobe.com/message/4812539#4812539

  • GB crashing during large file export

    GB 09 is crashing during an export of a project that is 2 hours and 20 min. I've tried diff export settings but the program still quits when it reaches about 3/4 of the project length.
    No crashes in the past. Been exporting the project to rough cuts at various lengths from1 hour to 1 1/2, but upon finalizing the project, which happen to total over 2 hours, it can't make it through an export.
    It's an audio book - talking only -no effects, other instruments, very straight forward.
    I've tried exporting from the master .book file and a version with all the clips joined, tracks locked, and extra stuff deleted for project.
    Here is some of the crash report (just pasting the first page of the crash report).
    Process: GarageBand [2716]
    Path: /Applications/GarageBand.app/Contents/MacOS/GarageBand
    Identifier: com.apple.garageband
    Version: 5.1 (398)
    Build Info: GarageBand_App-3980000~2
    Code Type: X86 (Native)
    Parent Process: launchd [138]
    Date/Time: 2010-03-29 11:14:16.969 -0400
    OS Version: Mac OS X 10.6.2 (10C540)
    Report Version: 6
    Interval Since Last Report: 1758706 sec
    Crashes Since Last Report: 39
    Per-App Interval Since Last Report: 219501 sec
    Per-App Crashes Since Last Report: 6
    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    Thread 0 Crashed: Dispatch queue: com.apple.main-thread
    0 com.apple.CoreFoundation 0x94dd0554 CFRelease + 196
    1 com.apple.AppKit 0x9468967a -[NSBitmapImageRep initWithFocusedViewRect:] + 2257
    2 com.apple.garageband 0x001f5fea 0x1000 + 2052074
    3 com.apple.garageband 0x00205650 0x1000 + 2115152
    4 com.apple.garageband 0x0014f7c2 0x1000 + 1370050
    5 com.apple.garageband 0x0015a58a 0x1000 + 1414538
    6 com.apple.AppKit 0x945edb6c -[NSView _drawRect:clip:] + 3721
    7 com.apple.AppKit 0x945eb238 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 2217
    8 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    9 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    10 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    11 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    12 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    13 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    14 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    15 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    16 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    17 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    18 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    19 com.apple.AppKit 0x945ebbcb -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4668
    20 com.apple.AppKit 0x94689b5f -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 311
    21 com.apple.AppKit 0x945e7111 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 3309
    22 com.apple.AppKit 0x94547d6e -[NSView displayIfNeeded] + 818
    23 com.apple.AppKit 0x944fb9c5 -[NSNextStepFrame displayIfNeeded] + 98
    24 com.apple.AppKit 0x94511094 -[NSWindow displayIfNeeded] + 204
    25 com.apple.AppKit 0x945425aa _handleWindowNeedsDisplay + 696
    26 com.apple.CoreFoundation 0x94e43892 __CFRunLoopDoObservers + 1186
    27 com.apple.CoreFoundation 0x94e0018d __CFRunLoopRun + 557
    28 com.apple.CoreFoundation 0x94dff864 CFRunLoopRunSpecific + 452
    29 com.apple.CoreFoundation 0x94dff691 CFRunLoopRunInMode + 97

    Sorry about listing too much data from the GB crash report.
    Anyone have trouble shooing tips for crashing during large mix downs/exports?
    The file that crashes during export is over 2 hours long, but only 1 voice track with no effects!

  • Project crashing during rendering

    Hi all again,
    Ive a new problem that may be a simple Premier Pro CS3 software reinstall but first I thought to seek further advice.
    During the rendering processes (to Encore) Im frequently having system errors with PP needing to shut down.
    The error message is;
    C\DOCUME''1\user\locals'1\temp\143d-appcompat.txt
    Any advice as to what this might b pointing to or other sugestions to get remdering process running better.
    With persistance the projects will render and export to Encore but i may take any attempts
    The Computer Specs;
    Intel (R) Core (TM)
    E6750 @ 2.66GHz
    2.67GHz, 1.97 GB of Ram
    Windows XP Professional version 2002
    Cheers

    In some instances you will experience crashes during renders if the automatic screensaver kicks in during the process.  Goto your desktop and ramp the screensaver up as high as it goes.  You may find this fixes that nasty problem.

  • Muse Crash - after pages "optimizing assets" and "exported" During Publish

    The following was causing me problems for about a week or so. I continued to pursue it with the following "Crash" symptoms until waking this morning with perhaps a resolution to the inconsistent problem. It is so simple I would probably be wise just to ignor giving you an answer to save face. But, sometimes you just must standup and take it ... so don't be too hard on me.
    ANSWER TO MY CRASH PROBLEM: When publishing you have in the option menu to either upload all changes or just upload those things that have changed from the last update. With over 2,000 images on my site and 18 pages I decided, until I had a major upgrade, to take the option to upload only changed items of my site. This saves a lot of time. In thinking about it it came to me "who is then deciding what is "change" and what conditions apply and are covered by the logic of the Muse program". What is considered an error to crash the program! So I chose the option to upload all items and this seemed to fix the problem. I think it has as it crashed right after it had uploaded the "changed" items but, never published them (because of an error somewhere in the uploads). My suggestion to the program writers is whatever sensed the error should have a dialogue box that says to rerun the program using "upload all items". Love this program! Howard Lower of Lower Photography and Studio in Rochester, MN.
    Muse Crash right after pages are exported during publish with no other indication of a problem. I have been fighting this problem for many days now.
    I thought I had it fixed last night as it worked fine after deleting the Microsoft Outlook plugin called Acrobat PDFmaker Office com Addin as the descriptions of the problems it caused others with Adobe programs sounded exactly what I was see with Muse.
    The only Change I see in Muse today is that during "Publish", and the information as it runs is Muse first "optimizing assets", them it Export Desktop page and gets to 16 of 18 then Muse crashes without any indication or message for the problem.
    Could it be a problem with "Business Catalyst" as that is what "Publish" is exporting to? Who can check out to see what is happening from exporting assets to Business Catalyst? It appears that the one line in the specification box does not have to have any information put into it regarding the directory location as it already has the business Catalyst name or reference site in it. Is this correct?
    That is all I need and the only thing I can say is  .... HELP! Muse is the perfect program for me and my business and now it has let me down so that I can not make changes to what I would consider a great website at http://www.lowerphotography.com if I could only make needed changes.
    Message was edited by: HLower
    Message was edited by: HLower

    Well, after 20 hours of work and rebuilding most of my Muse website I finally was able to upload by site again.
    Here was my problems per above and the last 20 hours. When publishing the site it does the following: Optimize assets, exportin desktip page 1 thru 19, Fining export HTML files then uploading images which I have 2208 on this site plus other stuff uploaded.
    I can not answer why it now works as "normally"it would het error #2015 uring optimizing assets wich is an invalid bitmap data error and failed at only 9% publish process then got a 1125 index 0 is out of range0 at publish 20% complete.
    I did rewrite most of the pages and made minor changes to all of them thinking that would force all pages to be uploaded as I also took option to upload all pages instead of just those that changes. All 2008 images were reloaded onto the pages by another hint I read on how to delete all thumbnails and thus the files is to select all and press delete and it will leave one as required. Then the one left could be deleted by itself. Thanks for whoever asked the question and who answered it. This saved me a lot of time.
    Thanks to all that have taken the time to help me out. Muse is a great program but sometimes you don't have any idea if it is working at something so I found myself looking at the computer busy light to see if Muse was taking a lot of cycles. It would help to have a wider use of the cursor busy indicator as sometimes the system seemed like it was hung up but it was not.
    Thanks guys!
    Again, after hours of calmness and yes I also prayed over this problem and this last time it worked. So stay calm, and keep working at it and God helping doesn't hurt either. I can not explain it otherwise.

  • IWeb application keeps crashing during my Mobileme publish....PLEASE HELP!!

    Hey everyone,
    I am in some serious need of some help. If anyone can help it would be greatly appreciated. I have been using iWeb for about 5 months now and have never had any problems uploading to Mobileme. Just recently, after creating an elaborate website for my Miami HEAT clientele, iWeb has been crashing during my publish to Mobileme through the iWeb application. Through reading some different discussions, I have figured out that my domain file under the Application Support folder is corrupted. I know this because when I drag that domain (with all my website content) to the desktop and re-start iWeb, a new domain is created and successfully publishes. I am now in need of figuring out how to copy all my website content from my old corrupted domain to this new freshly made one....the bottom line; I would like to avoid having to re-create my entire website from scratch on this new domain...Roddy mentioned being able to copy and paste, but after exploring some I have not been able to figure out how to do this.
    I also tried to upload to a folder and then dragging all the files to Cyberduck, but it takes ALL DAY to do and never completes uploading...
    I don't want to pay $50 for the 30 day Applecare for phone tech support to only hear that I will inevitably have to re-create my entire site...
    Can anyone help? I have clientele that have been hassling me to get their pictures online...please help.

    The posters here are right. Cutting and pasting may take a bit of time if you have a lot of pages (as I did a year ago) but it's better than rewriting code or retyping pages. As of '08 Apple didn't have any server backup capability of published iweb sites, so it is up to the user to do it.
    I have four sequential backups of my Domain file. I backup to 2 locations each day, that way if a batch goes bad, I only lose a day's work at most; in addition, the chances of 2 backups and the original going bad at one time are remote.
    Just last week my Domain file became corrupted. Just wouldn't publish and received an error message. In 10 seconds I clicked on a recent backup and it worked fine. Go figure?! So I dragged the main bad Domain file to the trash, dragged the working copy from the external hard drive to the Library, and voila...back in business.
    The message is backup, backup, backup, especially when your business web site is at stake.

  • I am trying to render a movie in ilife 11. Error appears: Unable to prepare project for publishing. The project could not be prepared for publishing because an error occured. (project is too large). It is only 1:39:00. Any ideas? Thanks! Marv

    this error occurs. Unable to prepare project for publishing. The project could not be prepared for publishing because an error occured. (Project is too Long)
    I know this isn't true, as it is only 1:39:31. I have a mac with 160mb and 160 gb available. Could this be the problem? If so how can I remove some things to make room? Thanks!!

    By exporting to the right format a movie of an hour and forty minutes could potentially use up 160 GB, exactly what format are you exporting to. additionally I'm not clear what you mean when you say your mac has 160 MB and 160 GB available.

  • RH8 HTML:  Publishing Sections of Project (Not Entire Project)

    Hi,
    I have a fairly large project that I'm doing various updates to.  Is there a way to publish just the areas that have been updated instead of the whole entire project?  Currently, I select "generate primary layout" once I commit through SVN but this publishes the entire project.  I just want to publish certain sections as they're being updated.
    Thanks!

    Hi there
    You can accomplish what you want in many ways. I cannot help but to notice you used the word "Publish". Are you using the built in Publishing feature to do this? If so, note that typically this operation only copies over the files that have been added or changed since the last time you published.
    From what you stated, one may also infer that you wish to prepare certain content but prevent it from going out as you update. If that's what you are hoping to do, you would use Conditional Build Tags to accomplish that. Just create a tag and name it perhaps IP (for In Progress) and exclude anything tagged with IP during the generation of the output. Assuming everything has been correctly tagged and is working, nothinig tagged with IP should end up among the output files.
    Hopefully this was helpful... Rick
    Helpful and Handy Links
    Captivate Wish Form/Bug Reporting Form
    Adobe Certified Captivate Training
    SorcerStone Blog
    Captivate eBooks

  • IMovie is crashing after creating the large movie for YouTube.

    Hey Guys!
    So, I have been uploading to YouTube from iMovie for several years now and today I uploaded again as I usually do. The problem was that about 30 seconds before the end of my video it went black on YouTube! I deleted it off YouTube and reuploaded but it happened again! So, thinking that it was something on YouTube's end I deleted it but the next time I tried to upload, iMovie gave me this error message: "The project could not be prepared for publishing because an error occurred. (Not enough room in heap zone / )"
    Now when I try to upload, iMovie crashes after creating the large movie to upload to YouTube!
    I have restarted my computer, deleted items to create extra space on my disk, and ejected my iPhone so nothing else happens while I'm trying to create the large movie.
    Does anyone have an idea of what is happening and how to fix it?
    Thank you!

    I'm having a similar problem with Imovie 11.  I wonder if the problem is in the new Mountain Lion update.  Fortunatly, I cloned the drive befor installing the update.  I've cloned this drive back to the original startup drive and gotten back to IMovie.

  • GoPro Cineform files cause Premiere to crash during Media Export

    I first  noticed this problem when using a project that had been copied and transcoded with GoPro codec as demonstrated in Dave Henly's helpful video.  The codec is indeed beautiful.
    However, 50% to 80% of the time when trying to export a project where there are GoPro files on the timeline, it'll get about halfway through the export before Premiere (or Media Encoder) simply freezes up. 
    I didn't know what was causing this problem until I was  using one large GoPro-exported video as the new base layer for a project that had otherwise been working perfectly prior to that (using Canon 60D-created .mov files).  Now it was crashing during every export.  On a hunch, I re-exported that base layer as an h264 file and replaced the GoPro video on the timeline, and now the project exports out just fine. 
    Is this happening to anyone else?  I'm using just the standard 8bit GoPro preset whenever I export out or transcode clips. 
    I'm using Premiere Pro CC, whatever the up-to-date version number is right now.
    Windows 8.
    24 gb RAM.
    GeForce Titan Black
    Intel Core i7

    Similar problem.
    The new feature rendering a ae comp inside premiere timeline is perfect, but using gopro cineform codec crashes premiere on export.

  • Unknown errors encountered during publish(EJB)

    Hi,
    I am getting following error while deploying simple stateless EJB.
    Can anybody help. Please mail me.
    I am pasting the error both from JDeveloper and from command prompt deployment.
    ==========================================
    ***From JDeveloper 3.2.2 It says***
    *** Executing deployment profile E:\jdevloper\myprojects\Hello.prf ***
    *** Generating archive file E:\jdevloper\myprojects\HelloSource.jar ***
    Compiling the project...done
    Validating the profile...done
    Initializing deployment...done
    Scanning project files...done
    Generating classpath dependencies...done
    Generating archive entries table...done
    *** Archive generation completed ***
    *** Deploying the EJB to 8i JVM ***
    EJB deployment argument list:
    "E:\jdevloper\java1.2\jre\bin\javaw" "-DPATH="standard jdev path"
    -classpath "standard path of Jdev" oracle.aurora.ejb.deployment.GenerateEjb
    -u system -p manager -s sess_iiop://10.5.0.55:2481:ORCL -republish -keep -temp TEMP
    -descriptor "E:\jdevloper\myprojects\Hello.xml" -oracledescriptor E:\jdevloper\myprojects\Hello_oracle.xml
    -generated "E:\jdevloper\myprojects\HelloGenerated.jar" "E:\jdevloper\myprojects\HelloSource.jar"
    Reading Deployment Descriptor...done
    Verifying Deployment Descriptor...done
    Gathering users...done
    Generating Comm Stubs.......................................done
    Compiling Stubs...done
    Generating Jar File...done
    Loading EJB Jar file and Comm Stubs Jar file...done
    Generating EJBHome and EJBObject on the server...done
    Publishing EJBHome...
    Unknown errors encountered during publish. Please check the server trace file
    *** Errors occurred while deploying the EJB to 8i JVM ***
    *** Deployment completed ***
    ==========================================
    ***Error occured while trying to deploy from command line.***
    E:\jdevloper\myprojects>D:\oas9i\bin\deployejb.bat -u system -p manager -s sess_iiop://10.5.0.55:2481:orcl -republish -keep -temp temp -descriptor Hello.xml -oracledescriptor Hello_oracle.xml HelloSource.jar
    Reading Deployment Descriptor...done
    Verifying Deployment Descriptor...done
    Gathering users...done
    Generating Comm Stubs.......................................done
    Compiling Stubs...done
    Generating Jar File...done
    Loading EJB Jar file and Comm Stubs Jar file...Exception in thread "main" org.omg.CORBA.COMM_FAILURE: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read minor code: 0 completed: No
    at com.visigenic.vbroker.orb.TcpConnection.read(TcpConnection.java:61)
    at com.visigenic.vbroker.orb.GiopConnectionImpl.receive_message(GiopConnectionImpl.java:436)
    at com.visigenic.vbroker.orb.GiopConnectionImpl.receive_reply(GiopConnectionImpl.java:347)
    at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:562)
    at com.visigenic.vbroker.orb.GiopStubDelegate.invoke(GiopStubDelegate.java:503)
    at com.inprise.vbroker.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:60)
    at oracle.aurora.AuroraServices._st_JISLoadJava.add(_st_JISLoadJava.java:66)
    at oracle.aurora.server.tools.sess_iiop.Loadjava.add(Loadjava.java:137)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.loadAndCreate(Loadjar.java:101)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.invoke(Loadjar.java:80)
    at oracle.aurora.server.tools.sess_iiop.Loadjava.<init>(Loadjava.java:94)
    at oracle.aurora.server.tools.sess_iiop.Loadjar.<init>(Loadjar.java:52)
    at oracle.aurora.ejb.deployment.GenerateEjb.invoke(GenerateEjb.java:560)
    at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke(ToolImpl.java:143)
    at oracle.aurora.ejb.deployment.GenerateEjb.main(GenerateEjb.java:575)
    =============================================
    I have checked log also. This is the log from oracle trace file.
    Session 13 exceeded soft sessionspace limit of 0x100000 bytes.
    *** SESSION ID:(8.3994) 2001-06-23 17:44:30.625
    jox_call_java_pres_: caught
    ORA-04031: unable to allocate 4032 bytes of shared memory ("large pool","unknown object","joxu heap init","ioc_allocate_pal")
    Please help me out of this si tuation.
    regards,
    vijay

    You can try to set the java_pool_size and shared_pool_size to larger. This parameter is in the file: init.ora . The size should be large enough. Usually at least 50M.

  • In iMovie I am getting this message...Unable to prepare project for publishing. The project could not be prepared for publishing because an error occurred.m file already open with write permission.

    In iMovie I am getting this message...Unable to prepare project for publishing.  The project could not be prepared for publishing because an error occurred. File already open with write permission. 
    How do I resolve this?

    Hi
    Most often it helps by - Turning Off the TimeMachine application - during work in iMovie.
    Yours Bengt W

Maybe you are looking for