Illustrator & Indesign CC (Windows) crashes when trying to open an new/existing document

I installed Illusrator & Indesign CC when they were released as I had a pre-existing Adobe CC account which I had previously downloaded Photoshop and Indesign CS6 with. When I try to use Indesign & Illustrator CC they both crash when you go to open a new / existing document. I also downloaded Photoshop CC and this works fine. I have phoned Adobe 6 times to try to resolve the issue, each time I wait on hold for an hour and they get told they will call back within 2-5 hours but this never happens.
Has anyone else had this issue since installing CC and found a way to resolve it?

Are Tahoma and Verdana fonts installed on your system?

Similar Messages

InDesign CS5.5 crashes when trying to open ANY CS5.5 document

I am using InDesign CS5.5 and can't open any of my InDesign CS5.5 documents. The message "InDesign has stopped working" appears.
Even when trying to create a new document, again the message "Adobe InDesign CS5.5 has stopped working" - close programme.
InDesign was working perfectly on Friday. Saved and exported a file to pdf, all okay.
Are you able to help.

Hi Peter
I uninstalled the whole CS5.5, downloaded and ran the cleaning thing, reinstalled the whole suite but it came up with the message that the install had errors … every other module worked except Indesign which still did the same thing .. it would open, but not an existing or new doc … below is the error log
Did everything again.. same result
did it again but this time also deleted every folder with reference to 5.5 and cleaned the registry .. same result
finally, I did it all again, but this time did NOT install Fireworks (because of the error log below), 32bit Photoshop, Flash or the Apple support thingy .. and it now works !!
so it seems there is a problem with one or more of the above … was there an update around 24-26 May ??
Interestingly there's no icon against the Indesign program menu listing (but it still works) but the icon is still shown against all the 'indd' files
We rang support about 4 hours ago, they couldn't help but were going to look into it and get back to us 'within the hour' … needless to say they didn’t .. hope this 'work around' goes onto the blog and helps others
regards
Bruce
Exit Code: 6

Invisible windows appears when trying to open a new window. These windows are listed in the Window list, but I cannot switch to them or close them. This also occurs when I try to "View Source". This was not a problem prior to my 6.0 upgrade.

I cannot open a new window for FireFox.
Invisible windows appears when trying to open a new window. These windows are listed in the Window list on the menu, but I cannot switch to them or close them. This also occurs when I try to "View Source". This was not a problem prior to my 6.0 upgrade.
The Downloads Window cannot be accessed either.
This is very annoying. Is this a bug? Or is there a fix.

If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

Finder crashes when trying to open a new window

When trying to open a new Finder window, Finder will crash and relaunch but won't open an actual new window. Neither can I use the Go To Folder menu.
I tried relaunching Finder, restarting my MacBook and repairing my disk. Unfortunately, nothing has helped so far..
Any ideas?
Small addition: I first noticed the problem while trying to open a DMG file. I don't have any reason to suspect this file is malicious though.

I faced the exact same problem.
Please check How to activate an event handler manually? Read the COMPLETE thread... especially the second last entry. Valery has given a perfect workaround for this problem.
And it works absolutely fine too !
regards,
Navneet.

Iphoto crashes when trying to open with the existing db

