Unable to use relay server using https configuration

[Former Member]

Hi All,

I am using Sybase Unwired Platform 2.2 SP 04 with iOS 7.1.

I am implementing relay server with https configuration. I have already implemented relay server with http using port 80 which is working fine. But when I am changing the outbound enabler property from http to https in Server Configuration, outbound enabler is giving error

"Could not connect to Relay Server, errCode: 57, sysCode: 11001" in the RSOE log.

Instead of public IP, I am using hostname.com URL for accessing relay server.

Also in browser the availability of the url:  /ias_relay_server/server/rs_server.dll is showing none.

Kindly advice.

Regards

Debidutta

[joachimvanpraet]

Hi Debidutta,

I also had some problems to connect the RSOE to the relay server with https.

I changed the settings for ssl on the "server" folder from accept to ignore client certificates.

kr,

Joachim

[Former Member]

Hi Joachim,

I suggest you to uncheck Require SSL option too,  and than check in browser with the https option. if it's working there than go to SCC and check if you have configured proper certificate or not. Below mention image will guide you where to check it or How to map Certificate in SCC.

Regards-
Dipak

[Former Member]

Hi All,

This issue has been resolved to some extent. Now I am able to browse relay server through https:443. But still whenever I am tryng to sync from iOS, I am getting the 'Request Timeout' error.

Any suggestions??

Regards

Debidutta

[midhun_vp]

Double check whether you are adding the certificate before sync,http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01217.0225/doc/html/fre13...

Midhun VP

[Former Member]

Hi Midhun,

Thanks for your reply.

I have checked the link you suggested and followed the same approach. But after that when we try to sync the data, it is giving 571 error code.

Any suggestions further??

Debidutta

[Former Member]

Hello,

Could it be related to ;

CR 695671

Listview object query fails with error.

When performing a listview object query with very large data sets, the client returns an

error code 571 or 1053, and the server becomes temporarily unavailable, or tries to

restart. The mlsrv_err.log reports java.lang.OutOfMemoryError.

Workaround: Modify the maximum Java heap size to handle very large amounts of data

in an object query. See Configuring Unwired Server Performance Properties in System

Administration.

Can you specify what you mean with 571 error code?

Where do you see this?

Thanks,

Have a nice day,

Wim

[Former Member]

Hello Wim,

Thanks four reply.

Actually I have developed an iOS native app using SUP 2.2 SP 04 with SAP as back end.

I am using the relay server for connecting to the SUP server.

I have done the binding of the certificate to my relay server with url: hostname.com.

The relay server availability is FULL for both http(80) and https(443).

When I try to connect to the relay server from iOS using http(80) by providing the url: hostname.com the device is getting registered and the sync starts.

But When I try to connect to the relay server from iOS using https(443) by providing the url: hostname.com the device keeps waiting for an unusual long time and throws an error code 571 for COMMUNICATION_SESSION_TIMEOUT.

Please suggest.

Best Regards

Debidutta

[Former Member]

Hello,

When you test with https, do you see entries coming in to the rs.log?

Have a nice day,

Wim

[Former Member]

Hello Wim,

Me and Debidutta part of a same team and working on the same solution.

Here rs.log means IIS server log? (where Relay server has been hosted). if not, Please let me know where should I look for it.

Thanks & Regards-

Dipak

[Former Member]

Hello,

The location of the Relay Server log (rs.log is the default name) is specified in the parameters of your Relay Server Windows service.

So, I think you should look for it there or jus search on "rs.log".

The IIS log is separate from the Relay Server log.

These are the IIS logs that are relevant for you;

• The W3SVC log; for IIS 7 this file is located in the C:\inetpub\logs\LogFiles\W3SVC-folder

This file will give an overview of HTTP requests that came in, the IP of the sender and the HTTP response code to the request.

• The HTTPErr log; for IIS 7 this file is located in the C:\Windows\System32\LogFiles\HTTPERR-folder

Please check if you see anything coming into these files after testing.

Have a nice day,

Wim

[Former Member]

Hi Wim,

I have retrieved the log and the log contents are as follows:

I. 2014-04-08 16:50:09. <DnChannel-0000> parseHTTP(): HTTP status received: 204

I. 2014-04-08 16:50:09. <DnChannel-0000> parseHeaders: successfully parsed Transfer-encoding

I. 2014-04-08 16:50:09. <DnChannel-0000> absorbing chunked data

I. 2014-04-08 16:50:09. <DnChannel-0000> absorbChunkedBytes: end of chunked data reached

I. 2014-04-08 16:50:09. <DnChannel-0000> Sending down channel connect packet..

I. 2014-04-08 16:50:09. <DnChannel-0000> doHTTPRequest: sending POST request..

I. 2014-04-08 16:50:09. <DnChannel-0000> Wrote request headers:

                        POST /ias_relay_server/server/rs_server.dll HTTP/1.1

                        Content-Type: application/octet-stream

                        Host: xxx.xxx.xx.xxx:443

                        Connection: close

                        User-Agent: IAS_OE_DnChannel

                        Content-Length: 2097152000

I. 2014-04-08 16:50:09. <DnChannel-0000> TripLeft: 2097102848

I. 2014-04-08 16:50:09. <DnChannel-0000> downChannel noDownCtr: 0

I. 2014-04-08 16:50:09. <DnChannel-0000> Down channel connect request sent..

I. 2014-04-08 16:50:09. <DnChannel-0000> Releasing connect mutex

