Unable to Access Analytics Plus in 3600/3700
Issue:
You may unable to access Analytics Plus console when your default web server port is set to 443.
It's identified as a bug which would affect both the existing and new users on builds 3600/3700.
Cause:
The builds 3600 and 3700 has an issue with the change in the architecture. The redirection to the authentication module internally has been disconnected due to this change.
Here is a temporary workaround to resolve the issue
1. Download the text file from the attachment.
2. Rename the file as 1.jar and place it under <Analytics Plus home>\lib folder
3. Restart Analytics Plus Services.
New to ADSelfService Plus?
Related Articles
Unable to access Analytics Plus after installation
Issue: Unable to access Analytics Plus after installation even though the wrapper logs are fine. Analysis: There is a space character after the port number in the URL construction. Log Traces: java.lang.IllegalArgumentException: Invalid uri ...Unable to sync between Servicedesk Plus and Analytics Plus - ATKey error
Issue: Unable to configure integration/sync between ServiceDesk Plus and Analytics Plus ERROR Message: FAILURE :Not able to get ATKey from Server. You can obtain the error log files from Support tab by clicking on the Support File link in the ...Unable to access the console in build 5120
Issue: Unable to access the console in build 5120 After upgrading Analytics Plus to build 5120 or fresh installation of build 5120, upon trying to login to the application, the page next to login screen would not load. Would throw the below error. ...License management page does not load as expected (due to license violation)
Issue: After license violation, the user will be unable to access the license management page. Identified it as a bug in the product (3950) (During License violation, the page will keep on loading without any response. This is due to some ...Unable to start or access the application after upgrading to 4600 or 4610
Issues: Unable to start or access the application after upgrading to 4600 or 4610 version. Case 1: The application fails to start. Case 2: The application is started successfully but couldn't access the UI. Root cause: A few files were missing in the ...