Hi there,
iPhoto keeps crashing when i try to launch it with the existing db. I can open it with a new db but am not sure how I can get the old one working.
I love using iPhoto with all the events, faces and other features. Is there a way to get all them back?
Thank you in advance
Here is the crash log:
Process:         iPhoto [270]
Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:      com.apple.iPhoto
Version:         9.4.3 (9.4.3)
Build Info:      iPhotoProject-720091000000000~1
App Item ID:     408981381
App External ID: 15017489
Code Type:       X86 (Native)
Parent Process: launchd [123]
User ID:         501
Date/Time:       2013-08-30 17:40:29.477 +0300
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report:          223 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report: 8 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      14DBC6AD-2C67-87D4-F3EB-208F45A7B3D8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
Application Specific Backtrace 1:
0   CoreFoundation                      0x921a0e8b __raiseError + 219
1   libobjc.A.dylib                     0x95c5a52e objc_exception_throw + 230
2   CoreFoundation                      0x920ac07b -[__NSArrayM insertObject:atIndex:] + 299
3   CoreFoundation                      0x920abf40 -[__NSArrayM addObject:] + 64
4   iPhoto                              0x00069858 iPhoto + 256088
5   iPhoto                              0x00350d0c iPhoto + 3300620
6   iPhoto                              0x0026065c iPhoto + 2315868
7   libdispatch.dylib                   0x982f1cb1 _dispatch_barrier_sync_f_slow_invoke + 80
8   libdispatch.dylib                   0x982ebc82 _dispatch_client_callout + 46
9   libdispatch.dylib                   0x982f12e3 _dispatch_main_queue_callback_4CF + 223
10 CoreFoundation                      0x9209cc29 __CFRunLoopRun + 1961
11 CoreFoundation                      0x9209c01a CFRunLoopRunSpecific + 378
12 CoreFoundation                      0x9209be8b CFRunLoopRunInMode + 123
13 HIToolbox                           0x92a48f5a RunCurrentEventLoopInMode + 242
14 HIToolbox                           0x92a48cc9 ReceiveNextEventCommon + 374
15 HIToolbox                           0x92a48b44 BlockUntilNextEventMatchingListInMode + 88
16 AppKit                              0x997c993a _DPSNextEvent + 724
17 AppKit                              0x997c916c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
18 AppKit                              0x997bf5cc -[NSApplication run] + 855
19 AppKit                              0x997625f6 NSApplicationMain + 1053
20 iPhoto                              0x0003b0b9 iPhoto + 65721
21 iPhoto                              0x0003a705 iPhoto + 63237
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation                0x921a16a7 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 7
1   libobjc.A.dylib                         0x95c5a52e objc_exception_throw + 230
2   com.apple.CoreFoundation                0x920ac07b -[__NSArrayM insertObject:atIndex:] + 299
3   com.apple.CoreFoundation                0x920abf40 -[__NSArrayM addObject:] + 64
4   com.apple.iPhoto                        0x00069858 0x2b000 + 256088
5   com.apple.iPhoto                        0x00350d0c 0x2b000 + 3300620
6   com.apple.iPhoto                        0x0026065c 0x2b000 + 2315868
7   libdispatch.dylib                       0x982f1cb1 _dispatch_barrier_sync_f_slow_invoke + 80
8   libdispatch.dylib                       0x982ebc82 _dispatch_client_callout + 46
9   libdispatch.dylib                       0x982f12e3 _dispatch_main_queue_callback_4CF + 223
10 com.apple.CoreFoundation                0x9209cc29 __CFRunLoopRun + 1961
11 com.apple.CoreFoundation                0x9209c01a CFRunLoopRunSpecific + 378
12 com.apple.CoreFoundation                0x9209be8b CFRunLoopRunInMode + 123
13 com.apple.HIToolbox                     0x92a48f5a RunCurrentEventLoopInMode + 242
14 com.apple.HIToolbox                     0x92a48cc9 ReceiveNextEventCommon + 374
15 com.apple.HIToolbox                     0x92a48b44 BlockUntilNextEventMatchingListInMode + 88
16 com.apple.AppKit                        0x997c993a _DPSNextEvent + 724
17 com.apple.AppKit                        0x997c916c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
18 com.apple.AppKit                        0x997bf5cc -[NSApplication run] + 855
19 com.apple.AppKit                        0x997625f6 NSApplicationMain + 1053
20 com.apple.iPhoto                        0x0003b0b9 0x2b000 + 65721
21 com.apple.iPhoto                        0x0003a705 0x2b000 + 63237
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x9496c9ae kevent + 10
1   libdispatch.dylib                       0x982eec71 _dispatch_mgr_invoke + 993
2   libdispatch.dylib                       0x982ee7a9 _dispatch_mgr_thread + 53
Thread 2:: Dispatch queue: com.apple.root.default-priority
0   libsystem_kernel.dylib                  0x9496980e semaphore_wait_trap + 10
1   libdispatch.dylib                       0x982f0e70 _dispatch_thread_semaphore_wait + 25
2   libdispatch.dylib                       0x982f0ccc _dispatch_barrier_sync_f_slow + 149
3   libdispatch.dylib                       0x982ed3fb dispatch_barrier_sync_f + 37
4   libdispatch.dylib                       0x982f1c5a _dispatch_sync_slow + 70
5   com.apple.iPhoto                        0x002605fc 0x2b000 + 2315772
6   com.apple.Foundation                    0x913c9f27 -[NSBlockOperation main] + 188
7   com.apple.Foundation                    0x9139d259 -[__NSOperationInternal start] + 740
8   com.apple.Foundation                    0x9139cf64 -[NSOperation start] + 67
9   com.apple.Foundation                    0x913a5039 __block_global_6 + 135
10 libdispatch.dylib                       0x982eff8f _dispatch_call_block_and_release + 15
11 libdispatch.dylib                       0x982ebc82 _dispatch_client_callout + 46
12 libdispatch.dylib                       0x982ecf02 _dispatch_worker_thread2 + 285
13 libsystem_c.dylib                       0x995c0e72 _pthread_wqthread + 441
14 libsystem_c.dylib                       0x995a8d2a start_wqthread + 30

