HTTP Status 404" Error Occurs within the Forcepoint Security Manager
Issue : "HTTP Status 404" Error Occurs within the Forcepoint Security Manager.
Action taken:
1. Observed that the issue occurred post patch update on the server.
2. Stopped the services on the server in below order and started again, but still the issue persists.
- Websense TRITON Web Security
- Websense TRITON Unified Security Center
- Websense TRITON Web Server
- Websense TRITON Settings Database
3. We modified and repaired the Forcepoint infra but dint work.
4. We have uninstalled the Forcepoint infra and rebooted the server.
5. Installed the Forcepoint Infra and restored the backup.
Now we are able to launch and see the console of Forcepoint Web and DLP.
As the issue resolved, we are archiving the case for now. Kindly open a new case for any other issues
Restarting the Manager's services may resolve the module's access.
- Open Services by running the following command: services.msc
- Stop the following services in the order shown below:
- Websense TRITON Web Security
- Websense TRITON Unified Security Center
- Websense TRITON Web Server
- Websense TRITON Settings Database
- Start the following services in the order shown below:
- Websense TRITON Settings Database
- Websense TRITON Web Server
- Websense TRITON Unified Security Center
- Websense TRITON Web Security
- Wait for the services to fully start. You should now be able
to connect to the Manager. If not, close the browser completely and then
try connecting again.
If the connection issue to the Manager persists after restarting the services, complete the steps below:
- Launch the Forcepoint Setup file. If the installer is not on the server, you may download it from here. When downloading the installer, ensure the version matches your current installation's version.
- Click Modify next to Infrastructure.
- Click Repair on the next screen.
- Click Next until complete, then click Finished.
If repairing Forcepoint
Infrastructure does not resolve the issue, it is possible that a Windows
update may have affected the server to cause an HTTP Status 404 error.
To re-initialize Forcepoint Infrastructure, SQL credentials will be necessary:
- Launch the Forcepoint Setup file. If the installer is not on the server, you may download it from here. When downloading the installer, ensure the version matches your installation.
- Click Modify next to Infrastructure
- Click Modify on the next screen
- Click Next until asked for the SQL login
- Enter the SQL administrator User Name and Password used to connect with write permissions to the databases.
- Click Next until complete, then click Finished
If the issue continues to persist, please raise a case with Technical Support.
Important The steps below are for Data deployments on version 8.6 and above only. For previous versions or if Web is part of the deployment, follow the instructions above.
- Access the Forcepoint Security Manager server.
- Open Services by running the command: services.msc
- Disable and stop the Websense TRITON Unified Security Center service
- Navigate to Websense\EIP Infra\tomcat\webapps
- Move the manager folder to the desktop.
- Enable and start the Websense TRITON Unified Security Center service
- Confirm that a new manager folder has populated in Websense\EIP Infra\tomcat\webapps
- Log back into the Forcepoint Security Manager
- Launch the Forcepoint Setup file. If the installer is not on the server, you may download it from here. When downloading the installer, ensure the version matches your installation.
- Click Modify next to Infrastructure
- Click Repair on the next screen.
- Click Next until complete, then click Finished
If repairing the infrastructure
does not resolve the issue, it is possible that a Windows update may
have affected the server to cause an HTTP Status 404 error.
To re-initialize Infrastructure, the SQL admin or "sa" login will be necessary:
- Launch the Forcepoint Setup file. If the installer is not on the server, you may download it from here. When downloading the installer, ensure the version matches your installation.
- Click Modify next to Infrastructure
- Click Modify on the next screen
- Click Next until asked for the SQL login
- Enter the SQL administrator User Name and Password used to connect with write permissions to the databases.
- Click Next until complete, then click Finished
If the issue continues to persist, please raise a case with Technical Support.