About former_member1351120

former_member1351120 · 10-23-2023

Everything was working fine. Installed a new certificate, and now receive error OEE1028: The Outbound Enabler was unable to write an HTTP body to the Relay Server because of [MLC24: Server certificate not trusted.] Hoping I can get help resolving...

former_member1351120 · 11-07-2019

We are upgrading MobiLink v16 to v17. We have the following setup- ServerA (Windows 2016, IIS, MobiLink RelayServer v17)- ServerB (Windows 2016, OutboundEnabler v17) I cannot get the OutboundEnabler functioning. The RSOE log file repeats 4 lines ev...

former_member1351120 · 11-06-2019

We are trying to upgrade MobiLink from v16 to v17. We are having issues trying to get the RS (IIS on Windows 2016 server) talking to the RSOE on another Windows 2016 server. I can find the logfile for the RSOE, but do not know where the logfile is no...

former_member1351120 · 02-29-2016

We are in the process of upgrading MobiLink from v11 to v16.I have run into this issue now in 3 environments:- initial v16 installation (resolved)- migration to test environment (resolved)- migration to production environment (not resolved)I cannot g...

former_member1351120 · 01-13-2016

Hello, I am upgrading MobiLink configuration from v11 to v16. Seem to be just about there, but currently receiving the "RSE3003 Redundant outbound enabler" message in the RS log. The v16 is being built upon the same servers that v11 was on previou...

former_member1351120 · 10-23-2023

RESOLVED....Ends up the new (replacement) certificate was generated in UPPER case, and MobiLink does not like the difference in case. Requested a new certificate in the "proper" lower case, and mystery solved.

former_member1351120 · 11-07-2019

Found it. With v17 the log file (rs.log) is added to a folder (Log) under the installation path (in our case C:\Program Files\SQL Anywhere 17\RelayServer\IIS\Bin64\Log). This differs from v16, as you specify the logfile folder location during the "...

former_member1351120 · 03-03-2016

There was no answer to this post, however if you are reading this thread, you are more than likely to find helpful information on this thread:- http://scn.sap.com/thread/3871037

former_member1351120 · 03-03-2016

Reg...This was our problem. Your help fixed the issue.We have now migrated the production environment to v16 MobiLink. Thank you so much for your professional and timely responses on this thread. Very much appreciated.Vance McColl

former_member1351120 · 03-01-2016

Thanks Reg!I think you may have found the issue. I have applied that change, and restarted my "pseudo" environment. The error messages are no longer being produced, and appears that RS is talking to RSOE.I cannot take this any further until tomorro...

User Statistics

User Activity

Receiving certificate error MLC24 server certificate not trusted

MobiLink upgrade v16 to v17 - winsock error

MobiLink upgrade v16 to v17

OEE1052 outbound enabler was unable to write to a OE_DNCHANNEL_NOOP (PUNCTURE)

RSE3003: Redundant outbound enabler connection for backend server

Re: Receiving certificate error MLC24 server certificate not trusted

Re: MobiLink upgrade v16 to v17

Re: RSE3003: Redundant outbound enabler connection for backend server

Re: OEE1052 outbound enabler was unable to write to a OE_DNCHANNEL_NOOP (PUNCTURE)

Re: OEE1052 outbound enabler was unable to write to a OE_DNCHANNEL_NOOP (PUNCTURE)