Here's how to repair your iPhoto database.
How to Rebuild/Repair an iPhoto Library.

InDesign CS5 keeps crashing when trying to open (windows 7)

I have the master suite collection and have no issues with the other programs. I don't use InDesign as much as some of the other programs, but now I am trying to use it, and it will not open. The purple box comes up saying that it is initializing, then I get RunTime Error! Program: C... This application has requested the Runtime to terminate in an unusual way. After reading a few posts on the forums I tried to update with the 7.0.4 patch, however, this has done nothing for me. I would reinstall but my Adobe account is no longer showing my download info for my purchase.

Are you sure you've logged in with the same ID? YOu might call customer service and see if they can find the order, too.
As far as fixing what's wrong, it does sound like a bad install. You could try running the installer again without uninstalling first, and it might recognize the existing serial number (select repair in the installer), but the odss of it actually working are about 50/50 at best, I think.

InDesign CS5.5 crashes when trying to open or create files on Yosemite

Hi,
I've just recently migrated to a new iMac running Yosemite. Photoshop CS5.1, Illustrator 5.1 and Bridge 5.1 are working fine but I'm having major issues with InDesign CS5.5. Every time I try to open an existing file or create a new one the programme freezes and I have to force quit.
I've trawled the forums and have done everything mentioned including uninstalling/reinstalling, removing temporary cache files and preferences, removing Data Store, deleting the Adobe font list, and removing the SING component.
I ran Activity Monitor and have uploaded the details to Sample of InDesign - Pastebin.com and the Crash Report to http://pastebin.com/KdEEWadj
Please help, I'm getting desperate!
Thanks,
Dan

CS5.x is not compatible to Yosemite. It may or may not run, if it does never without problems.
Adobe applications should never be installed via migration. It is always making problems in the long run. If you have done so, deinstall them immediately, run Adobe's Creative Cloud Cleaner Tool (available on Adobe's Website) and install any application from it original installer.
I recommend to upgrade to a CC subscription. CS6 might also work, but it is now very old and 2 to 3 versions after CS6 have been released. If you get a new system upgrade it is NOT guaranteed that it will work as CS6 is now at the end if not out of its product life cycle.

Office Word 2008 crashes when trying to open a local stored document ONLY if network connection is down

Sorry to bother you all but I have a situation I can't find a solution for:
on a MBP 2009, running Mac OS X 10.6.8 and MS Office 2008 (up to date), if I open a local stored document AND the unit is connected to the network everything works fine.
As soon as I switch off the network connection and I open a local stored document Word freezes and within "Force quit..." I can see that Word is no longer responding. A few minutes later OS X quits Word and that's it.
I already checked Safe boot, removing the Microsoft plist's and reinstalling MS Office 2008 including all available updates but the situation is still the same.
Any ideas?
Thanks in advance
Robert

Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
Isolating an issue by using another user account

Itunes crashes when trying to open the devices preferences

itunes crashes when trying to open the devices preferences. I use Mac osX 10.7.3 and iPhone 4s. The iPhone (and iPad) syncs via WLAN but when i try to open the iPhones/iPad Preferences in iTunes iTunes crashes. Any Idea?

