1 Reply Latest reply on May 19, 2011 11:11 AM by philmodjunk

    Cannot remote access a hosted file anymore



      Cannot remote access a hosted file anymore



      The compagny i work for has FMP 7 databases, but one of them suddenly decided to stop working with multiple users.

      Everything was working fine until 2 days ago, suddenly the username and password were not valid.

      The database is on a server, the 1st user log in and becomes the host and the other log in via remote, but now it always gives the message to the user using remote " The account and password cannot be used to access this file. Please try again "

      If the remote user copy the database on his desktop and log in locally with his username and password everything is fine, but again trying to use the same username/password as remote is not working now.

      All the users are PCs and we are not using FM Server.

      Anybody has any idea?

      Because i did not create those databases and my knowledge of FileMaker is fairly limited, i cannot go into anything technical and but i'm an IT so if you explain or have documentation i'm sure i can manage.

      Thank You


        • 1. Re: Cannot remote access a hosted file anymore

          Sounds like you have damaged your file and this is likely due to the way your are sharing your file over the network.

          If two users attempt to access the file directly on the shared directory at the same time, you can get a corrupted file. Also, having the first user host the file from a shared directory has an increased risk of damage to the file if he gets a network "glitch" while he has the file open.

          FileMaker Techs recommend that you always host the file with FileMaker Pro by first opening it with FileMaker Pro on the computer where the file is located, then other users use open remote to connect to the file. The file should not be placed in a shared directory to prevent uers from attempting to open the file directly over the network.

          Recover the file and test the recovered copy to see if it works.

          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.