Quantcast
Channel: SCN: Message List - SAP SQL Anywhere
Viewing all articles
Browse latest Browse all 2182

Re: RSE3003: Redundant outbound enabler connection for backend server

$
0
0

Thanks Mirco,

 

That question was asked when trying to upgrade our test environment from v11 to v16.  That environment resolved the issue, and has worked fine since then.  Not 100% sure, but it must have resolved itself.

 

Now, we have attempted to upgrade the production environment from v11 to v16.  Here is the sequence I start up components and the errors I now receive:

- start the RS service - all fine and waits

- start IIS AppPool, start IIS WebSite - all fine and waits

- start the ML service - all fine and waits

- start the RSOE service

   - successfully connected to backend server (ML)

   - successfully connected to relay server (RS)

- messages from the RS as follows

   - Processing RS peer list request

   - Processing up channel connect request

   - Authenticating up channel first time connection

   - Using RSOE protocol version 8

   - Engaging...

   - Established for server 'servername' in farm 'farmname'

   - Processing up channel connect request

   - Authenticating up channel first time connection

   - using RSOE protocol version 8

   - Engaging...

   - RSE3003: Redundant outbound enabler connection...

   - Processing down channel connect request

   - Authenticating down channel

   - RSE3005: Mismatched outbound enabler instance...

   - ...above 8 lines repeat...

- messages from the RSOE as follows

   - OEE1052: The outbound enabler was unable to write a OE_DNCHANNEL_NOOP(PUNCTURE) packet to the Relay Server because of ... (winsock error code: 10053).

   - successfully connected to relay server

   - OEE1031: The outbound enabler access was denied by the relay server

   - OEE1036: A network connection was closed by the relay server or an intermediary while the outbound enabler was reading from it

 

 

We were not able to complete a synchronization.  However, we never let the connection remain actively trying for more than a few of minutes, and the interval is set at 10 minutes.

 

Based on your previous comments, should I reduce the interval to 1 minute, and leave the connection actively trying to synchronize for a much longer time - like 1 or 2 hours.  With this frequency, and duration (leaving the connection trying to sync on a 1 minute interval) do I have a chance of this resolving itself?


Viewing all articles
Browse latest Browse all 2182

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>