SMP2.3 SP7 - URGENT - Impossible to synchronize data

[Former Member]

Dear All,

I have a problem with Native iOS App after the upgrade of SUP 2.2 SP5 to SMP 2.3 SP7.

After the upgrade I have regenerate the source code from SDK2.3 for the App and I have updated the libraries necessary in Xcode project.

After this when I try to use the App I can see that the connection arrive at SMP because the related Application Connection has status "Online" but I have a problem in Replication profile because I don't receive the message "You are online" during registration / connection to SMP. In XCODE Log I can see these records:

2015-12-29 14:11:31.446 xxxxxxxx1[3219:1523464] =================================================

2015-12-29 14:11:31.446 xxxxxxxx1[3219:1523464] onConnectionStatusChanged: status = 103, code = 0, message =

2015-12-29 14:11:31.446 xxxxxxxx1[3219:1523464] =================================================

2015-12-29 14:11:32.636 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:32.636 xxxxxxxx1[3219:1523464] onApplicationSettingsChanged: names = [Default - 1]

2015-12-29 14:11:32.636 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:32.675 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:32.675 xxxxxxxx1[3219:1523464] onApplicationSettingsChanged: names = [Default - 1]

2015-12-29 14:11:32.675 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:33.000 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:33.000 xxxxxxxx1[3219:1523464] onApplicationSettingsChanged: names = [Default - 1]

2015-12-29 14:11:33.000 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:33.236 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:11:33.236 xxxxxxxx1[3219:1523464] onApplicationSettingsChanged: names = [/var/mobile/Containers/Data/Application/78043499-C508-44A7-A1B8-1348461C8931/Documents/xxxxxxxx1_v7_trustedCertificates.crt]

2015-12-29 14:11:33.236 xxxxxxxx1[3219:1523464] ================================================

2015-12-29 14:13:10.467 xxxxxxxx1[3219:1523223] =================================================

2015-12-29 14:13:10.488 xxxxxxxx1[3219:1523223] onConnectionStatusChanged: status = 104, code = 0, message = (null)

2015-12-29 14:13:10.531 xxxxxxxx1[3219:1523223] =================================================

2015-12-29 14:13:10.564 xxxxxxxx1[3219:1523465] =================================================

2015-12-29 14:13:10.565 xxxxxxxx1[3219:1523465] onConnectionStatusChanged: status = 105, code = 0, message =

2015-12-29 14:13:10.565 xxxxxxxx1[3219:1523465] =================================================

2015-12-29 14:13:10.654 xxxxxxxx1[3219:1523464] =================================================

2015-12-29 14:13:10.654 xxxxxxxx1[3219:1523464] onConnectionStatusChanged: status = 105, code = 0, message =

2015-12-29 14:13:10.654 xxxxxxxx1[3219:1523464] =================================================

Seems that the SMP required a certificate  "/var/mobile/Containers/Data/Application/78043499-C508-44A7-A1B8-1348461C8931/Documents/xxxxxxxx1_v7_trustedCertificates.crt" but I don't have setted the certificate in SMP and in the App. In SUP2.2 this application runs correctly.

Below you can see how I have valorized the NetworkStreamParam:

[sp setNetworkStreamParams: @"trusted_certificates=;compression=none;url_suffix=/ias_relay_server/client/rs_client.dll/xxxxxxxx1.05RBS"];

I have also try to search a solution in the standard documentation but the http://infocenter.sybase.com/ website is down from 5 days.

Could you help to resolve this problem ?

Many thanks.

Regards.

--

Roberto

[vfweiss · Accepted solution]

What might be worth checking out is the following:

Known Issues for Native Object API - Release Bulletin 2.3 SP07 - SAP Library

• SMPONP-18226 iOS apps fail to register with SAP Mobile Server after upgrading to SAP Mobile Platform version 2.3 SP05 or SP06.After upgrading to SAP Mobile Platform version 2.3 SP05 or SP06 from SAP Mobile Platform versions 2.3 SP01, SP02, or SP03, an iOS app cannot successfully register with SAP Mobile Server using the iOS Object API.Workaround:
  1. Log in to SAP Control Center, go to localhost Configuration General Components .
  2. Select Replication, and click the Properties button.
  3. Set the value of properties E2E encryption certificate alias and Secure sync port certificate alias to the proper e2ee alias, and click Save.
  4. Restart SAP Mobile Server.

In a 2.1 landscape I upgraded I had to change these values as well.

Currently working in a fresh 2.3 landscape and I haven't set anything else but the default you get when you install from scratch:

And networkstreamparams are: "url_suffix=/ias_relay_server/client/rs_client.dll/<farmid-rep>"

which results in the following logging:

onApplicationSettingsChanged: names = [/Users/X/Library/Developer/CoreSimulator/Devices/E4577792-DED1-4167-89C3-DC73B003E772/data/Containers/Data/Application/877E611D-1FA1-4B2C-BAF1-993C8A55339C/Documents/X_e2eeKey.key]

================================================

================================================

onApplicationSettingsChanged: names = [/Users/X/Library/Developer/CoreSimulator/Devices/E4577792-DED1-4167-89C3-DC73B003E772/data/Containers/Data/Application/877E611D-1FA1-4B2C-BAF1-993C8A55339C/Documents/X_trustedCertificates.crt]

