SMP 3.0 with SP3 AgentryApp is not Connecting from Client : Communications error (14)

[Former Member]

Hello,

In SMP 3.0 : Version 3.0.2, SP Level:02, my Agentry App : Work Manger 6.0 is working fine, it is running from device and running properly. After i migrate my SMP3.0 from SP02 To SP03, it is not connection from Any Device,(it is not showing any Error in Log file, Means App deployed successfully.) whenever we try to connect from Any device it is showing following Error Message.

Requesting Public Key from Server

Communications error (14)

Connection failed

Ending transmission

??? :  Is there any other confugration need to do in SMP 3.0 : SP03???? please help on this Issue...

Thanks

Krishna

[Former Member]

From the Logs you have on the Support ticket I we see:

12:09:54 06/19/2014: Event: 0, 2, Error loading cryptography keys: Unable to open or read a keystore: Object already exists.

You where informed to look at SAP Note: 2008882

[Former Member]

Hello Steve,

i go through the SAP Note 2008882. based on that Note i run the following

command.

C:\windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -pa

"C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.serv

er.agentry" smpServiceUser.

Now that Error is Gone from Log file but still it is not allowing to

connect. Even from ATE also.

Event Log File :

06/19/2014 17:54:00, 0,         0,         0, Thr       3192, New files opened events.log, messages.log

06/19/2014 17:54:00, 0,         0,         2, Thr       3192, Loading the Agentry Runtime's public/private key for password exchanges.

06/19/2014 17:54:01, 0,         0,         2, Thr       3192, Upgraded the Agentry key pair from pre-SP03 format

06/19/2014 17:54:01, 0,         0,         2, Thr       3192, Key pair loaded successfully.

06/19/2014 17:54:01, 0,         0,         2, Thr       3192, Agentry Startup

06/19/2014 17:54:01, 0,        17,        14, Thr       3192, WebSockets Front End v7.0.3.205

06/19/2014 17:54:01, 0,         1,         4, Thr       3192, Agentry Server Agent v7.0.3.205

06/19/2014 17:54:01, 0,        20,       150, Thr       1656, Loading Development application definitions

06/19/2014 17:54:07, 0,        24,         4, Thr       1656, Loaded HTTPXML-HTTPXMLSystemConnection (HTTPXML v7.0.3.205) from ag3httpxmlbe.dll

06/19/2014 17:54:07, 1,         3,         9, Thr       1656, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

06/19/2014 17:54:07, 1,         3,         9, Thr       1656, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

06/19/2014 17:54:07, 1,         3,         9, Thr       1656, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

06/19/2014 17:54:07, 1,         3,         9, Thr       1656, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

06/19/2014 17:54:20, 0,        23,         4, Thr       1656, Loaded Java Back End (Java v7.0.3.205) from ag3javabe.dll

06/19/2014 17:54:20, 0,        20,       152, Thr       1656, Loading Development application definitions for default localization

06/19/2014 17:54:20, 0,        20,       153, Thr       1656, Finished loading Development application definitions for default localization

06/19/2014 17:54:20, 0,        20,       151, Thr       1656, Finished loading Development application definitions

06/19/2014 17:54:21, 0,        20,         4, Thr       3192, Server v7.0.3.205

06/19/2014 17:54:21, 0,        17,        10, Thr       3192, WebSockets Front End v7.0.3.205

06/19/2014 17:54:21, 0,         0,         0, Thr       3192, Old log files moved into C:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-06-19-175400

06/19/2014 17:54:21, 0,         0,        23, Thr       3192, Agentry startup is complete.

Thanks

Krishna

[bill_froelich]

Krishna,

The errors you are seeing are due to you not using the Management Cockpit to setup the backend connection information but instead it appears you cut and pasted the Java-x section from an older Agentry server into your new SMP 3.0 Agentry.ini.

There are a number of keys in the Java section that are no longer valid under SMP 3.0 and the error is simply indicating it found an invalid key (initialHeapSize, maxHeapSize, reduceOSSignalUse, nonStandardJavaOptions).  You should remove those from your Agentry.ini and restart the server and the errors will go away.

--Bill

[Former Member]

Hello Bill,

Thanks you very much for your reply. Based on your instructions Error gone, but unfortunately Still my Agentry App is Not connecting from Client/ Device.. Still same Error Message i am getting in Client .

Requesting Public Key from Server

Communications error (14)

Connection failed

Ending transmission

Thanks

Krishna

[Former Member]

What is the url you are using for the clients?

Can take that url to a web browser and get "I am Here"

Stephen Streeter

[Former Member]

Hi ,

i am getting "i am here" Message from Server URL. with out any errors

https://smp-3:8081/SAPWM

Thanks

Krishna

[Former Member]

You need to make sure you the FQDN name.  The smp_cert.cer that is at "<plaform>\Server\configuration\" should show "Issued to"  you will want to use that value.

Stephen

[Former Member]

i generate the Certificate on the Same Name Only. Still we are getting same Error....

Thanks

Krishna

[bill_froelich]

What client are you trying to use to connect to the Agentry server?

--Bill

[Former Member]

Hi Bill,

we try with ATE, Windows Agentry Client, Android TAB. we are using the Same devices what before Migration also Use. in Previous Version (SMP 3.0 with SP02) all devices are connecting properly after migrating No device are Connecting...

Thanks

Krishna