Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

We have a MobiLink setup that has been running for months. A couple of days ago the link stopped running, and I cannot get it started. The setup consists of 2 servers named ELLIPSE (in the DMZ customer facing) and TRACK (behind the firewall).

ELLIPSE (shared application server) with these SQL Anywhere services: - SQL Anywhere - AbInterfaceRelayServer

TRACK (is a server dedicated RSOE to this app) with these services installed: - SQL Anywhere - AbInterfaceMobiLinkServer - SQL Anywhere - AbInterfaceRelayServerOutboundEnabler

ELLIPSE - top of log file:
=========================
I. 2010-10-01 12:12:21. iAnywhere Relay Server Version 11.0.1.2355
I. 2010-10-01 12:12:21. 
I. 2010-10-01 12:12:21. Copyright © 2001-2009, iAnywhere Solutions, Inc.
I. 2010-10-01 12:12:21. Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
I. 2010-10-01 12:12:21. Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 2010-10-01 12:12:21. 
I. 2010-10-01 12:12:21. Machine ELLIPSE is running Windows 2003 Build 3790 Service Pack 2
I. 2010-10-01 12:12:21. Software built for X86

TRACK - top of log file:
=======================
I. 2010-10-01 13:42:50. SQL Anywhere MobiLink Server Version 11.0.1.2355
I. 2010-10-01 13:42:50. 
I. 2010-10-01 13:42:50. Copyright © 2001-2009, iAnywhere Solutions, Inc.
I. 2010-10-01 13:42:50. Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
I. 2010-10-01 13:42:50. Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 2010-10-01 13:42:50. 
I. 2010-10-01 13:42:50. This server is licensed to:
I. 2010-10-01 13:42:50.     Developer Edition
I. 2010-10-01 13:42:50.     Restricted Use
I. 2010-10-01 13:42:50. Running Windows 2003 Build 3790 Service Pack 2 on X86 (X86_64)
I. 2010-10-01 13:42:50. Server built for X86 processor architecture

I have shutdown the services and website on these servers, restarted all services and website.

ELLIPSE appears to be functioning properly -

ELLIPSE bottom of the log file:
==============================
I. 2010-10-01 13:33:14.  Engaged
I. 2010-10-01 13:33:14.  45 bytes RS_UPCHANNEL_CONNECT_RESPONSE(fidx=0;bidx=0;rsid=_unused_;rsu=44bb099e70774109be5e225edc4c3137;dtl=2097152000;oet=1)
I. 2010-10-01 13:33:14.  Established for server 'AbInterfaceMobiLinkServer' in farm 'AbInterfaceMobiLinkFarm'
I. 2010-10-01 13:33:14.  Waiting for client request
I. 2010-10-01 13:33:45.  Sending a 4 bytes liveness packet
I. 2010-10-01 13:33:45.  4 bytes RS_UPCHANNEL_NO_DOWN()
I. 2010-10-01 13:33:45.  Waiting for client request
I. 2010-10-01 13:34:15.  Sending a 4 bytes liveness packet
I. 2010-10-01 13:34:15.  4 bytes RS_UPCHANNEL_NO_DOWN()
I. 2010-10-01 13:34:15.  Waiting for client request
I. 2010-10-01 13:34:45.  Sending a 4 bytes liveness packet
I. 2010-10-01 13:34:45.  4 bytes RS_UPCHANNEL_NO_DOWN()
I. 2010-10-01 13:34:45.  Waiting for client request
I. 2010-10-01 13:35:15.  Sending a 4 bytes liveness packet
I. 2010-10-01 13:35:15.  4 bytes RS_UPCHANNEL_NO_DOWN()
I. 2010-10-01 13:35:15.  Waiting for client request
I. 2010-10-01 13:35:45.  Sending a 4 bytes liveness packet
I. 2010-10-01 13:35:45.  4 bytes RS_UPCHANNEL_NO_DOWN()
I. 2010-10-01 13:35:45.  Waiting for client request
I. 2010-10-01 13:35:51.  After SHM_USE Attach: GetAttachCount: 2  GetRefCount: 2
I. 2010-10-01 13:35:51.  Received a new OE request
I. 2010-10-01 13:35:51.  231 bytes OE_UPCHANNEL_CONNECT(farm=AbInterfaceMobiLinkFarm;backend=AbInterfaceMobiLinkServer;mac=00-13-21-65-d3-23!!;token=****;protocol=4;oeu=82ae99f09ee14dd991b3dd36ef997b24)
I. 2010-10-01 13:35:51.  Processing up channel connect request
I. 2010-10-01 13:35:51.  Relabel up channel as 
I. 2010-10-01 13:35:51.  Using RSOE protocol version 4
I. 2010-10-01 13:35:51.  Engaging...
I. 2010-10-01 13:35:52.  Finished
I. 2010-10-01 13:35:52.  Disengaged
I. 2010-10-01 13:35:52.  Going to Close SHM_USE

