Who is this article for?

Users encountering a 404 server error message.

Server Access is required to investigate this further.

This article troubleshoots an issue encountered by users receiving the message "Server Error in '/' Application: The resource cannot be found, Description HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable..." when accessing Please Review. In this article, we'll outline the steps to investigate and resolve this problem effectively.

1. 1. Issue
   2. Resolution

1. Issue

A user may encounter the following error message: "Server Error in '/' Application: The resource cannot be found, Description HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable..." while accessing Please Review.

If the address entered is correct but Please Review isn't loading, it's likely because the application pool for Please Review has stopped. This directs users to the default site where Please Review files don't exist.

This could be happening due to scheduled maintenance, server relocation, or server decommissioning. If you have an on-premise installation, first check for these possibilities before attempting to restart the server in IIS. Restarting a server that's supposed to be moved can cause issues, as we want all new requests to go to the correct server. Contact those responsible for server management to ensure this is properly handled. If we host your server, our Implementation Teams can be contacted to verify any ongoing moves or changes.

2. Resolution

If the site should be running but isn't, verify if the application pool is running. If not, inspect the TaraWeb.log for startup errors. If there are no entries in the TaraWeb.log, check the Windows event log for any recorded issues.

Additionally, confirm that the TaraWeb.logging.config file in Runtime\config is configured to log correctly and that the system has write permissions to the log file. Ensure folder permissions for the user running the site are correct or grant full permissions to the IIS_IUSRS group for the runtime\data folder and its subfolders, especially if logging to the default location (runtime\data\log).

These steps should facilitate further investigation based on any errors encountered.