================================================

So havent set anything either besides the default which came with a fresh installation.

Main difference between our logging is that e2eeKey part first.

[Former Member · Accepted solution]

Thanks Vincent,

changes in SCC has resolve the problem of certificate. Now I receive the connection successful response.

Now I have another problem, when I press the button to synch I receive this error code in console

onRegistrationStatusChanged: status = 203, code = 0, message = (null)

Seems that the App is not able to use replication farm to synch data. I have setted a breakpoint in ABAP BACKEND but the request not arrive in ECC.

Do you have any suggestions ?

Thanks, regards.

[vfweiss · Accepted solution]

The 203 is good though as that is: SUPRegistrationStatus_REGISTERED = 203,

The code I use to register and sync is based on:

Except I don't have to set the username and pass through personalisation parameters as those are handled by SMP already.

Do you get a SUP*Exception or is anything related displayed in the log files of the SMP server?

[Former Member · Accepted solution]

Now the application is not able to synch any data with backend.

I don't receive an exception in Xcode console, when the App execute the instruction Synchronize I receive an empty result.

In domain log is not present any error, in Server Log there are this error:

2015-12-29 16:59:32  Module=HttpdSync, Description=(x-sup-sessid=uobqj09x52ga) SetRequestComplete  request dropped due to Invalid request handle=55, Level=ERROR, User=, Application Connection ID=, Thread ID=7928, Node=SAPSMPSVIL, Trace file name=SAPSMPSVIL_OBMO_HttpdSync_20151125T085507.txt, File attachment=, File name=, Line number=

In the file indicated "SAPSMPSVIL_OBMO_HttpdSync_20151125T085507.txt" I have these records

20151229T164507.598|1|(x-sup-sessid=dzp7i63qd9k) SetRequestComplete  request dropped due to Invalid request handle=246|||||5928

20151229T164510.579|1|(x-sup-sessid=dzp7i63qd9k) SetRequestComplete  request dropped due to Invalid request handle=251|||||6544

20151229T164515.172|1|(x-sup-sessid=dzp7i63qd9k) SetRequestComplete  request dropped due to Invalid request handle=259|||||8060

20151229T165332.327|1|(x-sup-sessid=1kpw5qghddbie) SetRequestComplete  request dropped due to Invalid request handle=5|||||3808

Any Idea ?

Thanks, regards.

[Former Member · Accepted solution]

Other things:

after Synch instruction I receive these status from SMP:

2015-12-29 17:12:12.636 xxxxxxxxx1[3320:1553608] onConnectionStatusChanged: status = 104, code = 0, message = (null)

2015-12-29 17:12:12.636 xxxxxxxxx1[3320:1553608] =================================================

2015-12-29 17:12:12.659 xxxxxxxxx1[3320:1554470] =================================================

2015-12-29 17:12:12.660 xxxxxxxxx1[3320:1554470] onConnectionStatusChanged: status = 105, code = 0, message =

2015-12-29 17:12:12.660 xxxxxxxxx1[3320:1554470] =================================================

2015-12-29 17:12:12.772 xxxxxxxxx1[3320:1554469] =================================================

2015-12-29 17:12:12.772 xxxxxxxxx1[3320:1554469] onConnectionStatusChanged: status = 105, code = 0, message =

2015-12-29 17:12:12.772 xxxxxxxxx1[3320:1554469] =================================================

[vfweiss · Accepted solution]

104 is disconnecting and 105 disconnected. You don't call a stop connection or so after sync?

I assume besides:

After the upgrade I have regenerate the source code from SDK2.3 for the App and I have updated the libraries necessary in Xcode project.

You have also redeployed the package? Did you do this in "upgrade" or "replace"? If upgrade I would suggest redeploying it in replace.

Besides what you already did there is not much else you have to change from 2.2 to 2.3.

If that doesn't work, I would up the logging and create a domain log config with everything enabled for your application connection.

The "SetRequestComplete  request dropped due to Invalid request handle" is something I am also seeing on our landscape in the logs, but the apps still run correctly.

[Former Member · Accepted solution]

Dear Vincent,

I have redeployed the package but I have the same problem: is impossible to synch. any data with backend. I don't receive any error message in Xcode console and in SMP Domain Log.

Could be a problem that I don't have import any certificate in the App ? In the standard help is indicated that if I use a relay server I need to import the relay server certificate into the App (with SUP2.2 this step was not required)

Do you know how can download this certificate from relay server ?

Thanks.

Regards.

[vfweiss · Accepted solution]

Hello Roberto,

I think that is only required if you are using HTTPS. At least we never imported one and are running with the default Relay server from Sybase (v16).

And it works at least for registering already for you, so the messaging based outbound enablers work at least. Maybe there is something with the Replication based ones?

Only difference that I can still see is that I don't have "trusted_certificates=;compression=none;" in my Networkstreamparams, only the url_suffix part.

I don't know what else it might be, I am sorry. Maybe best to start a new question detailing what you already investigated with this new problem, as the initial is already answered and you might get more help in a new one.

Best of luck