on 11-20-2012 4:31 PM
All,
The client has in the application a synchronise button that they can only press one time and after the synchronise is done he can press a second time and so on. It crashes on the synchronise (the first one) and then we get the error below :s…
The code that we are using is the following:
SAET_LINKSynchronizationParameters *sp_link = [SAET_LINK getSynchronizationParameters];
sp_link.syncLinkByUserID = employeeID;
[sp_link save];
[SAMborevcrmDB synchronize:@"AccountContactGroup"];
SAET_VISITSSynchronizationParameters *sp_visit = [SAET_VISITS getSynchronizationParameters];
sp_visit.syncByEmployeeId = employeeID;
sp_visit.syncByInitiatorId = employeeID;
[sp_visit save];
[SAMborevcrmDB synchronize:@"VisitGroup"];
SAET_TASKSSynchronizationParameters *sp_link_task = [SAET_TASKS getSynchronizationParameters];
sp_link_task.syncByEmployeeId = employeeID;
sp_link_task.syncByInitiatorId = employeeID;
[sp_link_task save];
[SAMborevcrmDB synchronize:@"TaskGroup"];
Now after a synchronising multiple times > 10 we get the following error:
SUPPersistenceException from synchronize: SUPPersistenceException from isReplayQueueEmpty: error in findEntities -> Crash...
Has anybody any idea what the problem can be?
We are working with SUP 2.1.3 patch 02.
Nick
Hi Nick,
Refer to ths issue that you are facing " SUPPersistenceException from synchronize: SUPPersistenceException from isReplayQueueEmpty: error in findEntities -> Crash" , This is a known issue and appears in the Synchronize method when Synchronization is performed many times continuously as you did.
I can see that patch is release but it is for SUP 2.1.3 with patch 01. I suggest you to contact SAP support as they will provide you required information for your patch release after investigation.
Regards,
Sachin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nick,
i had the same error when using consecutives synchronizations, i posted a ticket to SAP and they answered me that this is solved at:
- SUP 2.2 (have not tested)
- SUP 2.1.3 with patch 01 + another private patch that they sent me.
Apparently they told me that there is no solution for SUP 2.1.3 with patch 02 or previous versions (2.1.2 and below). I guess you might need to upgrade or downgrade your version of SUP.
Regards,
Daniel Yrigoyen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.