Unable to access Prognosis WebUI

[kashyap]

Hi Team,

I am unable to access the Prognosis WebUI, it was throwing an error, "You do not have permission to log in. Login failed. The username or password is incorrect". we are using the correct credentials.

We are able to access the prognosis desktop application with the same credentials.

Could someone please let me know, how to proceed further?

Thanks,

Kashyap.

[SCOTT_BALDWIN · Accepted solution]

Hi @kashyap,

The error seen can have several possible causes. One of the more common causes is the PrognosisPostgres service not running.

Please check to make sure the PrognosisPostgres service is running on the Web UI server.
If the service is running and the same error is seen, please open a Support Case for additional troubleshooting with one of the Support Engineers.

Thank you,
Scott Baldwin

[kashyap]

Hi @SCOTT_BALDWIN ,

Postgres service is stopped and when I tried to start the service I am getting the below error,

Thanks,

Kashyap.

[SCOTT_BALDWIN]

Hi @kashyap ,

Thank you for trying to start the sotpped PrognosisPostgres service. Unfortunately, the error returned from trying to start the PrognosisPostgres service is very generic like the error in the Prognosis Web UI.

Please open a Support Case so this the specific trouble in this environment can be examined.

Thank you,
Scott Baldwin

[kashyap]

Thank you @SCOTT_BALDWIN ,

Just need one more piece of information regarding prognosis licenses,

if we remove all devices from prognosis without uninstalling the application still the licenses will be consumed?

[SCOTT_BALDWIN · Accepted solution]

Hi @kashyap,

Licenses should only be consumed for devices that are monitored.

Additional information:

• If a Cisco Cluster is monitored, then all the endpoints associated with the cluster consume Licenses even if only the publisher is monitored or if the publisher, all subscribers and IM&P servers are all monitored.
• If the entire Cisco Cluster or Avaya CM is removed from monitoring, then the associated Licenses should be available again.

If you are are seeing something different, please open a Support Case for troubleshooting and resolution.

Thank you,
Scott Baldwin

[kashyap]

Thank you @SCOTT_BALDWIN , it cleared my doubts.