Unable to access Analytics Plus after installation
Issue:
Unable to access Analytics Plus after installation even though the wrapper logs are fine.
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 'https://localhost:8443/ /iam/apiauthtoken/nb/create': invalid port number
Solution:
1. Stop the Analytics Plus services.
2. Execute changeHostPort.sh 8443 from <Analytics Plus Home>/bin
3. Clear the logs and start the services.
New to ADSelfService Plus?
Related Articles
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 ...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. ...Move Analytics Plus from one Server/folder
Go to Start --> Services.msc and stop the ManageEngine Analytics Plus service. Take a backup of the entire <Analytics Plus_Home> directory and then move it to the new server. On the new server, navigate to (similar path) <Analytics Plus_Home>\bin ...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 ...Analytics Plus Inventory
Aim: To have the detailed list of all the Reports, Databases created in Analytics Open Local & Cloud Databases and fill the entries password = Postgres and if any error occurs stating something like "check the DB connection" change the Port to ...