Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hi,

I have installed SMP 2.3 SP03 L01 and have deployed the Work Manager 6 application on the server. My Agentry.ini and JavaBE.ini files seem okay. Self-Signed certificates were used properly as mentioned in the guides. connectTest.bat executes correctly, thus showing SAP backend information. The Work Manager agentry application starts correctly from SMP.

However, now that i want to test the application, I'm unable to connect to the server. The WPF and ATE errors are as below:

Can somebody help me out with these errors?

Tags edited by: Michael Appleby

0 Likes

Know the answer?

Help others by sharing your knowledge.

Answer

Need more details?

Request clarification before answering.

Show replies
Show replies
View Entire Topic
bill_froelich
Product and Topic Expert
Product and Topic Expert
‎2014 Mar 20 2:13 PM
0 Likes

Did you install the certificate on the machine running the WPF and ATE clients?

--Bill

Show replies
Show replies
Former Member
‎2014 Mar 21 1:28 AM
0 Likes

Yes Bill, my WPF and ATE are working fine now. My issue is with the Android client.

bill_froelich
Product and Topic Expert
Product and Topic Expert
‎2014 Mar 22 7:13 PM
0 Likes

Sreyan,

Did you install the certificate on the Andorid device?  I'm trying to do that myself now but can't seem to get my device to take the certificate.  I will try again on Monday with a different device.

It should be essentially the same process.  Install the certificate on the device and it should show up under Settings -> Security -> Trusted Credentials -> User.   Then try to connect from your client as normal.

--Bill

Former Member
‎2014 Mar 24 3:52 AM
0 Likes

Hi Bill,

As I mentioned earlier, I'm using an emulator for the client. I have successfully installed the certificate, and it shows under Settings -> Security -> Trusted Credentials -> User too.

The client still refuses to accept the credentials though. It is unable to resolve the hostname.

Former Member
‎2014 Mar 24 4:57 PM
0 Likes

What version of Android are you using?

There was a known issue where the OD wouldn't recognize host names in a local domain.

Issue 8030 - android - Not recognizing hostnames on local domain - Android Open Source Project - Iss...

This issue was resolved in Android 4.4

Former Member
‎2014 Mar 25 5:18 AM
0 Likes

I'm using Android 4.2.2.

I went through the thread and tried with 4.4. The Agentry client simply force closes.

bill_froelich
Product and Topic Expert
Product and Topic Expert
‎2014 Mar 27 3:08 PM
0 Likes

I have been unable to get my Agentry 6.1 generated certificates to load on either of my Android devices still to test myself.  I have been successful with my SMP3 certificates so I must have soemthing wrong in my process and will have to investigate further when I have some free time.

--Bill

tahir_z
Contributor
‎2014 Apr 01 8:52 AM
0 Likes

Hi Bill,

I also have problem on running my Agenrty 6.1 client in android devices. It works in ATE and WPF. I have installed cert to device and can see in Trusted Certificates.

The error i am getting is : "SSL Signature Verification Failure, Communication Error (14)".

Only in Agentry 6.1.3.2001 client version it runs fine. Either it does not see the certifcate or does it have any other thing that i missed.

Kind Regards

Tahir

Ask a Question