Skip navigation

InDesign crashes when updating InCopy ICML files

Jul 1, 2010 9:28 AM

  Latest reply: John Hawkinson, Sep 17, 2013 4:23 PM
Replies 1 2 3 4 Previous Next
  • Currently Being Moderated
    Mar 19, 2012 12:10 PM   in reply to Pickory

    All my culpits are repaired at the moment. Care to enlighten us as to your theory?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 12:17 PM   in reply to E Diane King

    Hello,

     

    I wrote a plugin that required some special attributes to be saved when the user pressed command / Ctrl S. Well InCopy CS5.5 did not save the attributes. Anchored items may have such attributes.

     

    We fixed it by intercepting the save command.

     

    P.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 2:30 PM   in reply to Pickory

    Pickory, Tell me about! Plugin??

     

     

    Where? how much??

     


     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 2:32 PM   in reply to Pickory

    I cant share publicly the files, because they are from my client ... I will "modify" and post the files for you to prove your theory!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 2:37 PM   in reply to sectiond007

    Hi, Persons,

     

    My best to all!

     

    I never could enter into a discussion "high level" about InDesign and InCopy Practices... I feel less alone!...

     

    Hopefully I can contribute!!!

     

    I'll be online in the forum Starting now!

     

    Thank you so much, guys!  You are the best!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 2:47 PM   in reply to E Diane King

    I am Consultant at Adobe in Brazil and present the products in my country since version 2.0 ...

     

    Here is the only place I can say "I was angry"

     

    E Diane, I agree with you about "the more complex, more problematic" is a great consideration!

     

     

    But Brazil is a "wild west" in technical support category, Adobe Brazil has an office that is strictly commercial, support issues are resolved by the consultants ... in my case, I need to run Indesign CS and InCopy CS 5.5 anyway!

     

     

    The only place where people at least "hear" my problem and "suggested" a solution was here. I called the support for Brazil (from Holland and don't speak my language or English is a mixture of Portuguese-Portugal with Portuguese-Brazilian and Spanish) called me once and hung up on the second ring: never again!

     

    I am in this market for 10 years, but we pick up so much that it gets a little discouraged ...

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 20, 2012 10:42 AM   in reply to FabianaGO

    Hello FabianaGO

     

    Are you able to get a file to me?

     

    P.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 20, 2012 11:54 AM   in reply to Pickory

    Hi, Pickory!

     

    My best for you, boy!

     

    I'll have to unmount the file before you send ...

     

    Because I have not permission to send! I'll take one or two days but I send you!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 20, 2012 12:35 PM   in reply to FabianaGO

    Hello FabianaGO

     

    Dont't get your self into trouble. Ask your customer to give you a file that you can reproduce the problem in. Ideally steps to produce a broken InCopy document.

     

    Do remember this is only a theory, I could be barking up the wrong tree.

     

    All the best.

     

    P.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2012 1:38 PM   in reply to Pickory

    Any progess on this?

     

    I have all the broken InCopy / InDesign files you could ever need. CS5.5 just tell me where to send ... happy to send crash reports as well... What I have found is there must be some kind of translation issue. It occurs with anchored items in text and with multiple column tables.... I have tried everything including starting from a fresh document ... to starting from a new incopy file. I can open and save all day long from InDesign but the first edit made in InCopy corrupts the file.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2012 1:47 PM   in reply to JLMDesigns

    Not really… I have a crazy inefficient work around that I outlined in the forum.

    It got the project out the door but made for a very cranky lady.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2012 10:34 PM   in reply to Pickory

    My work around is to export from InDesign and open with incopy. Make changes in InCopy then save. Open the InDesign Document then do not update the information. Instead select all the boxes and drag it to the desktop as a snippit.

     

    Then save the file and drag the snippet back to the Indd file. Then update the links from the icml file.

     

    Just repeating this process each time a change is made in InCopy... this generally works more than it fails to work.

     

    Now what does this tell any normal person?

     

    Somethng is amiss --- ... Hello Watson, are you there?!?  What is the definition of insanity? InCopy / InDesign work flows requiring intervention by the user.

     

    Breaking the geometry and relinking the text information to old geometry... come now I should just make a javascript do this then sell it to Adobe... gosh isn't this rather Quarkish?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 23, 2012 7:50 AM   in reply to E Diane King

    I'm now on CS6 and having the same exact problem. I'm now working on files that had no problems at all in CS5 but now that I'm in CS6, updating the stories causes a crash on every edit by an IC editor. I have to place the files in a new doc and copy and paste the text back into the layout. Exporting to IDML doesn't work this time. The IC update still crashes the docs opened from IDML--this fix worked for CS5.

     

    This is becoming a serious bug and very irritating. I have to keep breaking the links to the stories so that I can copy the text from them and then re-export for the editor and then break and copy and re-export for every little edit. This is getting old really quick!

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 7:27 AM   in reply to E Diane King

    Like others in this thread, I have this problem of ID crashing when updating IC files that have anchored objects and long tables. I'm dismayed this hasn't been resolved in CS6. (I'm still using CS5, Mac OS 10.6)

    While the assorted work-arounds work, it's a pain. I try to avoid using anchored objects, and that's a shame.

    We have one project that is 150+ page booklet that is basically one long continuous table where we had to give the editors InDesign to make their changes as IC exports crashed repeatedly.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 21, 2012 8:56 AM   in reply to allisonblake

    I might as well throw my two-cents.  We are experiencing the same exact problem.  Unable to update stories fron inCopy as inDesign continues to crash.  We are expereincing this problem on CS5.5, CS6. Hopefully, that will get this issue fixed.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 23, 2012 1:11 PM   in reply to SkywalkerOne

    Well, I just did my first complicated layout in ID 6 and am also having the crash on update of InCopy story. Not only is it not fixed in CS6, it appears to be worse than it was in CS5. In CS5, I could export to IDML and that file, when opened, would allow an update. Now the only work around that works for me is to place the InCopy into a blank file, copy, open the original file without updating links, delete the InCopy stories from the assignments pallet, select the entire story and paste, re-export to InCopy. I'm really afraid that the next time the editor edits the story, I'm going to have to go through it all again. This is NOT good at all. Pretty much defeats the point of the InCopy workflow.  My stories contains in line and anchored images.

     

    This is the E.Diane King posting under a new screen name

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 24, 2012 2:45 PM   in reply to DKingDesigner

    OK, folks. I'm not sure if anyone is monitoring this thread any more, but this issue just sky rocketed to the top of my frustrations. As I mentioned above, the InCopy story update bug is even worse in ID CS6 than in CS5. I've just spent the entire afternoon trying to troubleshoot just one file to try and figure out what it is causing the crash.  This crash happens with ID and IC if the story in question needs to be updated.

     

    Here is what I've tried:

    • I tried creating a fresh new template in ID CS6, importing only the text (with styles) and a few object styles. Crash.
    • I tried placing the IC stories in a blank document and flowing them out to however many pages it takes to complete the story. The IC files place without crashing, but if they need updating, an update to the flowed story crashes ID.
    • I tried creating an IC assignment for the editor to work from (he was opening the ID file). Crash
    • I tried taking out all column breaking in the text styles. Crash
    • The file contains anchored objects, so I tried doing a find for all custom anchored objects and changed them to in-line. Crash
    • I deleted all split columns and span column styles or changed them to single column. Crash
    • The story contains in-flow icons linked to an AI file. I embedded all the icons. Crash
    • I deleted all the icons. Crash
    • I also tried exporting the story as plain text and placing it back into the flow. Crash.

     

    Work arounds I have tried:

    • Saving to Indesign mark up language (IDML). This worked for this problem in CS5 (not only to get the IC file to update, but also the file never had the problem again). Updating still crashes in CS6.
    • Deleting the link to the IC and then deleting the text in the flowed story frames and then placing the IC story with the cursor in the first text frame. Crash.
    • Deleting the link to the IC story, then deleting the text in the flowed story frames. Placing the text without any frame selected and then clicking into the first story frame to flow the text. This does not crash ID, but it's an awkard work around. Often, the story doesn't flow completely through the linked frames, and I have to manually link the frames again. It also doesn't always work for all the stories involved.
    • The only work around that always works is placing the culprit IC file into a new blank document, select all the text and copy. Return to the original file, delete the IC link and select all the text and paste. Re-export the IC file.  This is a very cumbersome work around and pretty much defeats the purpose of an IC workflow.

     

    I'm working on a fully-updated InDesign CS6 on a fully-update Mac tower running Mountain Lion. My editior is working on a fully-updated InCopy CS6 on a fully-updated Windows 7 laptop. The files we are working on will amount to hundreds of files with multiple edits per file (two IC stories per file). They are stored on a server.

     

    I seriously need help with this or I'm going to end up having to move both msyelf and my editor back to CS5 to finish this three year project (and I like CS6).  It's either that or get my editor InDesign and abandon the IC workflow entirely.

     

    I know Adobe is going to pretty much ignore me since I've already tried all the normal fixes, and this bug is not widely distributed among the user base so it probably doesn't warrant their attention. I'm pretty sure that it IS a bug since it existed in CS5 as well.  However, I'm not at the point where I can show the step by step progression that creates the behavior.

     

    Anyone have any ideas what else I can try in my troubleshooting to track down the problem?

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 24, 2012 5:50 PM   in reply to E Diane King

    Diane:

    OK, folks. I'm not sure if anyone is monitoring this thread any more, but this issue just sky rocketed to the top of my frustrations. As I mentioned above, the InCopy story update bug is even worse in ID CS6 than in CS5.

    I will say, I have been reading this thread, with trepidation and fear, and I'm worried. Our production environment of InCopy/InDesign remains on CS5 and we really do need to transition that sooner-or-later, and this is therefore pretty scary.

     

    With respect to your actual crashes, though, can you post them to http://pastebin.com/ for analysis? Have you passed any of them on to Adobe support?

     

    I suspect moving back to CS5 is the way to go in the short term. And I hate to ask it, but have you tried CS5.5?

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 24, 2012 7:14 PM   in reply to John Hawkinson

    John,

     

    I will reassure you that the IC/ID workflow usually works. I've worked all summer on a different project in CS6 with two separate editors working through IC assignments on files stored in a common Dropbox with very few problems. The reason I'm so frustrated in the case I mentioned above is that I know there is something about these particular files that is creating the crash and I can't figure out what it is--which means I can't report it as a bug to Adobe. I believe it may have something to do with anchored objects in coordination with spanning/split columns. If you don't regularly use the spanning/split columns or don't use them with other slightly less than stable ID features such as anchored objects or tables, you may be perfectly fine using an IC workflow in CS6.

     

    As to CS 5.5, I did use it but not with IC, so I can't speak to that workflow.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 24, 2012 8:44 PM   in reply to E Diane King

    Diane: I don't see why not knowing the cause prohibits you from reporting the bug to Adobe. Just give them the file.

     

    You did not answer my question about making the crash reports available...

     

    Yeah, I think Douglas Waterfall did a lot of work on improving the span/split logic around the CS6 timeframe.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 25, 2012 5:08 AM   in reply to John Hawkinson

    The last time I check the bug reporting, you have to give them the steps to creat the bug, which I don't know for this particular problem.  There's no way to "give them the file" on the bug report form.  The only time I've been able to give Adobe a problem file was when an observant Adobe employee found my thread about the text wrap bug in CS5 and gave me his email address to send the file to. He followed up on it until the techs closed the case without a solution. As far as I know that bug still exists as well, though the users on the forum decided it has to do with using a spanning columns option in a style on a page where there are no columns that causes it.

     

    Thanks for the link to pastebin. I'll see if I can't get an error report into that for everyone to see. I cannot share the problem files pubicly as they are copyrighted and in production, but would be willing to email them to individuals who want to see if they can replicate the crash. You need both IC and ID to create the problem.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 25, 2012 5:13 AM   in reply to E Diane King

    Well, I would suggest opening a support case at http://adobe.com/go/supportportal is always more effective than the anonymous "throw a wish in a well" approach ("don't ask and I'll never tell"). They might try to charge you $30 for the privilege, but they'll credit it to you in the case of a confirmed bug, which this seems to be, no question.

     

    You should be able to find the historical crash reports in Console.app, or ~/Library/Logs/DiagnosticReports/.

     

    You can email me the files and repro instructions (jhawk@mit.edu).

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 25, 2012 6:13 AM   in reply to John Hawkinson

    John,

     

    Your support portal link above didn't work for me. I recieved an Adobe website error "error processing your request." (edit: just tried the link on Chrome and it worked.)

     

    Files are emailed to you. Thanks for your help.

     

    Message was edited by: E Diane King

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 25, 2012 9:47 AM   in reply to E Diane King

    I've posted my latest crash report at http://pastebin.com/ryD7yfC6

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 25, 2012 7:50 PM   in reply to E Diane King

    Sorry for the delay, it has been a busy day.

    Your support portal link above didn't work for me. I recieved an Adobe website error "error processing your request." (edit: just tried the link on Chrome and it worked.) 

    When it fails, that typically is the result of screwed up browser cookies. Removing adobe.com cookies and trying again tends to work.

     

    I've posted my latest crash report at http://pastebin.com/ryD7yfC6

    So, your crash report has:

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   PublicLib.dylib                    0x016c5372 ProtectiveShutdown::~ProtectiveShutdown() + 278
    1   PublicLib.dylib                    0x016c53f5 ProtectiveShutdown::~ProtectiveShutdown() + 17
    2   com.adobe.InDesign.AppFramework     0x1197c20f 0x11960000 + 115215
    

    This means InDesign detected corruption and executed a protective shutdown, and you're supposed to look at ~/Library/Caches/Adobe InDesign/Version 8.0/en_us/InDesign Recovery/ProtectiveShutdownLog for more details.

     

    I opened your .indd file and was informed that assignments were out of date and updating produced a crash similar to yours. In my case, the protectiveshutdownlog offers:

     

    Adobe InDesign Protective Shutdown Log
    Thu Oct 25 22:40:00 2012 
    
    Unhandled error condition
    
    Session started up at 20:28:41 on Sunday, October 21, 2012
    Version: 8.0.1 - Build: 406
    
    Error Code 0x20705: "The content is locked and cannot be modified."
    
    
    Called to process command 0x7313
    Command Processor Stack (from top to bottom):
    6. Command Sequence "Re-import File"
    5. Command 0x7314 "Re-import File"
    4. Command Sequence "Update"
    3. Command Sequence ""
    2. Command 0x8c59 "Update Link"
    1. Command 0x8c9f "Update Link"
    

     

    That's all well and good, but what does it tell us? Not quite so much, but more than we had before.

     

    So obviously something's corrupt here.

     

    • I also tried exporting the story as plain text and placing it back into the flow. Crash.

    Err, so did you try creating  new INDD document and then placing the text? There's something toxic about your document, not sure what it is, and presumably it is re-infectig your assignment...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 26, 2012 4:42 AM   in reply to John Hawkinson

    Err, so did you try creating  new INDD document and then placing the text? There's something toxic about your document, not sure what it is, and presumably it is re-infectig your assignment...

    Look at the first two things I tried in my longer post from the other day.

     

    The actual text of these documents (and there are a lot more than one and they are all crashing) come from Word documents. I place the Word documents into a separate document and format the text and the sideheads and then a flow that into my template. The text is fresh for each document, so in my mind that means the only place a corruption could exist since I've already tried to create a fresh template is in the style set. Those are a lot of styles to recreate from scratch. In CS5, the export to IDML "cleaned" whatever corruption there was in the file, but that doesn't seem to be working in CS6.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 26, 2012 5:08 AM   in reply to E Diane King

    One other thing to add. I'm sure you've noted that the text layout is fairly complex. I created an RTF template with styles for the writers of this project so that the text comes to me pre-formatted. If I strip all the formatting out, it's really difficult and time consuming to redo it. If the corruption is in the style sheet, I need to find some way to clean it up without losing the styling on hundreds of documents. I simply do not have the time to reformat from scratch all these files.

     

    The solution that we are considering at this point is getting the main editor InDesign and abandoning the InCopy workflow. It's only updating the stories that is causing the crash.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Nov 5, 2012 5:08 AM   in reply to John Hawkinson

    Well, I would suggest opening a support case at http://adobe.com/go/supportportal is always more effective than the anonymous "throw a wish in a well" approach ("don't ask and I'll never tell").

    ...
    You can email me the files and repro instructions.

    OK, I filed a case with Adobe a while back. This morning they report that this is now bug #3359371.

    At what point that may generate a fix is an open question.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 5, 2012 6:34 AM   in reply to John Hawkinson

    John, thanks for getting this bug noticed by Adobe. I really appreciate your help. I'll be extremely happy to see a fix in the future, but for now my editor has switched to InDesign, so we're still in production. I hope no one else's workflow is brought to a grinding halt by the bug.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 6:56 AM   in reply to E Diane King

    Things just got worse in my office. Before it was just my complicated layouts that were having problems, now the designer who works exclusively on our quarterly magazine in a IC workflow with three editors is having the exact same problem with much simpler layouts. One of the editors edits any of the stories, and when the designer tries to update the link, ID crashes. This workflow worked in CS6 for the last issue, so something has bugged out recently, maybe the last update to the program?

     

    Anyone else having problems or is just our office?

     

    [EDIT] Just spoke at length with the other designer and I misspoke above. This is the first magazine issue that the whole team is in CS6. They are also going to have to work around the IC issue by doing all their edits in InDesign. We need a fix ASAP!

     

    Message was edited by: E Diane King

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 11:24 AM   in reply to E Diane King

    E. Diane King -

     

    You are not alone. We have had this problem since CS3. In my experiences, any Indd. file that has anchored objects and interactivity causes crash and even corruption when exported and edited with IC.  

     

    I gave up on that workflow a long time ago and have created a mess of a new work flow that works more than it doesn't.

     

    On occasions when my document revisions are extensive enough that I cannot collect edits/comments by PDF, I will cross my fingers and export the stories into IC. I then wait for all changes to be made, then try to incorporate them back into ID flow as you would expect it to work. When that fails, and it does consistently, I end up having to open the stories in IC, collect and copy the entire story flow and paste it over the ID flow. It's not perfect, is a pain in the #$%, and it causes me to have to relink all anchored objects and rebuild all interactivity.

     

    I did post and ask bout these crashes on forums and with a paid Adobe tech case and was told it wasn't a problem with the software. Funny that.

     

    I do hope that Adobe takes note and figures out how to make the checkout/check in workflow with IC and ID actually work. Good luck to us all.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 11:51 AM   in reply to ETC steph

    I'm not sure it's the anchored objects at fault. They are in use in my files, but not in my co-workers. I'm beginning to suspect that it may be a style sheet corruption. IC doesn't even need to be involved to cause the crash, just the stories. I can output to a IC story, place the story in a blank document, check it out, check it in without making any kind of edit. If I go back to the original doc and update the links, ID crashes.

     

    In both my workflow and in my co-worker's workflow, we are using style sheets imported from pervious version ID files. I'm beginning to wonder if that isn't the issue. The only way to test it that I know of is to recreate the style sheets from scratch and I'm not even sure I can.

     

    If anyone has any tricks for rebuilding style sheets, I'd sure like some advice.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 11:57 AM   in reply to E Diane King

    E Diane King wrote:

    If anyone has any tricks for rebuilding style sheets, I'd sure like some advice.

    Try exporting the story to InDesign Tagged Text and import it into a new doc to clean the styles.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:04 PM   in reply to Peter Spier

    Peter Spier wrote:

     

    Try exporting the story to InDesign Tagged Text and import it into a new doc to clean the styles.

     

    Do you mean IDML? I don't see an option for Tagged Text.

    The IDML export does not fix this problem in CS6 . . .  that was one of the first things I tried because it worked in CS5.

     

    UGH! Nevermind this post. I found the export option. Will give this a try.

     

    Message was edited by: E Diane King

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:05 PM   in reply to E Diane King

    No, I meant tagged text. That option is only available when you have an active insertion point or text selected.

     

    If you have a selection, only that text is exported. For an inertion point, but no selction, the entire story is exported.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:32 PM   in reply to Peter Spier

    OK, so here is a question. Let's say I get a nice clean style sheet by way of exporting one of my documents to tagged text. Will importing that style sheet/or syncing the book's style sheet to that clean sheet clean all of them, or would I have to export every single story for all the documents in this particular workflow that is crashing ID (hundreds of files) and reimporting them into blank documents the only way to get a clean style sheet? I ask because exporting the stories strips out my anchored objects, which I would have to replace in every single file, so I don't believe this is a doable workaround if it works.

     

    I just tried importing the "cleaned" style sheet into one of the documents that is crashing, and it still crashes, so either I'm not really cleaning the style sheet by importing tagged text or the style sheet is not causing the crash.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:50 PM   in reply to E Diane King

    I honestly don't know the answer to that question. I suggested the tagged text because it often works for me for cleaning up text anomalies like TOCs that don't pick up styled paragraphs. I often place the tagged text back into the same file, sometimes directly replacing the current story, sometimes on the pasteboard and then copy/paste to replace the text.

     

    Can you isolate a single file/story to play with? I'd try importing the tagged text into a new file, then putting that and your test into anew book and synching and see what happens.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 1:00 PM   in reply to Peter Spier

    OK, I went and grabbed one of my co-workers files to work with. His style sheet is far cleaner and the layout far simpler than mine. Here is what I've done:

    1. I put a copy of his file locally on my computer and exported the main story to IC.
    2. I placed the IC doc in a blank file and checked it out and checked it back in. Went back to the original file and updated the linke. ID crashed.
    3. I recovered the file. Exported the main story to tagged text and deleted the link to IC.
    4. Placed the tagged text file into a blank document, and then saved that doc as test and exporeted the IC story as test.
    5. Placed the test IC story in yet another blank document, and checked it out and in. Returned to test document and updated the IC link with no trouble.
    6. Returned to the original document, placed the Test IC into the document and ID crashed.
    7. Recovered everything. Tried placing the Test IC without anything selected and then clicked into the text frame and managed to get it to flow into the story frames.
    8. I returned to my test document and edited the story.
    9. I returned to my original file and updated the IC link and ID crashed.

    Anybody see anything in all of that that could suggest a cause for the crash?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 1:10 PM   in reply to E Diane King

    As a follow up. I have fixed the file that my coworker gave me. After I posted my comment above, I went ahead and stripped the main article out again, deleted all the other IC links in the document, selected all unused in both style panels (character and paragraph) and deleted them, then I placed in the "clean" test IC doc into the story flow, and reexported all the other stories to IC. I placed the entire batch in another blank doc and checked them all out and back in, then returned to the original file and updated the entire set without a crash. Not exactly sure how I fixed his file, but it's working now.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 2:02 PM   in reply to E Diane King

    That sounds like either an unused style was the problem, or the tagged text export cleaned things up when you removed the "bad" story.

     

    Not a pleasant thought to have to export hundreds of stories...

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points