Hi there AlexHB123,
You may find the troubleshooting steps in the article below helpful.
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
http://support.apple.com/kb/ts1717
-Griff W.

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
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.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Since the os7 update on my iPad, my safari is not right, it only opens one page at a time, crashes when trying to open more, it has no back button. Help

Since the os7 update on my iPad, my safari is not right, it only opens one page at a time, crashes when trying to open more, it has no back button. Help

Well, I rebuilt the entire workbook... that was a few months ago and so far, the problem hasn't resurfaced. It really wasn't fun to do, but whatever glitch there was in the file, I eliminated it.
I think I should mention that I am using Office v.X, NOT Office 2004. I got a new Intel iMac this week and yesterday when I opened up my files, it opened up the test drive (a JOKE of a program if you ask me) Anyway, some of the very minor issues I had with Office v.X were solved in the 2004 version. (When opening up large multi worksheet files without Excel being already opened, the tabs have white text) Anyway, I am still going to wait for the universal version to come out, but it seems that the newer versions may have fewer glitches (as is to be expected)
At any rate, best of luck to you!

Crashing when trying to open a project / forgetting where media files are

I spent all day manually locating hundreds of missing 'offline media' in a project, saving as I went. Premier Elements crashed when this was complete, now I try to open the project after rebooting and it either cannot find them again or crashes when trying to open the project. Anyone got any clues as to how I can fix this?

alex peatfield
What version of Premiere Elements are you using and on what computer operating system is it running?
How long has this issue existed?
Are you moving, deleting, renaming files and folders that go into a project after the project has been saved closed?
If you have source media stored on an external hard drive, determine if the external hard drive is malfunctioning, including if its drive letter
changing.
Lots of drill questions...
a. Running the program from a User Account with Administrative Privileges?
b. Latest version of QuickTime installed on your computer?
c. What are your computer resources and is your computer optimized?
d. What are the properties of your source media that are involved in this issue?
e. Where are the Scratch Disks directed and how much free hard drive space is at those locations?
f. Do the problems exist with and without the antivirus and firewall(s) disabled?
Let us start here and then we can decide what next.
Thanks.
ATR

Why does MainStage 2.2.1 crash when trying to open?

Why does MainStage 2.2.1 crash when trying to open?
It does not respond.

Contact this address below and request a new download, and that the one you have does not open or it crash whe doing so.
They open up my account and allowed me to reinstall.
My redowndloaded Mainstage is now working on my MacB Pro, and four [4] externals, with out any problems.
Hope this will help others, who are having a problem with Mainstage v 2.2.1
See below;
iTunes Store <[email protected]>

Freeze or stall when trying to open a new internet page

My Mac has started to freeze or stall when trying to open a new page. It seems to have gotten worse lately. Is it being caused by my internet provider or something in the Mac?

Which browser & version are you using? If Safari, post in their forum area. If 3rd party, post in their forums on their website.
Call your ISP to determine if the issue is on their end.
It is very difficult to offer troubleshooting suggestions when the "os version" you are using is unknown as each os has their own troubleshooting solutions.
Please complete your system profile.

InCopy Crashes when trying to open InDesign file.

InCopy just spins when trying to open an Indesign file and will eventualy cause InCopy to crash. When InCopy is then reopened the file will be recovered but the only tab available is layout view, both story view and gallery view are missing. The editor needs story view to make corrections.
The designer sets up the file with InDesign CS6 v. 8.0.1 on a mac w/osx v.10.7.5 the editor was using InCopy CS6 v.8.0.1 but has received new hardware and is on v8.0.2 windows 7. One of our Editors does receive this message Adobe InDesign is missing required files, Please reinstall.
We have upgraded editors hardware to allow more resorces.
Please advise what may be the cause.

Why would one of your editors receive a message about "Adobe InDesign is missing required files, please reinstall"? Aren't they using InCopy (not InDesign)?
Re the InCopy crashes, it sounds like the INDD file might be damaged. You can test this by having the InDesign user create a new test document and export one story to the workflow. See if the InCopy user can open that INDD file over the network, check out the test story, make a change, save it, check it back in, and then the InDesign user update the story on their end.
AM

Illustrator & Indesign CC (Windows) crashes when trying to open an new/existing document

Similar Messages

Maybe you are looking for