We’re moving our FSM 5.7 install to a new group of servers, and nobody can sync from the mobile app on the new servers. The sync screen starts and just keeps trying “forever”. There’s a notable error message coming out of the Application server log - note it shows sequence “0” no matter what user is logging in:
Timestamp: 2021-08-10T09:02:40.4152271-06:00
Message: Exception Message : Cannot change value because row person_mobile with keys person_id, sequence and values DMITCHEL, 0 is not in the database.
Source : Not Available
Target Site : Not Available
Machine: UFAAP214
App Domain: /LM/W3SVC/1/ROOT/FSMServer_5_7_0-1-132730035402219553
ProcessId: 4408
Process Name: w3wp
Thread Name: ServiceRequest_22
I tried deleting the person_Mobile record for one of the my own person (through the UI of course), but that made no difference.
The Mobile business server log just displays this over and over again when we try to sync:
8/11/2021 4:16:26 PM; TR; 7447; PerformGetMessageForDeviceBySize; Query mm_message_out Message: <hierarchy_select> <primary_table>mm_message_out</primary_table> <from> <table>mm_message_out</table> </from> <attrs> <attr>mm_message_out.*</attr> </attrs> <where> <data_constraint> <constraint> <left_operand>mm_message_out.person_id</left_operand> <operator>eq</operator> <right_operand>DMITCHEL</right_operand> </constraint> <constraint> <left_operand>mm_message_out.device_sequence</left_operand> <operator>eq</operator> <right_operand>0</right_operand> </constraint> </data_constraint> </where> <order_by> <asc>mm_message_out.message_id</asc> </order_by> <authentication> <logon_info> <person_id>METRIX</person_id> <password>XXXXX</password> </logon_info> </authentication></hierarchy_select>
The Mobile web service log displays this over and over:
8/12/2021 10:17:17 AM; CM; 982; 0; StreamingEnabled:True
8/12/2021 10:17:21 AM; CM; 985; 0; Cloud Environment:False
Any ideas? I’ve been through the troubleshooting section of the FSM57Mobile document and the only weird thing is our METRIX account has a “MOBILE” license instead of NAMED or MESSAGE, but that’s also how it is on the old infrastructure.
