Cs2 files crashing when exporting to inx

hi my name's Suzi and i have two problems with my indesign cs2.
Firstly I ftp'd some files yesterday to an editor with cs1 but she cant open them. I saved them by doing file-export-indesign interchange. i've downloaded all the updates from the website. what can I do?
Also two cs2 indd files wont export to inx - they crash every time. would someone else mind trying them for me? or any ideas what the problem might be? they were fine yesterday.
:0)

suzi,
If the editor on the far end can't open your CS2 .inx files, the problem is most likely that she isn't fully patched to the last 3.0.1 update (there were two with that number which confuses the issue). Keep in mind, too, that you will lose any of the unsupported features you may have used. This is not a good workflow.
File crashes on export sounds like a it might be font related. Any new fonts added to the file? How many pages are there in the document?
Peter

Similar Messages

CS2 InDesign crash when exporting

Hi,
I've got a copy of CS2 InDesign at work that crashes when exporting a certain file to PDF.
The files have limited information on each page except for placed PDF & JPG images. The images themselves seldom get above 300kb each, but there are lots - some times 5 per page in an 80 page document. It's a document to be printed so the images are as small as they can be.
When exporting the document, ID crashes without warning - it just vanishes, no dialog box saying 'This application unexpectedly quit' or anything.
Is this common? I have plenty of memory on the Mac, and no other applications or windows are open at the same time.
Any suggestions as to why this happens?
All text in the PDF images are outlined in Illustrator so presumably it's not a type recognition issue.
Any suggestions welcome.
cheers
G

Hi Bob,
System spec is PowerPC G5, version 10.4.11. I'll have to ask our Mac expert
if CS2 is fully patched.
Cheers for your response.
G

InDesign CS2 file crashing when saving or using save as

(This is on a Windows XP system)
I have a file that ran fine until the last few pages were edited. The file is a mock-up and has very few links and only 3 different fonts. The file opens fine and I can edit everything, and print. The actual program and document seem to work fine. However, when I attempt to save changes or export it crashes In Design and I get the "reference memory cannot be read" message (50%) of the time. Other times no error message is reported. Sometimes the changes have actually been saved and other times they are not. With the "save as function" I get a 50/50 return on a new file. I have tried re-naming the file, opening the file on another computer and the same thing happens. My other ID files are fine. Everything works fine until I try to save the document.
I've tried the fixes for my system like removing unnecessary fonts. I relinked all my links, changed my display resolution to "fast" to no avail. It truly seems to be an issue with the file not the program. Is there any wisdom on this issue? Ideas for how I might salvage or repair a damaged file so it can be saved?
HELP!

Since this is isolated to a single file, try exporting it to Interchange Format (.inx), then open and save the resulting file as a new InDesign file.
Since the problem occurs during export, that may not be possible. Another option to try would be to copy all elements, page by page, and "paste in place" into a new document the same size. If you used layers, be sure to enable "paste remembers layers" in the layers panel menu.
This kind of problem is often indicative of an underlying font issue. You said there are only three fonts, and you should verify that in Type > Find Font... Try replacing, at least temporarily the fonts in use with something else that you know to be reliable from other documents. You might want to do this before the other steps.
Peter

Media Encoder crashes when exporting from Premiere Pro

Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?

Try turning off GPU acceleration.

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5
Using Motion 5.0.6 and Final Cut Pro X 10.0.7 on New iMac (December 2012) Mountain Lion,
Intel Core i7 quad-core a 3,4GHz, Turbo Boost fino a 3,9GHz
32GB di SDRAM DDR3 a 1600MHz - 4 x 8GB
Fusion Drive da 3TB
NVIDIA GeForce GTX 680MX 2GB GDDR5
During the rendering of complex FCPX mac crashes and I have to force a restart.
I also happens when I try to export movies with Motion 5.
Does anyone have the same problem with my new iMac?

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:
find . $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl $ 2> /dev/null | wc -l
Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
The output of this command, on a line directly below what you entered, will be a number such as "35." Please post it in a reply.

