Aomated Analytics - Error after authentication

[former_member186752]

Dear experts

I'm starting the Auomated Analytics - Remote Assistant 2.3 and I'm entering the server details(IP:12345) and the credentials.

The authentication is working but immediately after the authentication I'm getting the following error message:

"Connection with the Modelling Server could not be created
com.kxen.CommonInterf.Exception.KxenTimeoutException"

I can say close to dismiss the error message but all the SAP Predictive Analytics options will be greyed out.

Any ideas?

Cheers

M

[achab · Accepted solution]

Hi Marian,

What kind of authentication are you using? I would recommend that you create a support ticket in parallel to this thread.

Thanks & regards

Antoine

Side-note: the latest released version of SAP Predictive Analytics is 2.5.

[former_member186752 · Accepted solution]

Hi Antoine

It's normal authentication - >user and password.

The credentials are stored on the Server in the credentials file.

[achab · Accepted solution]

Hi, our Operations guide here: https://websmp208.sap-ag.de/~sapidb/012002523100004482292016E/pa25_operation_admin_en.pdf has a troubleshooting section.

I read on page 20:" Automated Analytics client cannot connect to the server

Try to reach the server from your client computer using the same name or IP address you use in your client application. The server could not be reachable because:

● IP Address or DNS hostname is unresolvable from your client computer.

● The server computer is not running. If the server is reachable, this error can be due to the fact that the Authserver is not started on the server computer. "

Page 19 describes the information to collect for the support team.

Thanks & regards

Antoine

[former_member186752 · Accepted solution]

Hi Antoine

But the thing is that I can connect to the server.

Authentication is also possible (tested with different users) and after authenticating the error is displayed.

Cheers

M

[abdel_dadouche · Accepted solution]

Hi,

Does your server has multiple IP addresses?

I have seen similar issues where the Authentication Server is trying to startup, and will start accepting connection, but as it's needs to connect to the Name Server, but can't (because it's trying on the wrong IP), then it will go down.

Can you share the ini & log files located in

     C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv

     C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Servers\AuthServer

and also if you can execute the following commands and send the output:

netstat -ano

ipconfig /all

Thanks

@bdel

[former_member186752 · Accepted solution]

Hi Abdel

The Server has only one IP address so no need to add the ipconfig /all output.

I've attached the netstat -ano.

Is there any specific file(exact name) that you want to check from the following locations:

C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv

C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Servers\AuthServer

I would then add a specific file rather than all the content of the mentioned folders.

Cheers

netstat.txt.zip

[abdel_dadouche · Accepted solution]

Hi,

I'm referring to the following files (all the ini and log files in the mentioned folders):

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv\KxNameOutput.log

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv\KxNameServerErrors.log

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv\KxServiceManager.log

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Namesrv\KxServiceManager.ini

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Servers\AuthServer\KxAuthOutput.log

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Servers\AuthServer\KxServiceManager.log

- C:\Program Files\SAP Predictive Analytics\Server 2.3\EXE\Servers\AuthServer\KxServiceManager.ini

Can you run:

      ping localhost

as well as

      telnet localhost 12345

      telnet localhost 12347

this will tell me which IP is return by your system for localhost and if your system is accepting connections from there.

Regards

@bdel

[former_member186752 · Accepted solution]

Hi Abdel

Ping localhost is working.

Telnet localhost 12345 -> I'm connected

Telnet localhost 12347 -> could not open connection to the hosts

The files can be found in the attachment.

Please rename the Files.txt to Files-zip and extract the content.

Files.txt.zip

[abdel_dadouche · Accepted solution]

Hi,

With the ping localhost, I wanted to check what is the name bounded with it.

For example on my system it returns

C:\Users\i304811>ping localhost

Pinging PARN31649621A.emea.global.corp.sap [::1] with 32 bytes of data:

Reply from ::1: time<1ms

Reply from ::1: time<1ms

Reply from ::1: time=1ms

Reply from ::1: time=1ms

In my case localhost is bound to [::1]. So in netstat I should see this addres [::1] bound with port 12345.

I think you are missing the license file:

     Error: E_SYSTEM__NOENT ../../../../License.cfg.

This file need to be placed in:

    C:\Program Files\SAP Predictive Analytics

And should include your key code like this:

KeyCode<tab>B7X60-0SY0800-4EMK100-0PP1

(the key displayed in this post is the temp key) with a tabulation in between.

Can you validate that you have set your key code properly?

Thanks

@bdel

[abdel_dadouche · Accepted solution]

Hi,

One more thing, can you open a support ticket to report this as a defect? This will help to increase the defect priority.

Regards

@bdel

[achab · Accepted solution]

I also started a discussion with engineering teams in parallel - could you please confirm the reason for your problem was the absence of the license code?

[former_member186752 · Accepted solution]

Hi Antoine

I confirm that the reason for the problem was the absence of the license key.

Thank you for raising this issue internally.

[former_member186752 · Accepted solution]

Hi Abdel

Thank you very much for the support!

In the near future we will update to the latest release.

If the problem will appear again we will open an incident.

Hope you agree with this.

[abdel_dadouche · Accepted solution]

You are very welcome.

As a best practice, and based on personal experience, I always try to diagnose the root cause of a problem before trying to change anything.

There are many steps before going for going for an upgrade, like testing the same version on a different machine, reinstalling the same version etc..

In my opinion, upgrading to a newer should only be driven by the fact that the root cause of your problem is fixed on the newer version or because you may want to leverage new features from that release.

And last but not least, opening a support incident is always a "must" as our support colleagues needs to track this kind of issues and report on any underlying defect to the development team.

Best Regards

@bdel

[former_member192509 · Accepted solution]

Hi Abdel,

Abdel, how can I generete the license key like : KeyCode<tab>B7X60-0SY0800-4EMK100-0PP1, because I can only generate the license for the modeler,

Regards,

Mario Mendoza

[achab · Accepted solution]

Hi Mario, please post a new question with the details. Thanks Antoine