InDesign crashes when updating image links

InDesign has crashed a few other times with the same error details I have below, but the easiest way to replicate it over and over is when I try to re-link images.
The module that keeps crashing is "TEXT.RPLN"
I thought it was a font at first, but have run Adobe's font validator and everything said it was fine.
I have replaced the "InDesign Defaults" and "InDesign SavedData" files and that didn't help either.
Any other thoughts on why InDesign could be crashing? 
It is becoming hard to get anything done, and I am thinking that I may just have to completely uninstall and then reinstall...
Windows Event Log Details:
Faulting application name: InDesign.exe, version: 8.0.2.413, time stamp: 0x51fb7197
Faulting module name: TEXT.RPLN, version: 8.0.2.413, time stamp: 0x51fb7469
Exception code: 0xc0000005
Fault offset: 0x00177388
Faulting process id: 0x1658
Faulting application start time: 0x01ced96ab5da87ca
Faulting application path: C:\Program Files (x86)\Adobe\Adobe InDesign CS6\InDesign.exe
Faulting module path: C:\Program Files (x86)\Adobe\Adobe InDesign CS6\Required\TEXT.RPLN
Report Id: c87cdb4a-455e-11e3-8205-0026833b2b0b

I did already replace the preference files.
It was actually happening on multiple InDesign installs on separate computers so I don't think it could have been preference related.
However, crossing my fingers, I think it is fixed now...
I created a copy of the original document and exported the .INDD document as a .IDML and re-opened/saved it as a new version.  By doing this, everything appears to be working now.  Don't know if it is just coincidence or if something in that process really fixed something.  I guess only time will tell.

