cancel
Showing results for 
Search instead for 
Did you mean: 

SMP 3.0 Development Landscape - Error 14

Former Member
0 Kudos

Hi All,

I followed this blog to set up my SMP 3.0 Development Landscape:

http://scn.sap.com/docs/DOC-56329

Everything seems good to me. I was able to deploy Work Manager 6.1 base app on the SMP 3.0 Server and the startup logs had no error.

I have installed both the SMP Server and ATE on my laptop.

When I try to access the URL: https://localhost:8081/SAPWM in Chrome, I get this message:

The site's security certificate is not trusted!

You attempted to reach localhost, but the server presented a certificate issued by an entity that is not trusted by your computer's operating system.

But when I click 'Proceed Anyway' - I get the 'I am here!' message.

The problem I am facing is in ATE - When I give https://localhost:8081/SAPWM in the Server in ATE, I am getting a Communication Error 14 message. I even tried given my FQDN of my laptop in that URL. It didn't work.

I am not sure what exactly can be the issue. It might be something to do with the certificate. I followed what was mentioned in the blog.

Regards

Ankur

Tags edited by: Michael Appleby

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

You are getting an error(14) because teh client isn't able to find the servers certificate. 

You need to install the Certificate <platform>\Server\Configuration\smp_crt.cer file into the Trusted Root store.

Former Member
0 Kudos

I installed the certificate as described in that blog under Trusted Roots.

now when I access the URL: https://localhost:8081/SAPWM in Chrome, I get this message: You attempted to reach localhost, but instead you actually reached a server identifying itself as <<my computer's FQDN>>.

And in ATE now I get this error:

Requesting Public Key from Server

Connect to server 'localhost', certificate is for 'my computer's FQDN', so it is not valid

Communications error (14)

Connection failed

Ending transmission

Former Member
0 Kudos

You need to use the FQDN for the server address instead of localhost.

Stephen

Former Member
0 Kudos

When I do that, the webpage doesn't load. And the ATE says, unable to resolve host.

Former Member
0 Kudos

Do you have a firewall on the machine?  It maybe blocking the connection from the client.

Stephen.