Generating large index in InDesign CS3 causes crash

I have a gig of RAM on a 1.42GHz PowerPC G4 machine. I cannot successfully run my index, which consists of approx 55 pages when it is complete, and contains about 5000 index entries retrieved from about 600 indexed pages (168 documents in the book file).
I have checked for overset (which Adobe should have built into the program) but found nothing out of the ordinary. The same manual ran perfectly fine in ID CS2. Of course I converted all CS2 pages to CS3 before I started the process. Here's how it went:
1. I started the generation of the index from the book file.
2. Waited about an hour.
3. Got standard message saying that this process was too big to undo, and said OK so it would continue.
4. Waited another hour, then did Option-Control-esc and found that InDesign CS3 was "not responding.
I would be more than happy to make the files available to anybody who wants to test it. Could it be as simple as needing more RAM?
Thanks,
__Jeff Syrop
jsyrop9gillig.com (replace the 9 with @)

Well, seems I have a similar extremely frustrating problem (on deadline) where I'm trying to generate an index for our catalogue & ID CS3 crashes every time. I tried closing down all other apps, removing all plugins except Adobes, & rebooting so I'm working with a fresh machine but to no avail. I know RAM isn't the problem as I have 6 gigs now & generating the index use to work fine in CS1 with 2 gigs.
We converted all 72 catalogue documents from CS1 to CS3 a few months ago. Since then indexes generated within individual docs worked fine. However now that I am trying to compile them all into a single book index I've had nothing but problems (crashes).
After several hours of trying possible work arounds I've come to the conclusion that something wrong within some of the files themselves. I know this because I've been adding a file at a time to the book & regenerating the index between each. What I've discovered is that ID will crash only when certain docs were added (usually fairly complex ones).
Fortunately I've been able to fix these files by exporting them to INX format & back again. So far so good... I'll update the forum if anything else goes wrong.

