Jump to content
shailasg

Filemaker Client 13 or later very slow on launch and during use

Recommended Posts

Filemaker Pro 13 or later is very slow on launch and during use

George ShailasSolution Starter

George Shailas Feb 14, 2017 1:28 PM

CAUSE OF THE ISSUE AND THE SOLUTION:

It seems that when you using Filemaker Server, the client creates initially 150 temporary files in C:\Users\UserName\AppData\Local\Temp named FMTEMPFM####_###.png These files are just png picture files and it seems they get created very often while are connected to the server. It can create 20-30 files for every move you take do do something.

 

Well when you have 2 MILLION of these files create over time, this will cause the Filemaker to take up two hours to launch. Just to view the directory from windows it takes a good hour to display. Well for Filmaker to try to create again these files in this huge directory it takes a good hour and makes the application non responsive. Sometimes I noticed the slowness also as I was using the Database and that is because Filemaker creates these files as you are connected as well every time you perform an action.

 

DO NOT TRY TO DELETE THESE FILES FROM THE WINDOWS INTERFACE. IT IS IMPOSSIBLE.

 

RUN del  "C:\Users\%username%\AppData\Local\Temp\FMTEMP*.png"   /Q

 

THIS WILL DELETE THE FILES MUCH MORE FASTER.

 

AFTER I DELETED ALL THESE FILES AND THE C:\Users\UserName\AppData\Local\Temp  DIRECTORY IS EMPTY, THE FILEMAKER IS NOW BACK TO NORMAL.

 

NOTE: FOR SOME REASON, IF YOU JUST USE FILEMAKER CLIENT ONLY WITHOUT THE SERVER THE PROBLEM DOES NOT EXIT.

 

I SPENT A LOT OF COMPANY'S TIME OVER THE LAST SIX MONTHS TO FINALLY FIGURE OUT THE SOLUTION, THAT DOES NOT INCLUDE THE FRUSTRATION OF ALL OF MY USERS THAT WENT THROUGH, SWITCHING OR RELOADING MACHINES EVERY TIME TO AVOID THE ISSUE. THE FILEMAKER CUSTOMER SUPPORT WAS UNABLE TO HELP AT ALL. I AM NOW EXPECTING FILEMAKER TO CORRECT THE BUG AND ISSUE AN UPDATE AS SOON AS POSSIBLE.

 

Attached is a picture of the Temp directory listing 1.5 MILLION FILES. That was after I deleted 1 MILLION.

 

TEMPORARY SOLUTION UNTIL FILEMAKER INC. FIXES THE PROBLEM:

 

CREATE AN MSDOS BAT COMMAND FILE DELFMTEMPFILES.BAT WITH THE FOLLOWING COMMAND AND CALL IT during Open or on Close:

del  "C:\Users\%username%\AppData\Local\Temp\FMTEMP*.png"   /Q

 

 

THANKS

George

 

FMTEMPFM.JPG

Edited by shailasg
Updated text

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By sal88
      Hi all
      I've created a value list that serves as an email autocomplete drop down (like the sort in an email client). This VL looks to a single text field in a single record table which currently has 3000 lines. The field is updated every 15 minutes by a scheduled server script.
      The 'auto complete using value list' option is applied on the field that refers to this VL.
      The old method was to not have a VL but to just tick the 'auto complete using existing values' option on the field. This was not ideal because existing values might be incorrectly spelled email addresses (and the user would not be able to remove them).
      Since switching to the new method it is slower to retrieve the values from the VL. It is not the type of slowness that locks up filemake; rather it just means the user has to wait 1-4 seconds for values to pop up when letters are typed - before this is was instant in the way it is instant in normal email clients.
      Does anyone have any ideas as to how to speed it up? Or whether this is expected from a single field VL?
       
      Thanks
    • By jemcgui
      Hello,
       
      I'm new to FMS and I'm trying to figure out why opening a database is taking so long. When I open the DB over our gigabit LAN things work smoothly and the layout opens in 1-2 seconds, but if I switch to our Wireless LAN opening the same layout can take up to 90 seconds and if I try to connect via VPN from home then we're into the minutes time frame. All the calculations occur server side in FMS correct? So if it's sending the same amount of results data why does a drop in connection speed cause such a drastic change in load times, unless of course wer're sending a HUGE amount of data to the client. Is there a way to track how much data is getting sent to the client?
       
      The size of the database is really quite tiny; something like 200k records / 3k fields.
       
      Server Specs:
      10.7 Mac
      2x 2.93 Ghz Hexcores
      16GB of 1333 Mhz DDR3 ram.
      The only application it runs is FMS though it does alos serve a file store.
      The CPU according to Activity Monitor never gets above 1-2% usage.
    • By VickyLNesbitt
      Hi All
       
      I'm wondering any of you could shed some light on this for me or rather make some educated guesses about what could be our problem!
       
      Our setup;
       
      Mac server (10.6.8), running FileMaker Server 11 Advanced
      Mac clients (all between 10.5.8 and 10.6.8 I think) all running via FileMaker Pro 11 - these clients log into networked user accounts which are synched between 2 different locations (although they only log into this FileMaker Server from one location)
      We also have a number of clients who connect to a PHP site with FileMaker backend.
       
      Right so at least once a week our server crashes, all users get the spinning wheel and are kicked or have to force quit FileMaker. There is nothing at all in the logs to suggest what has caused this...
       
      I just wanted to know if there is some kind of issue with our setup i.e. the synched networked user accounts or if there is anything else any of you can suggest???
       
      If you want some more info don't hesitate to ask!
       
      Thanks in advance
       
      Vicky x
       
×

Important Information

By using this site, you agree to our Terms of Use.