Final Cut Express FCE Crashes when exporting to Quicktime or Quicktime conv

Final Cut Express FCE Crashes when exporting to Quicktime or Quicktime conversion!
This started completely out of the blue last night. The export gets about 30-50% done and FCE disappears from the screen and the "FCE quit unexpectedly" message pops up. This has never happened before and I was doing exports of this very project all week. All other projects won't expect, the current project won't export when brought into a new file, I tried reinstalling FCE, and I deleted the pref files spoken about in the forum.
Any Ideas!!!????

Try repairing permissions and re-boot.
Al

Crystal Crashes when exporting to PDF

Hi Experts,
Crystal reports crashes when exporting a report to PDF. I am using Crystal Reports for SAP Business One, what could be causing this..is it a patch level problem ?

Hi,
Please check this thread http://scn.sap.com/thread/3303863.
What is your B1 version and PL?
Thanks & Regards,
Nagarajan

Incopy CS6 crashes when exporting to pdf

Incopy 6 crashes when exporting to pdf. Message – unknown error

Hi Sushmar
My editor edits with Incopy 6, everything goes well until she wants to export a pdf, Incopy 6 then crashes. Incopy 5.5 does not have this problem. Please point me in the right direction, as we have extremely tight deadlines and no other way of working.
Tx
LVG

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

Is ILife 11 the current version today? Will its purchase upgrade my Iphoto 8.2.1 to Iphoto 11? I have a Macbook, Maverick and Iphoto is crashing when exporting photos. I understand ILife is the way to fix it.

Is ILife 11 the current version today? (May 2014). ILife 11 on Amazon appears to be 3+ yrs old?
When searching for ILife 11 on the Apple Store, I am directed to a separate purchase of Iphoto version 9.
Somewhat confusing, Apple is always so clear with these things.
The goal is to upgrade my Iphoto 8.2.1 to Iphoto 11.
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
I understand ILife is the way to fix it.
Thanks!

The current version of iPhoto is iPhoto 9.5.1., and it is the latest version of iPhoto '11.
If you are running Mavericks 10.9.2, you can buy iPhoto 9.5.1 from the AppStore - it is the currently sold version.
The iLife bundle is called iLife '11, and the iPhot version in iLife '11 is iPhoto 9.x.x. - that is confusing allright
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
While it is certainly useful to upgrade to the current iPhoto version to be fully compatible with MacOs X 10.9.2, there may be a differnet reason for the crashes. Is there an error message with the crashes? When did these start? Did you import new photos or videos? Install other software?

Flash CS5.5 crashes when exporting movieclip for Actionscript

Hello,
My Flash CS5.5 crashes when exporting movieclip for Actionscript (select movieclips -> modify -> convert to symbol -> check export for actionscript). I think this only happens when Photoshop CS5 is open.
Does anyone know how to fix this? I'm using Win7 64-bit. The only open programs are Flash, Photoshop, and Firefox.

Oddly enough, I opened up Flash again, today, just to see if it was still the same, and it had worked. Everything seemed normal, I opened a new document and started working. Then, out of nowhere it stopped responding again. So I waited for it to respond, it didn't. I closed it from the task manager, and now it's back to the original problem of crashing when I try to create a new document or open an old ontrie
Update: I tried the cleaner, as you'd suggested. Followed all the steps, but to no avail. Think it may have something to do with my machine, and less with the software?

InDesign Crashes when exporting to InCopy

I support several hundred InDesign/ InCopy users. We have been using this workflow for several years.
Approximately a month ago, we migrated to CS5 (7.0.3). I began to immediately get support calls that InDesign and InCopy were crashing. A few of the calls were that InCopy was crashing when pasting text from MS Office, but he overwhelming majority of the calls are for InDesign crashing when exporting stories to InCopy. If exported one at a time, the stories export fine. When exporting all stories or an entire text layer of stories, it will crash nearly without fail.
Our environment consists of Mac Pro 2x2.66Ghz and 2.8Ghz Intel Core Duo 2 iMacs running 10.5.8. with CS5 7.0.3. This is happening on multiple machines. A few of them have been gone over to verify base OS integrity, permissions repaired, DiskWarrior run etc… to make sure we did not have individual machine issues.
I need resolution for both issues, but the crashing while exporting is so prevalent that my graphic designers are starting to really get aggravated.
I searched the forum for "InCopy", for "export" and for "crash." None of those terms returned a single hit. I can't imagine those terms are not in this forum, so I am working on the assumption that searching must be broken at the moment.
Thanks in advance for any guidance,
Kevin

