1 2 3 4 Previous Next 54 Replies Latest reply on May 3, 2017 7:47 AM by TSGal

    Unknown errors after  Progress backup is activated in FileMaker Server 13

    Michael Leung

      Summary

      Unknown errors after  Progress backup is activated in FileMaker Server 13

      Product

      FileMaker Server

      Version

      13

      Operating system version

      Mac OSX 10.9

      Description of the issue

      FileMaker Server always sends out error messages and we don't know what's happened and how to solve the issues.

      Steps to reproduce the problem

      Activate progressive backup in FileMaker Server.

      Expected result

      No error message.

      Actual result

      FileMaker Server always sends out error messages.

      Exact text of any error message(s) that appear

      Error Message 1 :

      FileMaker Server 13.0v1 on M******* reported the following event:

      2014-08-07 23:24:56.917 +0800   Error   808     M*******  Unable to read backup log. To free disk space, manually delete "filemac:/Data/Progressive Backups/Removed_by_FMS/***_Data1185842495_49332.fxl". (10709)

      FileMaker Server automatically sent you this email.  Contact the administrator if you no longer want to receive these notifications:
      Contact information not specified.

      ======   End  =========

      Error Message 2 :

      FileMaker Server 13.0v1 on M******* reported the following event:

      2014-08-07 23:24:56.876 +0800   Error   799     M*******  Unable to apply changes from backup log "filemac:/Data/Progressive Backups/Changes_FMS/Interval_63543020995728643/***_Data1185842495_49332.fxl". Progressive backup for database "***_Data1" is disabled. (10705)

      FileMaker Server automatically sent you this email.  Contact the administrator if you no longer want to receive these notifications:
      Contact information not specified.

      ======   End  =========

      Workaround

      Reactivate progressive backup in FileMaker Server again and again.

        • 1. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
          TSGal

               Michael Leung:

               Thank you for your post.

               Our Development and Testing departments are aware of this infrequent error during progressive backups.

               How often are the progressive backups run?

               How frequent do these error messages appear (799 followed by 808)?

               I see you "reactivate" the progressive backups.  Have you rebooted the server?  If so, have you noticed any difference in frequency?

               Any other information you can provide may be helpful.

               TSGal
               FileMaker, Inc.

          • 2. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
            philmodjunk
                 

                      Our Development and Testing departments are aware of this infrequent error during progressive backups.

                 Is it a real error indicating a problem with the system or the back up or a spurious error to be ignored?

            • 3. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
              TSGal

                   PhilModJunk:

                   This issue was found internally by one of our testers.  The notes are a little cryptic, but it appears the database server is able to detect the error, creates a new copy of the database and restarts progressive backup for it.  So, there may be a small time with no progressive backup.  This issue has occurred twice on the database that Testing and Development uses to track issues.

                   TSGal
                   FileMaker, Inc.

              • 4. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                philmodjunk

                     Makes one wonder if HardDrive issues might result in more frequent cases of this situation.

                • 5. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                  philmodjunk

                       An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.

                  • 6. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                    fmarker

                    I also have seen these "Unable to apply changes from backup log " and  "Unable to read backup log" errors on the same database twice in the last 6 days. FMServer Error 799 occurs first, then FMServer Error 808 occurs twice immediately after.

                    FMS 13v4 running on Windows 2008 R2 SP1 server in VMware environment.

                     

                    • 7. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                      TSGal

                      Fred Marker:

                      Thank you for your post.

                      I have also attached your post to the original report.  The latest notes show this is a temporary error, as it actually notifies the server to make a new progressive backup, so the user may be without a progressive backup for one iteration.

                      TSGal
                      FileMaker, Inc.

                      • 8. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                        levinr_1

                        We are running Filemaker 12. Our server hung this afternoon. The only recourse was to reboot the server. It reported  this error in the event long on the server:

                        Unable to read backup log. To free disk space, manually delete "filewin:/e:/XXXXXXX/Changes_FMS/Interval_63546660869229000/XXXXX21034366_407192.fxl". (20402)

                        The XXXs are to mask the file names.

                        We are running server version 12.3.0.327

                        Any thoughts on how what the problem might be?

                        • 9. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                          TSGal

                          levinr:

                          Thank you for your post.

                          The main issue here is determining why the server hung.  How many clients were connected?  What were the clients doing?  Were any new actions taken on the server (operating system update, java update, etc.)?

                          If the server hung during the backup process, the error you reported would be normal. After restarting the server and FileMaker Server, manually remove the file, start a new backup, and see if the issue returns.

                          TSGal
                          FileMaker, Inc.

                          • 10. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                            levinr_1

                            This is a recurring, but intermittent problem. We have had a half a dozen hangs like this in the last 12 months. In this instance the host server was up and completely idle. There were no operations going on on the server other than the FileMaker Server. We had about 70 clients connected at the time, which is high for us. Our procedure when this happens has been:

                                   
                            1. Close the databases
                            2.      
                            3. Stop the web and database services. The java console will show them as being closed, but if we exit the console and restart it, it will show the Web services stopped, but the database as closing.
                            4.      
                            5. Reboot the server.
                            6.      
                            7. Start the database and web services.

                            This has cleared the problem so far, but it will return.

                            Rod.

                            • 11. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                              TSGal

                              levinr:

                              Thank you for the additional information.

                              I need some clarification.  You said "the host server was up and completely idle", and then you said "we had about 70 clients connected at the time".   Did you mean there were 70 clients connected but no schedules running?  Or, were the 70 clients connected but not actively making changes to data?  Or...?

                              The procedure you are following after the crash is sound.

                              Have you looked at the log files?  System log?  What are the last few entries in the Event log prior to the hang?

                              TSGal
                              FileMaker, Inc.

                              • 12. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                                levinr_1

                                Follow-up

                                70 clients connected. Schedules were active. Did not note if any were running. The clients were frozen. They could not complete any action in FileMaker. The task manager on the FileMaker DB Server looked normal. There was a lot of RAM allocated (~6GB of 16GB) We normally sit at 4-5GB in use. The CPU was 99% idle.

                                Looking in the log, the clients were being disconnected because of the server shut down or time-out. There were many messages similar to this:

                                Client "XXXXX(XXXX-tech-1) [10.0.1.88]" no longer responding; connection closed. (10)

                                Just before this, tied to shutting down the database or web services:

                                Faulting application name: fmscwpc.exe, version: 1.0.0.1, time stamp: 0x505bae84
                                Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
                                Exception code: 0xc0000005
                                Fault offset: 0x000000000004e4e4
                                Faulting process id: 0x12e0
                                Faulting application start time: 0x01cfb6302e1890ac
                                Faulting application path: C:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\fmscwpc.exe
                                Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
                                Report Id: b71ffd85-3f5f-11e4-9e1e-90b11c17eb77

                                Before this, there is nothing noteworthy in the application or system log.

                                Rod.

                                • 13. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                                  TSGal

                                  levinr:

                                  Thank you for the clarification and additional information.

                                  If all 70 clients went dead, then it definitely points to the server; either FileMaker Server, the server, or connection to the server.

                                  On the server, do you have any other software running?  For instance, some users may have antivirus software.  Make sure this is turned off/disabled.

                                  If you have any third-party automatic backup software, make sure it is not backing up the FileMaker Server directories, as this would interfere with FileMaker Server and possibly backup database files that are open.

                                  Anything else you can provide may be helpful.

                                  TSGal
                                  FileMaker, Inc.

                                  • 14. Re: Unknown errors after  Progress backup is activated in FileMaker Server 13
                                    levinr_1

                                    There is no Anti-Virus on the Database Server. Clients are using Webroot for AV. Backups are done by backing up the backup directories created by Scheduled backup scripts and progressive backups. They are on a separate physical drive on the FileMaker server. They are backed up to our NAS. We do not backup the live database files.

                                    1 2 3 4 Previous Next