two of Customer's BlackBerry’sone(one a
simulator) experienced a login timeout error. One was unable
to
connect and one was unable to register with this
error:
“com.sybase.mobile.ApplicationTimeoutException: Unable to
register
application within 150 seconds.” We would like to know if
there is anything
that indicates why this could have
happened.
Here is a glimpse of the error that we see in the server log:
Thread-269 [com.sybase.djc.security.SecurityManagerLog] Login Failed: user 'E60470'. Account is locked due to previous login failures. Account will be unlocked in 2,371 seconds.
2013-04-11 11:57:08.639 ERROR Mobilink Thread-269 [com.sybase.ml.sup.Logger] [-10052] The authenticate_parameters script returned 4000
2013-04-11 11:57:08.675 WARN MMS Thread-286 [com.sybase.djc.security.SecurityManagerLog] Login Failed: user 'T41661'. Account is locked due to previous login failures. Account will be unlocked in 2,403 seconds.
2013-04-11 11:57:08.685 ERROR Mobilink Thread-286 [com.sybase.ml.sup.Logger] [-10052] The authenticate_parameters script returned 4000
2013-04-11 11:57:08.853 WARN MMS Thread-268 [com.sybase.djc.security.SecurityManagerLog] Login Failed: user 'E60279'. Account is locked due to previous login failures. Account will be unlocked in 3,595 seconds.
2013-04-11 11:57:08.866 ERROR Mobilink Thread-268 [com.sybase.ml.sup.Logger] [-10052] The authenticate_parameters script returned 4000
2013-04-11 11:57:10.134 WARN MMS Thread-275 [com.sybase.djc.security.SecurityManagerLog] Login Failed: user 'E10972'. Account is locked due to previous login failures. Account will be unlocked in 2,960 seconds.
and in the mlsr log:
I. 2012-12-19 12:29:57. <67427> Subscription id 7: consolidated progress 0 and remote progress 0
W. 2012-12-19 12:30:36. <67439> [10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 35 in the consolidated database and 33 in the remote database. The remote is being asked to send a new upload that starts at the last known synchronization point
I. 2012-12-19 12:30:36. <67439> Progress offsets for the publications that are explicitly involved in the current synchronization
I. 2012-12-19 12:30:36. <67439> Subscription id 9: consolidated progress 34 and remote progress 34
W. 2013-03-15 19:28:36. <85195> [10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 415 in the consolidated database and 409 in the remote database. The remote is being asked to send a new upload that starts at the last known synchronization point
I. 2013-03-15 19:28:36. <85195> Progress offsets for the publications that are explicitly involved in the current synchronization
I. 2013-03-15 19:28:36. <85195> Subscription id 2: consolidated progress 415 and remote progress 409
E. 2013-03-15 19:32:26. <85186> [-10279] Connection was dropped due to lack of network activity
E. 2013-03-15 19:32:27. <85187> [-10279] Connection was dropped due to lack of network activity
E. 2013-03-15 19:32:28. <85188> [-10279] Connection was dropped due to lack of network activity
E. 2013-03-15 19:32:29. <85189> [-10279] Connection was dropped due to lack of network activity
. 2013-03-14 15:15:56. <36277> [-10052] The authenticate_parameters script returned 4000
E. 2013-03-14 15:15:58. <36286> [-10052] The authenticate_parameters script returned 4000
W. 2013-03-14 15:16:00. <36296> [10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 53 in the consolidated database and 51 in the remote database. The remote is being asked to send a new upload that starts at the last known synchronization point
I. 2013-03-14 15:16:00. <36296> Progress offsets for the publications that are explicitly involved in the current synchronization
I. 2013-03-14 15:16:00. <36296> Subscription id 9: consolidated progress 52 and remote progress 52
I attached both logs for your analysis.
thanks