I. 2014-04-08 16:50:09. <DnChannel-0000> Successfully connected to relay server: xxx.xxx.xx.xxx:443

Regards

Debidutta

[Former Member]

Ok, great.

What do you see in the RSOE logs?

Have a nice day,

Wim

[Former Member]

Hi Wim,

The above log that I posted recently is the messaging RSOE log generated from the sybase control center.

Now below is the log content from the relay server log at C:\inetpub\logs\LogFiles\W3SVC1

#Software: Microsoft Internet Information Services 7.5

#Version: 1.0

#Date: 2014-04-08 13:34:14

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-

Agent) sc-status sc-substatus sc-win32-status time-taken

2014-04-08 13:34:14 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - xxx.xxx.xx.xxx IAS_OE_DnChannel 200 0 64 8050579

#Software: Microsoft Internet Information Services 7.5

#Version: 1.0

#Date: 2014-04-08 13:34:20

#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken

2014-04-08 13:34:20 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 15

2014-04-08 13:34:20 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 46

2014-04-08 13:34:21 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 31

2014-04-08 13:34:21 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 31

2014-04-08 13:34:22 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 62

2014-04-08 13:34:22 172.22.219.193 POST /ias_relay_server/server/rs_server.dll - 443 - 112.xxx.xx.xxx IAS_OE_DnChannel 200 0 0 1781

Below is the log contents found at C:\Windows\System32\LogFiles\HTTPERR-folder

2014-04-08 13:34:15 112.xxx.xx.xxx 60782 172.22.219.193 443 HTTP/1.1 POST /ias_relay_server/server/rs_server.dll 400 1 BadRequest RelayServer

2014-04-08 13:34:15 112.xxx.xx.xxx 60810 172.22.219.193 443 HTTP/1.1 POST /ias_relay_server/server/rs_server.dll 400 1 Connection_Abandoned_By_ReqQueue RelayServer

2014-04-08 13:34:15 112.xxx.xx.xxx 60782 172.22.219.193 443 HTTP/1.1 POST /ias_relay_server/server/rs_server.dll 400 1 Connection_Abandoned_By_ReqQueue RelayServer

As you can see, we are getting Bad Request in the last log contents.

I request you to provide your valuable suggestions on this.

Regards

Debidutta

[Former Member]

Thanks, so something is killing your IIS worker process.

Do you see anything in the MS Event Logs?

Have a nice day,

Wim

[Former Member]

Hello Deb,

Please check out the below link.

Tip/Trick: Enabling SSL on IIS 7.0 Using Self-Signed Certificates - ScottGu's Blog

Regards

Megha Aggarwal

[Jitendra_Kansal]

Hi ,

Can you please help here?

Rgrds,

Jitendra

[Former Member]

Hello,

Have you checked out the section on this page about the certificate?

Configuring RSOE Connection Setting

Have a nice day,

Wim

[Jitendra_Kansal]

Not sure what went wrong. Have a look at this discussion . Hope it will be helpful for you.

Rgrds,

Jitendra

[Former Member]

Jitendra,

When I am using http:80, it is working absolutely fine with availability full, but when I change the port number to 443, I am getting the error: "Could not connect to Relay Server, errCode: 57, sysCode: 11001" and the availability becomes "None".

I don't understand where I am doing wrong.

Please suggest.

Regards

Debidutta

[Former Member]

When I am changing http:80 to https:443, outbound enabler giving error.

In outbound enabler, node status description error is coming as: "Error writing http header, either the url suffix format is wrong or selected trusted certificate is wrong".

If I check in the RSOE log, it gives the following error.

<OEHost> Error writing HTTP headers, errCode: 0, sysCode: 0

<OEHost> doHTTPRequest: sending request failed

Kindly suggest.

[Jitendra_Kansal]

Hi Deb,

I am sure you would have checked it already, is relay server up and running?

Do you have to rs.config file and can you verify if all the changes are showing there if not you may need to restart RS (I doubt it)?

You may also look at this detailed explanation.

Note: SUP 2.2 SP04 doesn't support iOS 7.1, it supports only till 7.0 as per documentation. SyBooks Online

Rgrds,

Jitendra

[Former Member]

Hi Jitendra,

Thanks for the reply.

Actually, both the relay server and iOS are working absolutely fine with http using port 80.

But when we are changing the outbound enabler to https port 443, it is giving error in the out bound enabler.

Can you explain how the relay server be configured for https?

Thanks

Debidutta

[Jitendra_Kansal]

Deb,

is it possible to restart Relay server after making changes and see if you are seeing any error then?

Can you also check in rs.config file whether all the changes are getting reflected.

Rgrds,

Jitendra

[Former Member]

Jitendra,

I am getting the following error in the RSOE log file.

"Could not connect to Relay Server, errCode: 57, sysCode: 11001".

I have restarted the relay server many times.

Thanks

Debidutta

[Former Member]

Hi All,

I am using SUP 2.2 SP 04 with relay server.

I have done the binding of the certificate to my relay server with url: hostname.com.

Case 1:

When I use the public IP in the relay server configuration, and try to access it through the url "hostname.com" using https, the availability is showing FULL

Case 2:

When I use the "hostname.com" instead of public IP in the relay server configuration, and try to access it through the url using https, "hostname.com", the availability is showing NONE.

What could be the possible reason for this?

Please suggest.

Thanks

Debidutta