AppWorx, Dollar Universe and Sysload Community

UC4 || Appworx Dev envirnoment is not opening and we are unable to login and are getting an Error :

RMI Connection failure

Regards,

Akbar

Is this a new instance/system?  If you go on the machine where the Application Manager is install, can you verify that the RMI is running? If it is not, then I would recommend starting it up.  If it is up and running but you are not able to connect to it (the questions would be, what has changed? or is this a new system trying to connect to for the first time?).  From just that error message alone is hard to tell you what the cause of it is without more info on the system.

Hi Lu,

PFA the updated screenshot:

AWE-5009 RMI connection failure

Please also find the attached error logs.

Thanks  & Regards,

Mohd Zain Akbar

Tools Team

ClubCorp IT Service Partner | HCL Technologies

Mobile No.: +91-844-700-1608

To log a ticket call IT Service Desk @ 972-888-7777

or Email @ hclit@service-now.com<mailto:hclit@service-now.com> / hcl-cc-tools@clubcorp.com<mailto:hcl-cc-tools@clubcorp.com>

Hi Mohd_Akbar,o 

The screenshot is only of it general message, I recommend in the future to take a picture once you clicked on the "Detail" button as it would give more info.

As for the file "rmi error logs.txt"  - Is this the info that show on the "Detail" button?  As from the information in it - it doesn't appear to be from the RMIServer log (as it have no timestamp or other information you would normally see in the rmi logs).

Were you able to check if the RMI is up & running on the system?  If it is up and running, on the rmi logs itself what were the errors (they normally accompany by other "AWE-_______" error within the logs).

That snip bit from your "rmi error logs.text" file is more or less a generic java exception and matches a few other customer reported previous, where we have had varying different method to fix the issue (as it would depend on the user scenario/situation).  

For example, we had users who had moved their "Master" to a new IP... or had change/utilized a lower port range which wasn't allow at their company.. 

As I am not go through your system and look at all the files to make sure the configuration is setup correctly or if the RMI is up and running...

It would help greatly... if you can:

A) Provide a little background for this system

1. Is the RMI currently up & running?
2. Was this a system that was previously working and then suddenly stop with this error?
3. Was there any recent change to the system (such as it being move/migrated or change to the IP)?
4. Is this system a copy/duplicate of another running system?

Hi Lu,

1. The RMI server is up and running.

2. This is an old sytem we have not changed the system

3. There has been no change to the system or ip address.

4. No this system is not copy of another system

Kindly do reply on priority.

Regards,

M Akbar

Hi Team,

Kindly let us know the further steps to be followed as we have already performed the above steps and still the issue is occuring.

Regards,

Mohd Zain Akbar

This isn't the Java update bug, is it?

If your client autoupdates the JRE, v8u201 removed support for anonymous TLS ciphers...the basic error you get is pretty generic but you can see the handshake fail if you enable SSL Debug.

That update came out January 15th, which seems to tie in with your original question date.