0 Replies Latest reply on Nov 10, 2012 6:57 AM by JohnDuncan

    Upload of database to server fails with encrypted external containers

    JohnDuncan

      Summary

      Upload of database to server fails with encrypted external containers

      Product

      FileMaker Server

      Version

      12.0v2

      Operating system version

      MacOS-X 10.8.2

      Description of the issue

      When using the FileMaker Server Admin Console to upload a database and its associated encrypted external containers for hosting the process fails with a loss of communication between the FMS Admin Console and FMS.

      Steps to reproduce the problem

      The database used has about 64,000 records.  59,280 them are broken links to files that were previously stored by reference.  5,031 reference encrypted externally-stored files.  After verifying that the path to the external files is valid by looking at the containers in the database the database was closed (FileMaker Pro not running) and attempted to be uploaded via FMS Admin Console for hosting.  During the process an error message appears that FMS Admin Console has lost communication.  Upon inspection of the Data/Databases folder on the server there is a zip copy of the database itself but there are no uploaded external files.  This is all being done on the server itself with the database to be copied residing on the same hard drive (boot drive) as the server and the hosted server files.  The total size of the encrypted "Files" folder is 4.5GB.

      Expected result

      Expected it to take a while but complete successfully.

      Actual result

      Failed with lost communication

      Exact text of any error message(s) that appear

      Don't have the exact text but a dialog box appears saying that the FMS Admin Console has lost communication and upon clicking on the "OK" button FMS Admin Console quits.

      Configuration information

      Mac Mini 2011, Internal 750GB 7200 RPM HD, 16GB RAM, MacOS-X 10.8.2 Server

      Workaround

      Open the database with FileMaker Pro and turn off external storage for the containers.  After this process the database is 6.6GB in size and uploads but also failed after creating the zip file.  Decompressed the zip file, changed permissions, and opened via FMS Admin Console

      Screen_Shot_2012-11-10_at_10.04.38_AM.png