msawyer

Thousands of "single sign-on authentication failed on database leading to system crash

Discussion created by msawyer on Jan 23, 2019
Latest reply on Mar 21, 2019 by TSGal

REPORT AN ISSUE

HOPEFULLY, this is a one-off but want to report anyway.

 

Just had an event on a client's system where Server memory took off and FileMaker server crashed and system the server itself became unuseable.

 

The access log had 26,000 log entries over a 2 hour period for one user per below example of the login process which was repeated multiple times.

 

2019-01-24 14:42:10.085 +1100Information730PM_FM17SECURITY: Client "Andrew xxxx(PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "Main_System.fmp12" using "Andrew xxxx [fmapp]".
2019-01-24 14:42:10.175 +1100Information730PM_FM17SECURITY: Client "Andrew xxxx (PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "Items.fmp12" using "Andrew xxx [fmapp]".
2019-01-24 14:42:10.285 +1100Information730PM_FM17SECURITY: Client "Andrew Temple (PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "PM_Quoting_System.fmp12" using "Andrew xxxx [fmapp]".
2019-01-24 14:42:10.445 +1100Information730PM_FM17SECURITY: Client "Andrew xxxxx (PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "Items_Line_Items.fmp12" using "Andrew xxxx [fmapp]".
2019-01-24 14:42:10.604 +1100Information730PM_FM17SECURITY: Client "Andrew xxxx (PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "Digital_Files.fmp12" using "Andrew xxxx [fmapp]".
2019-01-24 14:42:10.798 +1100Information730PM_FM17SECURITY: Client "Andrew Temple (PREF2066LT12) [192.168.16.81]" single sign-on authentication failed on database "Items_Invoiced.fmp12" using "Andrew xxxx [fmapp]".

 

 

The MS Access log only reported the FileMaker server crash due to all memory being exhausted.

 

FileMaker 17 current version

MS Server 2016 22gb Ram running in a VM.

 

Cache allocated 2,000 MB.

 

The user mentioned logged on at 12.30 pm system crashed at 2.45 pm. The reported a normal log on and performance.

Outcomes