Here is an example message I am seeing in FMS10 admin console.

Client "User name" authentication failed on database "Database.fp7" using "User name [fmapp]".

This implies that 'User name' failed to open 'Database.fp7'.

My system comprises around 50 FILES, all of which have a set of user names/passwords that are the same EXCEPT some files that have only one password (Admin) and the files is set to open using 'Admin'. All of these files are inter-linked either by relationship and/or scripted access.

I understand that files opened by way of a relationship or scripted access do not obey the rules regarding the File Options settings - but this does not account for why FMS is reporting authentication failure, when there clearly is no failure as the file has opened for the user, albeit using the 'Admin' user name/password.

Please note this system has been in use for 15 years, day in, day out, and I have been developing for 10 years, with few problems, and certainly none that would produce critical errors if files would not open.

Comments, anyone?

Any files have auto-open checked? Any values stored in KeyChain?

Steven

These errors are usually generated when using an opener file or External Authentication.

Thanks Steven/John

None of those.

I can probably understand why FMS reports auth. failure on the basis that the file which is opened secondarily does not have a matching user name/password from the calling file, however FMS still permits the secondary file to open for correct processing as it does have valid credentials for the "Open file with user name/password".

As I say, the secondary files are opened via script call or relationship and this is how the system has always operated as far back as FMS 5. As I recently upgraded from FMS8 to FMS10 (skipped FMS9) then these log entries have only just become apparent.

In a simplified arrangement consider this:

File 1: Does NOT auto open

Users: 'Master', Full access. 'User', limited access

File 2: Auto opens using 'Admin'

Users: 'Admin', Full access

Both files are related. So, open File1 and submit credentials. File 2 is committed to open because of the relationship - FMS reports an an auth failure, but File2 continues to operate successfully as there is a Full Access privilege with 'Admin' and that is the auto open account - even though the auto open should not have been triggered this way.

Am I correct?

UPDATE:

I just tested this in a controlled manner and FMS DEFINITELY reports auth. failure as described.

I am the developer with master access throughout, although the master password is NOT the same in all files. Some of the files are 'reference' files which only have the 'Admin' user, so they have always worked as that is the only user that is used to open them with - they don't have a password either.

I opened a 'primary' file with the 'Master' user and then went into Manage Database, FMS reported I have failed auth. on the related files that only have the 'Admin' user, as 'Admin' does not exist in the 'primary' file.

Like John said: if your FMS is set up to allow external accounts for instance it will always try the OS account first before anything else. If there is no matching external account set up in your FM files then FMS will report an authentication error.

Thanks Wim

There's NO EXTERNAL authentication involved.