Timeouts in SRM

[former_member114630]

On a regular basis, we have users timing out of SRM while they are actually entering data. We can see the entries in SM21.

We have no idea what the messages mean. We are also unable to recreate it for OSS. Does anyone have any ideas how we should proceed? The following are a common list of errors:

Transaction Canceled ITS_P 101 ( Cannot sync )

Transaction Canceled ITS_P 041 ( t_screen_acclist-g_l_acct[1] )

Transaction Canceled ITS_P 041 ( t_screen_acclist-generic_acc[1] )

[Former Member · Accepted solution]

Hi,

Have you made any changes in the ITS templates?

BR,

Disha.

[former_member114630]

Applied OSS notes for the "nervous finger problem".

[Former Member]

Hi,

Could you please confirm,which OSS note fixed this issue,

Regards,

Srik.

[Former Member]

Hi Monique,

We are having the same issue. Appreciate telling me which OSS that you applied.

Thank you,

Glen

[Former Member]

Hi,

Also check note 705013.

BR,

Disha.

PLs reward points for helpful answers.

[former_member114630]

Everything appears to be correct. The problem is only happening every so often.

We are pretty sure the users are hitting a key sequence causing the connection to be disrupted. Once the connection is in error, the kernel gets confused on whom to talk to and stops – throwing the error.

Without actually sitting with the user and waiting for the error to occur, we have no way of knowing what they may have done at that particular time to generate the timeout.

[Former Member]

Hi Monique,

Did you solve this problem?

I'm facing it in SRM 5.0, also with some of the users.

I could reproduce the problem when I simulated a user navigating in SRM (Web), using a App server (A) . When the load balancing re-directed the next http request to a diferent server (B), the error message appears:

Internal error Cannot sync

Do you have a similar arquitecture, or the problem appeared in a different situation?

Regards,

Pedro

[former_member114630]

I don't believe this was ever resolved. Since it is very sporadic and the users are unable to replicate it, we can only conclude that the users are clicking on something that the system disagrees with.