Am 9.2.2. upgrade login issue

[Chris Fonger]

updated AM to 9.2.2 from 9.1.x and not not able to login

 

I am getting this error message when trying to connect. I have updated java on the master server as part of the upgrade.

I am using my local pc to connect, the server gives the same message as well. any advice would be much appreciated.

 

 

java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine

                at java.net.DualStackPlainSocketImpl.connect0(Native Method)

                at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)

                at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)

                at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)

                at java.net.AbstractPlainSocketImpl.connect(Unknown Source)

                at java.net.PlainSocketImpl.connect(Unknown Source)

                at java.net.SocksSocketImpl.connect(Unknown Source)

                at java.net.Socket.connect(Unknown Source)

                at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)

                at sun.security.ssl.SSLSocketImpl.<init>(Unknown Source)

                at sun.security.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source)

                at com.appworx.client.screen.util.ClientSocketManager.A(ClientSocketManager.java:250)

                at com.appworx.client.screen.util.ClientSocketManager.connect(ClientSocketManager.java:315)

                at com.appworx.client.screen.util.Loader.setMaster(Loader.java:936)

                at com.appworx.client.screen.logon.C.ń(Logon.java:230)

                at com.appworx.client.screen.main.AxMain.A(AxMain.java:2251)

                at com.appworx.client.screen.main.AxMain.main(AxMain.java:2864)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

                at java.lang.reflect.Method.invoke(Unknown Source)

                at com.sun.javaws.Launcher.executeApplication(Unknown Source)

                at com.sun.javaws.Launcher.executeMainClass(Unknown Source)

                at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)

                at com.sun.javaws.Launcher.run(Unknown Source)

                at java.lang.Thread.run(Unknown Source)

[Kristopher Thomas]

The error message:

java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine

 is a generic java error which can be caused for multiple reasons. I see you have opened a support case for the issue. I will up through the support case, and update this community post once a solution is derived.

Thanks,

Kristopher

[Kristopher Thomas]

This issue was caused by the Applications Manager java process not full starting. In the AgentService log the following error was discovered….

 

ErrorMsg: AwE-9999 Internal error (7/23/18 2:20 PM) 
Details: nativecalls 
java.lang.UnsatisfiedLinkError: E:\Automic\Master\c\nativecalls.dll: %1 is not a valid Win32 application 

 

This was due to the Applications Manager processes attempting to start with a 32 bit JRE. With Applications Manager 9.2.2 and above a 64 bit jre is required. Although 64bit java was installed on the system, Applications Manager was picking up a 32 bit jre from the system directory. The java.exe and javaw.exe files in the C:Windows\System32 and C:Windows\SysWOW64 are dummy files. Meaning that will execute whatever Java is indicated in the 'HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion' registry variable. This is the design of windows servers. To override this, we removed the java.exe and javaw.exe from the windows SysWOW64 and System32 directories. Once removed we modified the windows %PATH% environment variable to include the full path the 64 bit jre’s bin directory. After this was done the processes fully started with 64-bit java and we were able to login.