SAP Knowledge Base Article - Preview

2533943 - Relay Server log shows: RSE2003: Failed to use session id from client because backend server

Symptom

  • Add new relay servers and back-ends and then upgrade the Relay Server config files.
  • Afterwards existing clients could not connect or sync.
  • The Relay Server log shows these messages:

    E. 2017-09-12 09:35:24. <1964.3088.-> RSE2003: Failed to use session id from client because backend server 'xxxxxxxxx' was not found in farm 'ZYZ'
    E. 2017-09-12 09:35:28. <3860.3888.-> RSE2003: Failed to use session id from client because backend server 'xxxxxxxx1' was not found in farm 'XYZ'
    E. 2017-09-12 09:35:35. <840.2468.-> RSE2003: Failed to use session id from client because backend server 'xxxxx2' was not found in farm 'XYZ'
    E. 2017-09-12 09:46:32. <3860.6412.F1B1S1cR2> RSE4003: Client of backend server 'XXXXXXXXX'in backend farm 'XYZ' timed out waiting for backend server response after 660 seconds
    E. 2017-09-12 09:46:34. <3416.2368.F1B4S1eR4> RSE4003: Client of backend server 'xxxxxxxx' in backend farm 'XYZ' timed out waiting for backend server response after 660 seconds


Read more...

Environment

  • Relay Server Versions 12.x and 16.

Product

SAP Mobile Platform 2.3 ; SAP Mobile Platform 3.0

Keywords

RSE2003 RSE4003 RS RSOE , KBA , MOB-SUP-SCC , Sybase Control Center Administration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.