Try posting on the InCopy forum. There was another similar report there...
Did you fill out a bug report?
Harbs

IMovie 11 crashes when exporting to Quicktime

iMovie 11 crashes when exporting to Quicktime. Some people have posted that this problem disappeared when they upgraded from Lion to Mountain Lion. However, I am running Mt.Lion and it still happens. If there is no fix for this bug, does anyone know a workaround that will produce the same ultimate result..namely, a Quicktime movie that is not too large to attach to emails. Apple, please fix this. Thank you.

Update after two Apple iApps specialists spent 1.5 hours on the phone with me: There are 3 "poison pills" (that we know of) that will cause the crash if any of the three is part of the movie: Picture-in-picture, side-by-side, or a circle open/close transition. Otherwise, no crash. The specialist made a movie on his own computer, containing the poison pills, but he exported to Quicktime without a crash. There is at least one report in the threads of a problem like mine. Thus, some Gremlin is causing this, in some computers. The iApps specialist was curioius to know whether a lot of people have this problem, or only a few. (If a lot, then it is worth submitting to the engineers to fix.) He said if you have this problem, call Apple. I asked if such people should post a "Me too!" on this thread. He said no, better to call Apple and report it. So that's the story. I can live without those poison pills in my export-to-quicktime movies. I am just a consumer, not a pro, and I can live with it. But it would be nice if Apple could fix this.

Workarounds for project crashing when exporting?

I have developed a project in captivate 6 which is now crashing captivate when I export it. I can preview it in 'Web Browser' and 'HTML 5 output'. But when I export it as a SCORM package it crashes. I was able to do that yesterday but today it's crashing.
Any suggestions? Any one?
Slides contain nothing fancy except just mp3s, text and graphics.
Specs
Captivate 6 project
Tested on both Mac and PC
From,
Luke L

Hi Luke,
In Project Preferences, Start / End there is an option preload startscreen.
Best regards.
Philippe
Le 15 oct. 2012 à 21:48, Luke L PSA <[email protected]> a écrit :
Re: workarounds for project crashing when exporting?
created by Luke L PSA in Import/Export - View the full discussion
thank you tchiboo.
Which start screen is this? Thanks for the help desperate to know.
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/4775908#4775908
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/4775908#4775908
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4775908#4775908. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Import/Export 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.

Float4() causes "error saving Pixel Bender Byte Code file" error when exporting for flash player

Simple test
<languageVersion : 1.0;>
kernel untitled
<   namespace : "Your Namespace";
    vendor : "Your Vendor";
    version : 1;
>
    input image4 src;
    output pixel4 dst;
    void
    evaluatePixel()
        dst = float4(sampleNearest(src, outCoord()));
The above code will produce a "error saving Pixel Bender Byte Code file" error when exporting for flash player in Pixel Bender Toolkit 2.5.449694.
"dst = (sampleNearest(src, outCoord()));" works fine. And anything like "float4 a= float4(b);" will give same error.

Thank you for the error report. I'll put it into our bug database. We're bottling things up for the current version. Gven the workaround, it is unlikely we'll be addressing this bug soon. Please accept my apologies for the annoyance this will cause.
In your second example, float4 a = float4(b), does it return an error if b is only a float4 or regardless of what b is? If b is a scalar float, for example, is the conversion performed correctly? If so, this could be an error that only crops up when using constructor/conversion syntax when the thing being converted is already the correct type.
Thanks,
Chuck.

Cs2 files crashing when exporting to inx

Similar Messages

Maybe you are looking for