General Troubleshooting Steps

If you encounter an issue with EmpowerID, follow the below troubleshooting steps for each relevant category. Start with step one and progress to the next step if the issue does not resolve itself.

You can log in to the Web portal, but are experiencing issues

Follow the below steps if you can log in to the Web portal. Start with step one and progress to the next step if the issue does not resolve itself.

Check the event log for errors. If errors are present, you may be able to resolve the issue based on the error information.
Check to ensure the proxy account being used is not locked out and that the password has not recently changed and that the domain controllers are accessible from the EmpowerID servers.
If you recently made any customizations to the application, temporarily roll those changes back to see if that resolves the issue.
If the issue still exists, enter a support ticket in JIRA stating the problem and provide any relevant logs or steps you have already attempted. Please indicate if you are facing a problem with just one workflow or useror if the entire application is down.

You cannot log in to the Web portal

Follow the below steps if you cannot log in to the Web portal. Start with step one and progress to the next step if the issue does not resolve itself.

Try to access the UI from another computer or another compatible web browser and another EmpowerID server to see if the issue is isolated to one EmpowerID server. If you do not have another web browser, try to browse the site using incognito or private mode.
Check the Windows services and IIS application pools to ensure they are running.
Ensure the EmpowerID database server is accessible, that the database is online and the identity running theEmpowerID Windows services and IIS application pools has dbo access to the EmpowerID database.
Ensure that the identity being used for the EmpowerID Windows services and IIS application pools is enabled andthat the password has not been recently changed.
Restart all EmpowerID Windows services and perform an IIS reset on all servers.
Turn UAC off and ensure "Behavior of the elevation prompt for administrators in the Admin Approval Mode" is disabled.Also ensure that the identity set on the EmpowerID Windows services and IIS application pools is a localadmin.
Make sure the federation and SSL certificates are still valid and chained properly on each EmpowerID server.
Check to ensure the proxy account being used is not locked out and that the password has not recently changedand that the domain controllers are accessible from the EmpowerID servers.
If you recently made any customizations to the application, temporarily roll those changes back to see if thatresolves the issue.
If the issue still exists, enter a support ticket in JIRA stating the problem and provide any relevant logs orsteps you have already attempted. Please indicate if you are facing a problem with just one workflow or useror if the entire application is down.