Similar Messages

  • Indesign crashes when updating a linked document

    This is a reproducible crash.
    I have a indd file, several pages long with other embedded / placed indd documents inside.
    When a linked file in the original documents has been changed, I naturally get a notice in the "links" tab. So far so good.
    When I right-click and select "Edit original", the original document opens up and I get the usual notice if I like to update the changed link.
    I select yes and save the document and close it to get back to doc I started with and then Indesign crashes.
    Can this be fixed? It's extremely annoying.
    Tia.

    Sphynx25 I have the exact problem and have been dealing with it for a couple years now, it's incredibly annoying. I wonder if there's some preference that would eliminate the document from automatically checking the links?? Seems this is what causes the crashes. I fiddled with what I could find in the preferences to no avail.
    If you figure this one out please let me know, I'll do the same.
    - W

  • Indesign crashes when updating incopy assignments!

    Hi,
    I've read through some forums and it appears others are having this problem.
    When I open indesign and it says do you want to update links (referring to the incopy assignements) that need updated.
    I click ok, and Indesign crashes!!!!
    One thing I read could be the issue....
    - anchored objects, (incopy can't handle all the anchored objects)
    That is RIDICULOUS if that is the issue.  If so, Adobe should have had a disclaimer....don't buy incopy if you plan on having more than text in your document.
    There are no error messages that come up, the program just crashes.  I'm using Indesign CS5 version 7. 
    A solution I read was to save the indesign file that keeps crashing when updating the assignments as an .idml file.
    I tried this and it appeared to work, but what a joke!
    This is very unreliable and has caused a lot of stress.
    Anyone else have any solutions or can ADOBE come up with a solution???
    Thanks

    First question is are you fully patched to 7.0.4? If not, download and install that patch.
    Second: Do you have Suitcase Fusion 3 installed? If so, try disabling the autoactivation plugin.
    Bob

  • Indesign crashes when updating incopy content

    I'm having a lot of bother with (Mac) Indesign CS6 crashing when updating Incopy content. The problem first appeared after upgrading from CS4 to CS6 on OSX 10.6.8.
    I've since upgraded to Mountain Lion (10.8.2) and the problem still persists (with fully updated InDesign 8.01 and Incopy).
    Incopy is Windows version if that has any bearing on the issue.
    The crash occurs when opening an Indesign document with Incopy content that has been edited. I can open the document if I choose not to update content, but ID will subsequently crash if I choose to manually update the content from the assignments dialog. This doesn't happen with all my documents - perhaps about 1 in 4 with Incopy assignments.
    I can place the ICML files in a new Indesign document without incedent. In other words the ICML files don't appear to be corrupt.
    Suggestions anyone?
    Ian

    I got another crash.  This time just on trying to launch inDesign.
    Below is the report.  If anyone can help it would be very appreciated.
    Process:    
    Adobe InDesign CS6 [621]
    Path:       
    /Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
    Identifier: 
    com.adobe.InDesign
    Version:    
    8.0.1.406 (8010)
    Code Type:  
    X86 (Native)
    Parent Process:  launchd [172]
    User ID:    
    505
    Date/Time:  
    2013-02-14 13:25:08.237 -0500
    OS Version: 
    Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Interval Since Last Report:     
    3983 sec
    Crashes Since Last Report:      
    2
    Per-App Interval Since Last Report:  2270 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                 
    B8865CAA-B81B-3211-BACA-1F5C06EF8F47
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
    Exception Codes: 0x0000000000000001, 0x0000000000000000
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   PublicLib.dylib          
    0x016c5372 ProtectiveShutdown::~ProtectiveShutdown() + 278
    1   PublicLib.dylib          
    0x016c53f5 ProtectiveShutdown::~ProtectiveShutdown() + 17
    2   ObjectModelLib.dylib     
    0x016082d2 ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 28162
    3   ObjectModelLib.dylib     
    0x0160691c ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 21580
    4   ObjectModelLib.dylib     
    0x015f70c3 0x15d6000 + 135363
    5   ObjectModelLib.dylib     
    0x015f5742 0x15d6000 + 128834
    6   ObjectModelLib.dylib     
    0x0160566f ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 16799
    7   ObjectModelLib.dylib     
    0x016024ba ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 4074
    8   com.adobe.InDesign       
    0x00001dc2 main + 82
    9   com.adobe.InDesign       
    0x00001d55 start + 53
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib   
    0x942f49ae kevent + 10
    1   libdispatch.dylib        
    0x9a59ec71 _dispatch_mgr_invoke + 993
    2   libdispatch.dylib        
    0x9a59e7a9 _dispatch_mgr_thread + 53
    Thread 2:
    0   libsystem_kernel.dylib   
    0x942f38e2 __psynch_cvwait + 10
    1   libsystem_c.dylib        
    0x9374c289 _pthread_cond_wait + 938
    2   libsystem_c.dylib        
    0x9374c512 pthread_cond_timedwait_relative_np + 47
    3   com.apple.CoreServices.CarbonCore
    0x99e496ad TSWaitOnConditionTimedRelative + 177
    4   com.apple.CoreServices.CarbonCore
    0x99d95b9b MPWaitOnQueue + 261
    5   PMRuntime.dylib          
    0x005b9581 SetVSizeBaseline(unsigned long) + 1473
    6   com.apple.CoreServices.CarbonCore
    0x99e1ca7b PrivateMPEntryPoint + 68
    7   libsystem_c.dylib        
    0x93747557 _pthread_start + 344
    8   libsystem_c.dylib        
    0x93731cee thread_start + 34

  • InDesign crashing when updating associated InCopy files

    We just upgraded to CS6 and Creative Cloud. When graphic designers are using InDesign and writers update the affiliated InCopy files, when the designers hit the Update button to pull in the updates, it crashes InDesign. Here is Pastebin link of a recent crash log.
    http://pastebin.com/Luc13HET
    Designers are using Macs, writers are using PCs, we use DropBox to share the files, and re-placing the files seems to be ok, just not using the actual Update button. We've tried a ton of potential fixes, including resetting preferences, placing the file on to a new document, saving as IDML, exporting InCopy links separately.
    Anyone know of any fixes?

    This is the same for our department and the workflow sounds very similar except we are using Stand alone installs and not creative cloud with both design and editoiral using PCs.
    We have really experienced the problems when using previously designed templates from CS4 and are now having to go through systematcally and redo these from the ground up which seems to fix most but not all and is really annoying. Adobe of yet have not released a fix for this even thou there have been quite a few pastbin reports sent to them.
    CS6 using Indesign and Incopy is a real disappointment considering all the excellent features under the hood.
    See a long post here it might help
    http://forums.adobe.com/thread/671820?start=80&tstart=0

  • InDesign crashes when updating InCopy ICML files

    I created an assignment file with around 20 different stories. The next time I opened InDesign the writer had input text to most of the story files. One story file was a couple of pages of text, the rest were just a few lines of copy, nothing huge. Every time I tried to update the ICML files InDesign crashed. I didn't matter if I only tried updating one story or all of them, it always crashed. I was working on a PC when this happened. I moved over to my Mac to try and updated the ICML files and it crashed there too.
    The actual InCopy ICML files on the server were fine. The writer never realized there was a problem. All of the copy was sitting there, so I was able to go back and re-import all the copy.
    I did all the basic stuff to resolve the issue like restart, trash the prefs, convert to INX, and try on different computer. Nothing worked, crashed InDesign every time.
    I'm currently using CS5, but this same issue came up last year on another project in CS4 as well.
    Has anyone had this happen and/or know of a fix other than re-importing all the story files?

    Some might call me crazy, but in order to progress with my project I ended up having to create my own work around this crashing bug.
    The problem with my situation was that the reviewers had already made their comments in InCopy and it wasn't until I tried opening the .indd file and updating the stories that we received the crash... every time.
    My workaround - if the reviewers had made their comments in InCopy, hopefully with track changes enabled, in order to see their comments I did the following:
    I opened the .indd file in InDesign CS5.5 (version 7.5.2). DO NOT UPDATE the document with the ICML stories. Instead I unlinked the .icml stories from the main document. I then opened the .icml files in InCopy 5.5. I was able to see the edits that were made by my reviewers and copy and paste them between InCopy and InDesign at that point.
    I know, I know. This is totally a crazy thing to need to do when we have such a powerful tool (InDesign and InCopy). It comes down to, you must do what you must do to get the job done. I truly had no other option presented at the time. The project had to complete and the reviewers were not HAPPY to even think about reviewing the content again via PDF shared review.
    The best advice I received from other forum users when I proposed the crashing issue was that it could be because of anchored objects being deleted or moved by an InCopy editor. Because InCopy is strictly a text editing tool, there may be an issue that causes InDesign to get frustrated when an edit moves or deletes an anchored object or frame. I had lots of anchored object, interactive objects, etc. in my document. To track down whether an anchored object moved or was deleted by a user was unsurmountable... my workaround, while painful, at least got the job done this time.
    Any future projects will be moved back to CS4. That version atleast works with InCopy stories and Interactivity. I am sure one day this will be resolved... just wonder when.

  • Frame crashing when updating images

    I'm running FrameMaker 8 with the 8.0.2 patch on Windows XP.
    I am editing an image in that is a tiff in Frame with Illustrator. I will export my image as a tiff with the same file name so the tiff automatically updates in Frame. However, instead of updating, Frame crashes on me.
    Is there any way to prevent/fix this?

    Are both Illustrator and FrameMaker open when this happens? Why are
    you saving in TIFF format from Illustrator? You should try EPS instead
    (it supports rasters as well).

  • InDesign crash when updated from InCopy

    From 2007 to last week I have never had any issues with InDesign and InCopy. LOVE the way they work together.
    Upgraded to CS6 two weeks ago... Put one set of papers out last week with some odd things happeing where InDesign would update an InCopy edit and they seconds later it would be out of date again.
    Now this week all updates from InCopy crash InDesign.
    This is driving me crazy. I have started replacing content with InCopy files just to have them show up out of date... and any update crashes InDeisgn.
    I have no idea how I am going to get through this weeks paper.
    Any help out there???
    Thanks
    Chris
    Windows 7, one is brand new... all CS6 all fresh clean installs...

    OK... this is gettin worse.
    Now I cant place a PDF.
    I moved all files to my local computer, still haveing issues!
    Completely unacceptable!

  • Indesign crashes when placing a image

    When I try to place a image in Indesign CS6 or CC and even in Illustrator the program freezes with spinning wheel and i have to force quit program!!! The dialouge box does not even come up to enable me to pick a file!! Have spoken to Adobe and they are useless still waiting for them to phone me back!! Please can someone help as progam is un-usable as it is!!

    http://pastebin.com/R9QWYUxf
    does this help? i tried to the, chose View > Send Signal: Abort (SIGABRT) but everytime i try it Indesign crashes when i then reboot Indesign i can place a object?? but if i quit Indesign and try again does not work?
    what other info do you need? running on a macbook pro 10.9.1

  • InDesign crashes when scrolling/editing a corrupted page with a broken link.

    Just sharing a problem I had and how I solved it (with help from adobe tech support-thanks!).
    Indesign CC running on a Mac OSX 10.9.2
    PROBLEM:
    InDesign crashed when ever I reached a certain page in a large document I was working on. On that page was a link to an illustrator file. Somehow this file must have been corrupted, but there was no chance to edit or delete this link/page as the program crashed instantly when ever I tried to manipulated that specific page.
    SOLUTION:
    I opened a new, empty document; opened the broken file and moved all pages to the new document: LAYOUT/PAGES/MOVE PAGES; select Move Pages "ALL"; Move to: "Select the new document"; click OK. I went back to the new file with the moved pages saved it and deleted the corrupted link on that page which I could now edit again. Problem solved!
    Hope this is helpful for anyone who experience the same problem.

    Did you share in the program forum? InDesign
    This forum is about the Cloud as a delivery process, not about using individual programs
    If you start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

  • InDesign crash when place an image

    My InDesign crash when I try to place an image, that has never happend before?
    What is wrong?  (CS4)

    Win7 Pro
    InDesign CS4 6.0
    Error: InDesign CS4 has stop working, Windows try to find a solution.
    I take Ctrl + D, then when I take a picture from the disc, and press OK/place, the error cames up.
    I was possible to place one other picuture now, but it crash on several ones, never happend before.

  • InDesign crashes when syncing book with Hyperlinks in master

    Hi,
    I seem to have an issue with InDesign crashing when trying to sync a Book (INDB file) with page links (Hyperlinks) in the Master.
    Ref. Hyperlink panel > Edit Hyperlink > Link To: Page
    I've narrowed the crashing issue down to InDesign only crashing when the Style Source (containing the master with page links), tries to sync with another doc in the Book that uses the master in the Pages panel. Thus I do not get a crashing error if the doc does not contain the master in the Pages panel.
    For the pages that did not contain the master on the Pages panel I noticed that the Hyperlinks were labelled differently from the Style Source (ex. "hyperlink 1" from the Style Source would be "hyperlink 2" in the first document synced with it (assuming only one hyperlink present).
    If I remove the Hyperlinks (page links) from the master, the error no longer occurs for any of the pages.
    I put the links on the Page as opposed to the Master to test functionality and they work as expected. Although part of the reason for having the Master is these links appear exactly the same across multiple pages in the Book.
    I've tried to export all my pages as IDML files then re-save them as INDD files to no avail. Did the same to all the files as well with "Save As" which didn't do anything either. I then installed the latest patch I could find: Application Version 7.0.4.553 (See all InDesign Patches), which also did not work.
    Not sure if this is a bug or if what I'm trying to accomplish should be done differently.
    The links in the Master need to link to the first page of select docs in the Book. Similar functionality to how a rendered table of contents would behave.
    Ref. Layout > Table of Contents...

    I had the same problem, and it turns out that the problem is having the same file into different folders. For example I had an MP4 in iTunes, and the same file in the photos folder that was being updated to the iPad. So I just removed one file and it syncs perfectly.

  • Indesign crashes when placing pdf created in Xinet Fullpress.

    Indesign crashes when placing a pdf from Xinet Fullpress. Xinet thinks the problem is in inDesign.
    What to do?
    The pdf files works fine in acrobat and apple preview.

    Hi Peter, here is the link to the crashreport:
    http://pastebin.com/xzpp717i
    If you need the a test file that crashes, please download it on the attached link below.
    regard Martin
    Xinet pdf crash
    Hi, click on the link to download
    Tue Sep 18 2012, 15:47:53

  • Indesign crashes when I try and open my document

    I created a file in Indesign which represents many days of work.
    It crashed indesign when I was pdf'ing the document and now it crashes indesign every time I try to open it.
    It is my only version.
    I have tried many ways to open it but nothing has worked - can you help?
    I've just realised that now - Indesign crashes when I try and open any document!
    Thanks very much
    NB Someone suggested I send it to Adobe and they may be able to fix it, but I can't find a contact email to send it to.

    You need to empty the InDesign Recovery folder (which is hidden in your user profile/library). You can find the path to InDesign SavedData in this link: Replace Your Preferences  and the recovery folder should be in the same folder with the InDesign SavedData file.
    Once the recovery folder is empty you should be able to launch ID, then try opening the file. If it wasn't damaged while writing it back to disk it will be fine, in the last previously saved state.

  • Crash when updating site cache?  MM_Username1?

    Hi,
    All of a sudden, tonight, DW8.0.2 will no longer open or load
    one of my
    sites, crashing when "Updating Site Cache". The site is ASP
    linked to an SQL
    database.
    Checking the file that the cache gets to, I notice that the
    problem file is
    within a sub-directory of the site, called "/admin". Thing is
    though, it's
    not always the same file, but it IS always a file within the
    /admin
    sub-directory.
    Within this sub-directory I altered, by hand, the Login User
    code and
    Restrict Access to Page code to create and use the session
    variable
    MM_Username1 as opposed to the default MM_Username.
    Could this be the reason for the sudden trouble with the site
    cache? I am
    puzzled because the site was working fine for a few weeks
    now, with this
    sub-directory included, and I didn't create the MM_Username1
    issue today
    either, it has also been working fine for a good few weeks
    now. I've also
    not added anything new to the site, that I am aware of.
    When I remove the sub-directory from the site, the Updating
    Site Cache works
    fine, so I am 100% sure there is a problem with the files
    within this
    sub-directory. How will I know which one though?
    I've tried this, as recommended by Adobe, but I still get a
    freeze-up when
    re-creating the cache:
    1. Try renaming the Dreamweaver user configuration folder, so
    that
    Dreamweaver will automatically generate a new user
    configuration folder the
    next time Dreamweaver launches. The Configuration folder is
    located here:
    C:\Documents and Settings\<username>\Application
    Data\Macromedia\Dreamweaver
    8\Configuration
    2. Recreate your Dreamweaver user settings in the registry as
    follows:
    Launch the Registry Editor by clicking the Start button,
    choose Run, then
    type "regedit". In the Registry Editor, navigate to this
    folder:
    HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
    Rename the "Dreamweaver 8" key to "DreamweaverOLD", so that
    Dreamweaver will
    automatically generate a new user settings key the next time
    you launch it.
    3. Recreate your Dreamweaver site definitions in the registry
    as follows.
    The steps below will delete your site definitions in
    Dreamweaver.
    4. Launch the Registry Editor by clicking the Start button,
    choose Run, then
    type "regedit". In the Registry Editor, navigate to this
    folder:
    HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
    Rename the "Sites" key to "SitesOLD", so that Dreamweaver
    will automatically
    generate a new Sites key the next time you launch it.
    Any further advice?
    Regards
    nath.

    Found it! Jeesh.
    I had a querystring value in my UPDATE redirect URL which was
    coded
    incorrectly!!!
    I am frustrated that, rather than just highlighting the error
    or, at the
    very least, producing an error when opening the specific
    file, this type of
    thing crashed the entire DW programme.
    The time I spent in Notepad today changing MM_Username1 back
    to
    MM_Username!! Turns out that was nothing to do with it.
    <groan> Yeah,
    that's right, laugh it up! :o)
    Anyway, solved now. A misplaced ", %, ), (, <, >, &
    etc can cause you no
    end of grief! :o(
    Nath.
    "tradmusic.com" <[email protected]> wrote in
    message
    news:[email protected]...
    > Hi,
    > All of a sudden, tonight, DW8.0.2 will no longer open or
    load one of my
    > sites, crashing when "Updating Site Cache". The site is
    ASP linked to an
    > SQL database.
    > Checking the file that the cache gets to, I notice that
    the problem file
    > is within a sub-directory of the site, called "/admin".
    Thing is though,
    > it's not always the same file, but it IS always a file
    within the /admin
    > sub-directory.
    >
    > Within this sub-directory I altered, by hand, the Login
    User code and
    > Restrict Access to Page code to create and use the
    session variable
    > MM_Username1 as opposed to the default MM_Username.
    > Could this be the reason for the sudden trouble with the
    site cache? I
    > am puzzled because the site was working fine for a few
    weeks now, with
    > this sub-directory included, and I didn't create the
    MM_Username1 issue
    > today either, it has also been working fine for a good
    few weeks now.
    > I've also not added anything new to the site, that I am
    aware of.
    >
    > When I remove the sub-directory from the site, the
    Updating Site Cache
    > works fine, so I am 100% sure there is a problem with
    the files within
    > this sub-directory. How will I know which one though?
    >
    > I've tried this, as recommended by Adobe, but I still
    get a freeze-up when
    > re-creating the cache:
    >
    > 1. Try renaming the Dreamweaver user configuration
    folder, so that
    > Dreamweaver will automatically generate a new user
    configuration folder
    > the next time Dreamweaver launches. The Configuration
    folder is located
    > here: C:\Documents and
    Settings\<username>\Application
    > Data\Macromedia\Dreamweaver 8\Configuration
    >
    > 2. Recreate your Dreamweaver user settings in the
    registry as follows:
    >
    > Launch the Registry Editor by clicking the Start button,
    choose Run, then
    > type "regedit". In the Registry Editor, navigate to this
    folder:
    > HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
    > Rename the "Dreamweaver 8" key to "DreamweaverOLD", so
    that Dreamweaver
    > will automatically generate a new user settings key the
    next time you
    > launch it.
    >
    > 3. Recreate your Dreamweaver site definitions in the
    registry as follows.
    > The steps below will delete your site definitions in
    Dreamweaver.
    >
    > 4. Launch the Registry Editor by clicking the Start
    button, choose Run,
    > then type "regedit". In the Registry Editor, navigate to
    this folder:
    >
    > HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
    >
    > Rename the "Sites" key to "SitesOLD", so that
    Dreamweaver will
    > automatically generate a new Sites key the next time you
    launch it.
    >
    > Any further advice?
    > Regards
    > nath.
    >

Maybe you are looking for