There is likely a problem with Apache Tomcat on this system. Support would best be able to help you with this, so I'm glad to see you have a ticket open.
The HTML5 UI may still work since it doesn't rely on Tomcat. You can try logging in by browsing to /aui on the Avamar server.
Just a follow-up to the issue I was having: Aside from using /aui to be able to administer the device, I was able to use WinSCP to download the avamar administrator client .exe file from the Avamar to my system, then, once I installed it, am now able to use both the updated version of the Avamar Administrator Client and the Administrator Web gui.
ionthegeek
2 Intern
•
2K Posts
1
December 7th, 2020 12:00
There is likely a problem with Apache Tomcat on this system. Support would best be able to help you with this, so I'm glad to see you have a ticket open.
The HTML5 UI may still work since it doesn't rely on Tomcat. You can try logging in by browsing to /aui on the Avamar server.
SRHunter
4 Posts
0
December 7th, 2020 13:00
Thanks! That's a step in the right direction. I'd like to get the Avamar Administrator client up, but for the time being, I think this should work.
I think I tried to get to the /aui earlier today, but I had the port number in there and that may have thrown it off for some reason.
SRHunter
4 Posts
0
December 9th, 2020 11:00
Just a follow-up to the issue I was having: Aside from using /aui to be able to administer the device, I was able to use WinSCP to download the avamar administrator client .exe file from the Avamar to my system, then, once I installed it, am now able to use both the updated version of the Avamar Administrator Client and the Administrator Web gui.