manager12

Filemaker Pro 12.0.5 won't launch anymore

Discussion created by manager12 on Mar 18, 2016
Latest reply on Sep 29, 2017 by monkeybreadsoftware

All of a sudden today Filemaker Pro 12.0.5 won't launch. I click on the application and it bounces once in the dock and then it quits itself an error message pops up that says "Filemaker Pro quit unexpectedly". It then shows a report that can be sent to Apple.

 

The weird thing is I last launched FileMaker about 2 days ago and it worked perfectly fine. I have not installed any OS updates or Filemaker updates since then. (nothing has changed). I was using the trial version of Filemaker 14 today but I have been able to open version 12 after I installed the trial of 14 and have used them interchangeably. (and no its not a problem of trying opening a new fmp.14 file in version 12.)

 

I've tried the normal rebooting the computer, etc and nothing has worked. I'm running Mac OS X 10.11.3.

 

Here's part of the error message I get:

 

Process:               FileMaker Pro [662]

Path:                  /Applications/FileMaker Pro 12/FileMaker Pro.app/Contents/MacOS/FileMaker Pro

Identifier:            com.filemaker.client.pro12

Version:               12.0.5 (12.0.5)

Code Type:             X86 (Native)

Parent Process:        ??? [1]

Responsible:           FileMaker Pro [662]

User ID:               501

 

 

Date/Time:             2016-03-18 16:33:10.928 -0400

OS Version:            Mac OS X 10.11.3 (15D21)

Report Version:        11

 

Time Awake Since Boot: 610 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)

Exception Codes:       0x0000000000000002, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:

*** Terminating app due to uncaught exception 'NSRangeException', reason: 'Cannot remove an observer <FMInspectorWindowController 0x10608a40> for the key path "areInspectorsVisible" from <FMInspectorManager 0xd5f81b0> because it is not registered as an observer.'

 

Any ideas what might be causing this issue?

Thanks!

Outcomes