TRACK on the other hand, has "E." type messages -

TRACK bottom of the log file:
============================
I. 2010-10-01 13:42:50.  Connected
I. 2010-10-01 13:42:50.  This software is using security technology from Certicom Corp.
I. 2010-10-01 13:42:50.  MobiLink server started
E. 2010-10-01 13:43:49.  [-10030] A network read failed.  Unable to read data from the remote client
E. 2010-10-01 13:43:49.  [-10091] This connection will be abandoned due to previous errors

I am hoping someone is able to assist me determining how to resolve the outstanding issue, and get the links back into operation. Thanks.

asked 01 Oct '10, 20:54

Vance's gravatar image

Vance
46335
accept rate: 0%

edited 07 Oct '10, 19:44

Breck%20Carter's gravatar image

Breck Carter
32.5k5417261050

Is it possible to temporarily either place TRACK outside the firewall or bring ELLIPSE inside the firewall to test if it is a network issue?

(03 Oct '10, 22:53) Siger Matt

we have found the problem:

  1. we received information that the messages in the Relay Server log file probably indicated either: 1) IIS upgraded to IIS 7 which needs a later EBF than we are running, or 2) a length filter had been set because Relay Server needs 2GB messages to talk to RSOE.

checking the website log on the Relay Server, we found GETS and POSTS to the RSOE which included the message: "Rejected-By-UrlScan". We found this to be more informative than the Relay Server log file messages:

2010-10-06 23:46:02 W3SVC1822829138 142.32.78.25 POST /ias_relay_server/server/rs_server.dll - 443 - 142.32.36.178 IAS_OE_UpChannel 200 0 0
2010-10-06 23:46:02 W3SVC1822829138 142.32.78.25 GET /Rejected-By-UrlScan ~/ias_relay_server/server/rs_server.dll 443 - 142.32.36.178 IAS_OE_DnChannel 404 0 2

A Google search led us to some good explanations, plus the MSKB article: http://technet.microsoft.com/en-us/library/cc751376.aspx. we could then see the urlscan.ini file had been modified in the timeframe that our failures started.

a further search of log files on the web server revealed: 2010-09-29 23:49:29 142.32.36.178 1822829138 POST /ias_relay_server/server/rs_server.dll Rejected Content+length+too+long Content-Length: 2097152000 30000000

so we are fairly certain this content length limit was added, causing the failures. We are now waiting for the appropriate changes to verify the solution.

permanent link

answered 07 Oct '10, 16:02

Bill%20Aumen's gravatar image

Bill Aumen
2.1k354775
accept rate: 16%

edited 07 Oct '10, 19:46

Breck%20Carter's gravatar image

Breck Carter
32.5k5417261050

The Web server prevented the request from reaching the Relay Server plug-in. As a result, there is nothing the Relay Server can report as it does not know about the request. Knowing how the Web server works (IIS and Apache) is key to understanding how the Relay Server plug-ins interact in the system.

(08 Oct '10, 15:28) Josh Savill

Vance,

The TRACK log indicates a failed synchronization due to a network issue. This could occur as a result of a variety of reasons including a dropped network connection, timeout, etc. Were there any recent changes to any network topology?

Can you post the entire RSOE log with -v 4 output and the entire Relay Server log with verbosity = 4? Ideally you could post the entire log as a text file attachment. I'm not sure if that is possible with sqla.stackexchange.

There is a Relay Server specific newsgroup located at sybase.public.relayserver.general. You can post the files to this location so they can be reviewed.

Cheers, Josh Savill Project Manager - Sybase | An SAP Company

permanent link

answered 05 Oct '10, 19:14

Josh%20Savill's gravatar image

Josh Savill
510135
accept rate: 27%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×371
×37
×5
×4
×2

question asked: 01 Oct '10, 20:54

question was seen: 12,144 times

last updated: 07 Oct '10, 19:46