2 Replies Latest reply on Jan 18, 2012 11:51 AM by philmodjunk

    Faulting

    BakerD

      Summary

      Faulting

      Product

      FileMaker Pro

      Version

      11.0v3 Advanced

      Operating system version

      server 2008

      Description of the issue

      Application Hang followed by crash

      Steps to reproduce the problem

      Changing calculation in field

      Expected result

      Not crash

      Actual result

      Crash

      Exact text of any error message(s) that appear

      None Following from event viewer:
      - System
        - Provider
         [ Name]  Windows Error Reporting 
        - EventID 1001
         [ Qualifiers]  0
         Level 4 
         Task 0 
         Keywords 0x80000000000000 
        - TimeCreated
         [ SystemTime]  2012-01-18T06:21:11.000000000Z 
         EventRecordID 4925 
         Channel Application
         Computer NBFF-MS.NBFF.nbff.com 
         Security
      - EventData    
         0
         AppHangTransient
         Not available
         0
         FileMaker Pro Advanced.exe
         11.0.3.312
         4d3f6749
         unknown
         unknown
         unknown
         unknown    
         0
         9c9c072b-419c-11e1-84ab-d067e5e6698a
         1

      Configuration information

      OS completely up to date

      Workaround

      Wait until license restriction times out and restart

        • 1. Re: Faulting
          hschlossberg

          It would be helpful to see the calc you are changing when it crashes.  or is it crashing whenever changing ALL calcs?  And this is in a calc field definition? Or in the data viewer (FM Pro Advanced)?

          • 2. Re: Faulting
            philmodjunk

            And if you create a brand new, simple test field and repeat this process, do you get a crash?

            If you don't get this crash on a new file, it may be that your current file is damaged. Try recovering it and test the recovered copy to see if you get the same problem with it.

            Things to keep in mind about Recover:

            1. Recover does not detect all problems
            2. Recover doesn't always fix all problems correctly
            3. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.