Similar Messages

  • InDesign CS3 (PC) crashed document recovery woes.

    InDesign CS3 (PC) crashes when trying to open a ID document so I can't determine the problem. How can I open it without crashing? The problem may be a font or a placed image but I don't know for sure because I can't open the file.

    It was on a PC and I brought in my Mac and got the same response. The links
    are in disarray, I suspect that is the root of the problem but not being
    able to open it I won't know for sure.

  • PDFs from CS3 causing crash

    More than one case has cropped up at my office with a pdf generated by a client with CS3. (We are still using CS for our workflow due to another program we are using that isn't compatible with the new stuff yet)
    So what happens in our workflow is this:
    We place the Indesign-CS3-generated-pdf into an Indesign-CS document. When we're ready to publish we pdf that doc (or, rather, our 3rd party workflow program pdfs it into the workflow). And we get the application InDesign CS has unexpectedly quit crash. The same scenario occurs when I tested it without the 3rd party. And I've tried playing around with different settings in the pdf export presets to no avail. Any tips?

    Don't know if this will be helpful or not ...
    Date/Time: 2008-05-23 15:15:09 -0400
    OS Version: 10.3.9 (Build 7W98)
    Report Version: 2
    Command: InDesign CS
    Path: /Applications/Adobe InDesign CS/InDesign CS.app/Contents/MacOS/InDesign CS
    Version: CS 3.0.1 (3010)
    PID: 993
    Thread: 0
    Exception: EXC_BAD_ACCESS (0x0001)
    Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000004
    Thread 0 Crashed:
    0 Font Manager 0x0a736b54 0xa705000 + 0x31b54
    1 PDF 0x0c80ab08 0xc78f000 + 0x7bb08
    2 PDF 0x0c7d8890 0xc78f000 + 0x49890
    3 PDF 0x0c7d7194 0xc78f000 + 0x48194
    4 PublicLib 0x005b8a8c 0x487000 + 0x131a8c
    5 PublicLib 0x005b4634 0x487000 + 0x12d634
    6 AGMCarbonLib 0x021487ec 0x2008000 + 0x1407ec
    7 AGMCarbonLib 0x02146340 0x2008000 + 0x13e340
    8 AGMCarbonLib 0x02143950 0x2008000 + 0x13b950
    9 AGMCarbonLib 0x0202fd54 0x2008000 + 0x27d54
    10 PDF 0x0c7aff00 0xc78f000 + 0x20f00
    11 PDF 0x0c7ac708 0xc78f000 + 0x1d708
    12 PDF 0x0c7a9fc8 0xc78f000 + 0x1afc8
    13 PDF 0x0c7a7060 0xc78f000 + 0x18060
    14 PublicLib 0x00529a74 0x487000 + 0xa2a74
    15 PublicLib 0x0052a648 0x487000 + 0xa3648
    16 PublicLib 0x00532d9c 0x487000 + 0xabd9c
    17 PublicLib 0x00529a74 0x487000 + 0xa2a74
    18 Group 0x0c6c4744 0xc6bf000 + 0x5744
    19 Generic Page Item 0x0865d498 0x8616000 + 0x47498
    20 Group 0x0c6c4f04 0xc6bf000 + 0x5f04
    21 Group 0x0c6c48bc 0xc6bf000 + 0x58bc
    22 PublicLib 0x00529a74 0x487000 + 0xa2a74
    23 PublicLib 0x0052a648 0x487000 + 0xa3648
    24 Layer 0x0b7c9008 0xb7c1000 + 0x8008
    25 Layer 0x0b7c887c 0xb7c1000 + 0x787c
    26 Spread 0x0b6f5bc0 0xb6e9000 + 0xcbc0
    27 Spread 0x0b6f5518 0xb6e9000 + 0xc518
    28 Spread 0x0b6f374c 0xb6e9000 + 0xa74c
    29 AppFramework 0x06b64380 0x6b18000 + 0x4c380
    30 PDF 0x0c7c3734 0xc78f000 + 0x34734
    31 PDF 0x0c7c55b8 0xc78f000 + 0x365b8
    32 PDF 0x0c7c13ac 0xc78f000 + 0x323ac
    33 PublicLib 0x004ed164 0x487000 + 0x66164
    34 Utilities 0x06fa8cc8 0x6fa1000 + 0x7cc8
    35 Utilities 0x06fa906c 0x6fa1000 + 0x806c
    36 AppFramework 0x06b395e8 0x6b18000 + 0x215e8
    37 AppFramework 0x06b3c124 0x6b18000 + 0x24124
    38 PublicLib 0x004ec938 0x487000 + 0x65938
    39 PDF 0x0c802224 0xc78f000 + 0x73224
    40 PublicLib 0x005c147c 0x487000 + 0x13a47c
    41 Export Manager 0x069247c4 0x6921000 + 0x37c4
    42 Export Manager 0x069238d0 0x6921000 + 0x28d0
    43 Export Manager 0x06923134 0x6921000 + 0x2134
    44 PublicLib 0x00568a14 0x487000 + 0xe1a14
    45 Actions 0x074d296c 0x74c6000 + 0xc96c
    46 Actions 0x074c9a1c 0x74c6000 + 0x3a1c
    47 PublicLib 0x005068ec 0x487000 + 0x7f8ec
    48 PublicLib 0x00505d28 0x487000 + 0x7ed28
    49 PublicLib 0x0050627c 0x487000 + 0x7f27c
    50 AppFramework 0x06b46148 0x6b18000 + 0x2e148
    51 AppFramework 0x06b46078 0x6b18000 + 0x2e078
    52 AppFramework 0x06b226ac 0x6b18000 + 0xa6ac
    53 PublicLib 0x004f5528 0x487000 + 0x6e528
    54 com.apple.HIToolbox 0x92882e50 DispatchEventToHandlers + 0x150
    55 com.apple.HIToolbox 0x928830c4 SendEventToEventTargetInternal + 0x174
    56 com.apple.HIToolbox 0x92895530 SendEventToEventTarget + 0x28
    57 com.apple.HIToolbox 0x928f94ac _Z20HandleTextInputEventP14OpaqueEventRef + 0x38
    58 com.apple.HIToolbox 0x92893aec _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv + 0x204
    59 com.apple.HIToolbox 0x92882f0c DispatchEventToHandlers + 0x20c
    60 com.apple.HIToolbox 0x928830c4 SendEventToEventTargetInternal + 0x174
    61 com.apple.HIToolbox 0x92895530 SendEventToEventTarget + 0x28
    62 com.apple.HIToolbox 0x92901db0 SendTSMEvent + 0xe4
    63 com.apple.HIToolbox 0x928c7d80 SendUnicodeTextAEToUnicodeDoc + 0x2b0
    64 com.apple.HIToolbox 0x928d1f20 utDeliverTSMEvent + 0x3fc
    65 com.apple.HIToolbox 0x92901cb0 TSMKeyEvent + 0x64
    66 com.apple.HIToolbox 0x928b3244 TSMProcessRawKeyEvent + 0x398
    67 com.apple.HIToolbox 0x928e4a8c _Z27HandleCompatibilityKeyEventP14OpaqueEventRef + 0x68
    68 com.apple.HIToolbox 0x928a5c20 _ZN13HIApplication12EventHandlerEP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv + 0x1c0
    69 com.apple.HIToolbox 0x92882e50 DispatchEventToHandlers + 0x150
    70 com.apple.HIToolbox 0x928830c4 SendEventToEventTargetInternal + 0x174
    71 com.apple.HIToolbox 0x92887544 SendEventToEventTargetWithOptions + 0x28
    72 com.apple.HIToolbox 0x928bbfec _Z19HandleKeyboardEventP14OpaqueEventRefm + 0x160
    73 com.apple.HIToolbox 0x92893ae0 _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRefP14OpaqueEventRefPv + 0x1f8
    74 com.apple.HIToolbox 0x92882f0c DispatchEventToHandlers + 0x20c
    75 com.apple.HIToolbox 0x928830c4 SendEventToEventTargetInternal + 0x174
    76 com.apple.HIToolbox 0x92895530 SendEventToEventTarget + 0x28
    77 AppFramework 0x06b25860 0x6b18000 + 0xd860
    78 AppFramework 0x06b4bdec 0x6b18000 + 0x33dec
    79 InDesign CS 0x000b0d24 0xb0000 + 0xd24
    Thread 1:
    0 libSystem.B.dylib 0x900171f8 semaphore_wait_signal_trap + 0x8
    1 libSystem.B.dylib 0x9000e9dc _pthread_cond_wait + 0x270
    2 ...ple.CoreServices.CarbonCore 0x90345158 MPWaitOnSemaphore + 0xb8
    3 ACECarbonLib 0x0104cdd4 0x1008000 + 0x44dd4
    4 ACECarbonLib 0x0104d010 0x1008000 + 0x45010
    5 ACECarbonLib 0x0104ca28 0x1008000 + 0x44a28
    6 ...ple.CoreServices.CarbonCore 0x90345c44 _MP_CFMTaskProc + 0x20
    7 ...ple.CoreServices.CarbonCore 0x902f6b14 PrivateMPEntryPoint + 0x4c
    8 libSystem.B.dylib 0x90024930 _pthread_body + 0x28
    Thread 2:
    0 libSystem.B.dylib 0x9001a6ec syscall + 0xc
    1 ...ple.CoreServices.OSServices 0x906200cc BSD_waitevent + 0x2c
    2 ...ple.CoreServices.OSServices 0x9061cac0 CarbonSelectThreadFunc + 0xb0
    3 libSystem.B.dylib 0x90024930 _pthread_body + 0x28
    Thread 3:
    0 libSystem.B.dylib 0x900171f8 semaphore_wait_signal_trap + 0x8
    1 libSystem.B.dylib 0x9000e9dc _pthread_cond_wait + 0x270
    2 ...ple.CoreServices.OSServices 0x90627300 CarbonOperationThreadFunc + 0x50
    3 libSystem.B.dylib 0x90024930 _pthread_body + 0x28
    Thread 4:
    0 libSystem.B.dylib 0x90018e38 semaphore_timedwait_signal_trap + 0x8
    1 libSystem.B.dylib 0x9000e9d4 _pthread_cond_wait + 0x268
    2 ...ple.CoreServices.CarbonCore 0x902c59f0 MPWaitOnQueue + 0xe0
    3 com.apple.DesktopServices 0x90948c1c _ZN13TNodeSyncTask12SyncTaskProcEPv + 0x70
    4 ...ple.CoreServices.CarbonCore 0x902f6b1

  • Creating an index in InDesign CS3 - is there any way to limit where and for what it looks?

    I'm creating an index for a 300-page book using InDesign CS3 on both a PC with Windows XP home and a MacPro with OS X Leopard (I take this book back and forth between these two computers). I have created this as a book (.indb) file so I can use the Index panel with the book option checked to include all of the book chapters.
    There are two things I was wondering how to do, if they can be done at all.
    1 - I want the index to look for entries in the main pages only, not in the master pages.
    2 - I'd like to be able to do only attributed text. For example, I'd like the index to find only the word people when it is bold and italic, and not all of the other places it may occur. Can I do this with a style also, paragraph and/or character?
    Thanks so much,
    Marcy

    Read http://help.adobe.com/en_US/InDesign/6.0/WS8721440D-5F68-4fd6-8115-CA3BEDACF001a.html (the online Help on indexes) -- it will probably answer a few questions.
    One I do know immediately is your question on "picking up" stuff from master pages and only with formatting. InDesign does not make an index for you -- you have to (oh! manual labor!) mark the words that should appear in the index yourself. So just don't mark them on master pages, or when not bold and/or italic. You might be wondering about that little button "Mark all instances", well, it does what it say, and in your case you do not want to mark all instances.
    The Capitalization issue is, AFAICR, somewhere in the Help; and so is your singular/plural stuff. The latter one is easy solved: if you mark a word to be indexed, ID asks you in a friendly dialog how it should be included, and that defaults to the current selected phrase, but you are free to edit the text in that dialog. ID does not mark the word or phrase; it inserts an invisible marker inside the to-be-indexed word that contains all information you enter in the Add Index Entry dialog, and it uses that to determine what page number to add. (That invisible marker is visible with "Show Invisible Characters", and can be cut, pasted and deleted at will -- so to remove a water melon, find the marker, and delete it.)

  • INdesign CS3 suddenly crashes when trying to export pdfs

    I have exported PDF-x1as from Indesign for years with no issues. Suddenly today, indesign crashes when I select EXPORT. I have indesign CS3 on a macbook pro running 10.5.8.
    I work from home, and have to get some pretty huge projects out to the printer, and so I'm getting nervous about this not workling!! I'm trying to remain calm.
    I've restarted indesign with the control, option, and shift keys down, supposedly renewing the prefs. When that didn't work, I reinstalled it from my original disks. Still doing the same thing.
    Please say someone knows a fix!!!

    ok - I've spent countless hours now searching for an answer. I was about to upgrade to snow leopard hoping that would solve this issue, when, buried deep somewhere in these forums, I found the solution that, at least so far, has worked for me! Here it is, in case anyone else is having issues:
    http://kb2.adobe.com/cps/402/kb402521.html
    phew!!!!

  • Large project in Premiere CS3 causes Windows XP64 to reboot

    Ok...I have a rather sizeable project going in Premiere CS3.  It contains a rather large number of animations created in Autodesk Maya (most between 10 seconds and 3 minutes long) and a large number of stills, as well as scrolling background (a .mov file I created using Photoshop and Premiere) and a soundtrack created by myself (in Cakewalk/Sonar).  The total project is about 18 1/2 minutes in length....around 8 video tracks and 3 audio tracks at the moment. The main problem is that when I start working on it...either importing files and especially moving files around in the project or even just hitting the playback button, the system just reboots.  I have seen the infamous Windows "blue screen of death" flash briefly once or twice, but it doesn't hang...just goes right to the system BIOS screen.  The ONLY thing that seems to help is basically saving the project like every 30 seconds.  Import a file, save, conform file to widescreen, save, bring file into project, save, move file around a bit, save, add crossfade, save....you get the idea.
    Now before I go too much futher here, I suspect the problem isn't actually with Adobe/Premiere as I had this happen a few times while I was creating the sound track in Sonar 4 as well.  The sound track is basically a pseudo-orchastral piece and is equally around 18 1/2 minutes long....currently with around 42 tracks of audio and 5 midi tracks.  The audio has been sampled down to a standard stereo wav file for the import into Premiere. And yes, as the audio portion of this project got bigger and bigger, it caused a few reboots as well (not to mention drop-outs, studders and all the other fun stuff associated with audio production).  With that, I was able to "compact" the Sonar file (basically a Sonar project defrag) and the reboot problem seems to have went away on that end.
    The system itself SHOULD be able to handle this project...not top of the line, but pretty beefy. 2nd generation Intel i5 quad core, 16 gigs of Kingston DR-1600 RAM, Tascam US-428 for the audio and a good 2+ terabytes across 5 harddrives (3 internal 3 gig-per-second SATA's, 2 USB).  Also has a 4 gig HIS vid card with ATI chipset (still can't afford a FirePro yet).  While Premiere is installed on the (comparatively dinky) 160 gig C drive, I'm using the 500 gig E drive internal and a 500 gig USB drive as my work drives.  Most of the Maya animations are on the internal E drive but the rest...the stills and Premiere files and such...are on the USB drive.  I.e., the system itself should have plenty of rendering power for this.  Also I have replaced the C drive with a nearly identical twin.  After a recent crash, I finally broke down and got a backup C drive...in other words, I'm sure the drive(s) are a-ok...even put a brand new 500 watt power supply in just in case.
    I have already re-installed XP64...a couple of times in fact, as just before I started this project one of those god-foresaken MS "critical updates" crashed the crap out of my computer.  Then on the first reinstall, something hosed in .NET framework during the "night of a thousand updates" so I had to scrap it and start the reinstall all over again.  Likewise, I reinstalled Premiere CS3 (along with everything else including Maya) once I finally had the computer running again.
    A quick note here: I did create my own custom 1080 Hi Def widescreen settings for Premiere since CS3 didn't appear to have any such thing.  For short projects they seem to work just fine...although admitedly, the render time is a serious b*tch.  Likewise, all the Maya animations have been rendered out at 1080 widescreen, production quality (yea...the render time there was a killer too).
    Another quick note:  While I'm trying to use Premiere exclusively while I'm working, on occasion I have had to open either Photoshop or Maya to deal with a couple of stills...and when I open something else, I get a "windows virtual memory to low" (16 gigs of RAM and the virtual memory is too low??).  Otherwise, except for Avira (virus scanner) I don't really have anything else running in memory...no screen savers, no desktop pictures, no Instant Messanger crap, etc..  Never cared for bells and whistles and such, so the system is pretty clean in that regard (and I do keep up on my degrags as well).
    Finally, while I -am- grateful for any helpful suggestions regarding this, please do NOT simply tell me to upgrade something (Premiere, Windows, etc) as point blank; it ain't gonna happen.  Aside from the fact that Adobe seems to have made Premiere CS4 and up much more difficult to use (I have -many- niggles about the newer interfaces there...using CS5.5 at the college and it's REALLY annoying) and aside from my wife being a MS programmer/developer and having to listen to her complain about Windows 7 and 8, we're in the process of buying a new house, so any and all "disposable income" is nill...and will be for quite some time.  No money...zero...nadda...i.e. no upgrades.  Further, while granted this is certainly the biggest project I've done to date, I've ran this setup/configuration for at least the past 3 years now without a hitch...this all seems to have started with that last MS critical update (at the risk of sounding paranoid, I'm really starting to think they slid a nasty in that last one to FORCE people to upgrade since they're discontinuing XP64 support soon). 
    Alrighty...I know that's a lot but I wanted to provide as many details as I could here in hopes that someone can help me get a handle on this reboot issue.  Getting to be REALLY annoying having to save every 30 seconds or so.  I have searched the help files, but got tired of randomly sorting thru all the blather and not finding anything helpful.
    I'm grateful for any help here...thanks!
    Jim

    Well, I'm about 98% sure it isn't a hardware problem.  I had already pulled the RAM and tried some backup RAM I have sitting in the box (8 gigs of Corsair), went thru the harddrives weeks ago with Chkdsk and everything was a-ok there (a couple of bad clusters on the old C drive, but that has since been replaced and is on the shelf as a backup), motherboard seems to be fine, re-seated all cards and cables, etc..  Again I even slapped a new 500 watt PS in just in case (the old one was a 400 watt and with all the crap I have on this system, thought it might have been a voltage drop off issue...nadda).   I did have a bit of a heat problem a while back...one of the case cooling fans was going bad and the CPU was getting just hot enough to trip the system (about 5 degrees over).  That said, that also shows up in the BIOS monitor as well and was easy enough to track down.  Either way, the bad cooling fan has been replaced and I even added a "squirrel cage" style fan as well...system is running nice and cool now.
    BTW...I used to be A+ certified on both PC's and Macs when I was a hardware tech (not to mention HP, IBM and Lexmark certified, Cat 5 installer, etc), so I like to think I know my hardware fairly well.  Not just a weekend warrior on that front...used to do it for a living.
    I had also already tried manually resizing the paging file as well...tried different sizes, tried spreading it out across the drives, etc..  Didn't really make a difference either way and again the only time the virtual memory low comes up is if I try to open Photoshop or Maya while this big project is open in Premiere.  That said, Photoshop and Maya both tend to be pigs when it comes to memory/RAM (Photoshop especially).  Doesn't seem to happen with Illustrator or any other program....just PS and Maya if this project is open in Premiere.  
    One other oddity I have noticed recently is actually with Maya.  Before all of this started...in other words, before that last MS critical update and 3 days of reinstalling software...I used to be able to do a background render with Maya and still be able to keep working on stuff.  I'd fire off batch render and then I could move on to other things...editing images in Photoshop (CS 5 there if it matters), surfing the web and even doing some light stuff in Premiere.  Since this problem has been occuring however, I have noticed that the Maya batch renders are REALLY slowing down the system big time.  Difficult to even check my email while a batch is running.  Likewise, I have noticed that since I upgraded the Maya from 2011 to 2013, Maya has a nasty tendency to freeze during a batch render.  If I have a long batch render, I'll set it up to run over night...when I get up the next moring, the render itself will still be running (you can see Mayabatch.exe still going in processes under Task Manager) but Maya is totally frozen up.  Now I did that update at the same time as the rest of this mess happened so I don't know if these problems are due to the Maya upgrade or the (apparent) Windows problem...I'm inclined to believe the latter.
    BTW...after having a project file get corrupted yesterday during one of these shut downs, I've been double saving the files (so as to have a backup) and that too seems to have made things a bit better.  Hasn't actually shut down on me when I've been doing this.  That said, it's also a serious pain in the butt having to save that way too.
    With that, looking thru the rest of Hunt's article there, I did kill indexing services...at least on the work drives.  it's about the only thing there that I haven't tried, so we'll see what happens this afternoon.  I seriously doubt that would be the problem though as usually that would give an error or a lockup and not an instant shut down, but we'll see.

  • After Client quits Indesign Cs3, it crashes.

    Clients docs are saved, but Adobe thinks they are not and asks if she would like to restore them. She must go through this ordeal every time she quits Adobe Cs3. Anyone have a solution, or even seen this problem? Thanks.

    Hi, we are getting the same thing here. Have you had any feedback or a resolution to this issue? iiod, maybe we can pool resources and troubleshoot together, full specs can be posted if needed (don't have them handy right now).

  • InDesign CS3 Index problem

    I am trying to combine the indexes of several 30-40 pg. stories in an inDesign CS3 book for print; however, once I minimize the story and try to paste its index into a separate blank document, the cursor is no longer "loaded." It seems that the only way I can create an index is at the end of each individual story, then paste them all into a document and manually alphabetize them. Is there a method by which I can create the index for the entire book at one time?

    The help file says you can index the whole book:
    Long document features / Creating an index
    Generate an index
    Once youve added index entries and previewed them in the Index panel,
    youre ready to generate an index story to place in your document for
    publication.
    An index story can appear as a separate document or in an existing
    document. When you generate an index story, InDesign compiles index
    entries and updates page numbers across your document or book. If you
    add or delete index entries or update numbering in your document,
    however, youll need to regenerate the index to update it.
    If an index marker appears in overset text when you generate the index,
    you are asked if you would like to include these markers in the index.
    If you click Yes, the entry appears in the index without a page number.
    etc

  • Indesign CS3 crashes when making pdf

    I had this problem 2 months ago, and I thought it was fixed, but it's started happening again. When I try to export a file as a pdf, InDesign CS3 will crash/close the program. However, I CAN export pdfs in CS. It also crashes when trying to import/place a pdf file or other type of file.
    I am using a PowerMac G4. Version 10.5.8.
    Thanks!!

    Dual Personalities, eh?
    I'd tru running something like Cocktail or MacJanitor to clean your caches -- I'm on Windows so there may be a better way known to Mac folk. Emptying the temporary files is a good idea, but again, I don't know where they live on your system.

  • Indesign CS3 Crashes when loading text styles

    hi all, i need some help.
    Indesign cs3 keeps crashing when I try to "load all text styles" from one indesign file to another. the file has ten styles (character & paragraph). I'm currently working on windows 7.
    thankyou for any information you can provide.

    Are you patched to 5.0.4?
    Export both files to inx, re-open, Save As. (I checked, ID will not load styles from an inx)
    Load just one style at a time to isolate a conflict.
    Last resort, Highlight text from the source doc, paste into the new doc. I should carry in the style. It only needs to be a single charatcher.

  • Adobe InDesign CS4 Keeps Crashing #$%@@*(!

    Please help. It has been a nightmare since we installed CS4. InDesign CS3 never crashed. But since we
    For some reason I keep getting the error "network connection lost for the C:\file.indd or the file was modified by another process". And then the system crashes. It usually happens as we are placing or link pictures. Occasionally it will happen as we are exporting to a PDF.
    We store all of our pictures and artwork on a Netgear file server. I don't think that is the culprit because CS4 and CS3 worked fine. Does anyone have any solution to this problem.
    I checked Adobe's website and they are aware of this error but only post a solution for a mac. We use PC's here so upgrading Leopard will not help.
    Thanks

    Please help. It has been a nightmare since we installed CS4. InDesign CS3 never crashed. But since we
    For some reason I keep getting the error "network connection lost for the C:\file.indd or the file was modified by another process". And then the system crashes. It usually happens as we are placing or link pictures. Occasionally it will happen as we are exporting to a PDF.
    We store all of our pictures and artwork on a Netgear file server. I don't think that is the culprit because CS4 and CS3 worked fine. Does anyone have any solution to this problem.
    I checked Adobe's website and they are aware of this error but only post a solution for a mac. We use PC's here so upgrading Leopard will not help.
    Thanks

  • Indesign CS3

    Indesign CS3 is crashing when file> place.
    Two months back I remedied the problem by uninstalling & reinstalling the entire CS3.
    Surely there has to be a better way.

    The better way is to post this in the InDesign forum...with full system details.
    Bob

  • Indesign CS3 crash while generating an PDF or deleting an index entry

    Indesign crashes when I will starting the PDF export. This happens in all Indesign documents which are converted from CS2 and with index entries. So I want to delete the index but Indesign crashes while deleting too. I tried to convert the files in .indx files but nothing changes. Indesign is still crashing.
    Indesign 5.0.2
    Mac OS X 10.5.3
    MacPro Identifier 3,1
    RAM: 4GB

    Hi. Im having the same problems and tried everything. Indesign crashes not just on Exporting, but also Import and Save As. It mostly works with no problem for days and then all the sudden crashes and cant fix it, then in about an hour starts working again, with the exact same document. It seems to me like the software cant find the path it created with the document. For example, if I press just SAVE, its saves with no problem, but when I choose SAVE AS, Indesign crashes after opening the communication window.
    I still have PowerBook, not MacBook Pro, and OS X 10.5.3, so I figured my computer cant handle the new system and CS3. Although Im not having any problems with Photoshop nor other CS3 software, just indesign.
    I would really appreciate some advice or response.

  • InDesign CS3 index crash/quit

    We have a file that was originally created using InDesign CS3 on OS X with an index but it's now crashing: if any of the index text is amended/deleted it crashes and quits. Even trying to delete the actual index pages does the same. The file won't open at all in CS4 and crashes/quits that as well.
    We've tried the following:
    - removed the index markers across the document and updated preview
    - manually removed from the index pane all references
    - deleted every other page other than the index and have isolated the issue to something in the index content.
    There don't appear to be any font conflicts after checking.
    Has anyone else come across this as we need to use this file as a template for another but are slightly paralysed with this index issue?

    Sorry for the delay, took me a while to find a non-Intel Mac with CS3...
    So, yeah, I see your problem. CS3 crashes while exporting the INX. Though it looks like it gets most of your document.
    I'll play around with it some more...
    Citrus Design wrote:
    That's the problem, we can't even get this far as CS3 crashes when trying to export to INX.
    The original document was created on a G5 PowerPC Mac, Leopard and CS3 but we don't have access to this set-up any more so we're a bit stumped.

  • InDesign CS5.5 crashes when generating index

    Hello everyone.  I have been working on a 232 page catalog and have been indexing as I've went along.  The catalog itself (232 pages) is a book file.  When I generated the index before it seemed to take a long time, but it always got through it and had no problems.  One day, randomly, it decided it wasn't going to work anymore and crashes when I re-generate the index.
    I have tried to add documents at sections at a time to see if it might be a particular file, but my tests have all been inconclusive.  I have the catalog separated into 8 sections (32 pages each) I added 1, 2, 3, 4, and 5 generating the index after each addition.  I got to section five and it was still okay.  When I added section 6 it crashed.  I tried generating section 6 by itself and it was fine.  Then I generated sections 1-5, and 7 together and it still crashed!  I've done every possible combination of index generating and I'm getting desparate.  I really do not want to have all my indexing work on the entire back section of the catalog to be wasted.
    Is anyone having a similar problem?  If I could get it narrowed down to one section, it would help greatly.  I do have x refs in my documents but they are all contained within section 4 (which had no problems generating).
    I'm assuming the problem lies within section 6 or 7, but I generated them together by themselves and the index generated without a problem.

    My InDesign crashed a couple of months for no apparent reason and, whenever I tried to resume the same activity as I was doing when it crashed, it crashed again! I wasn't creating an index but adding photos. Bascially, what I had to do was copy and paste all of my data into a new document. That worked. It was a pain, because I had to copy the master pages, style sheets, blah, blah but it worked. I think what happens is that files get corrupted if they keep crashing. You're better off just grabbing the data and creating a new doc. A pain, I know but....
    Good luck! I am just now getting into Indexes, btw.

Maybe you are looking for