Standalone Orchestrator Detailed Logs Location

Help Orchestrator
,
1

Im using Orchestrator Trial Version, Installed on AWS EC2 via Windows Installer, not AWS Deployment.

I cannot find the detailed logs of the Application, i can only see the logs from IIS
but it only logs like
2023-06-16 01:49:17 GET /favicon.ico - 443 - /host/tenants 500 30 2147500037 2

Where do i see the detailed logs of why “/host/tenant” failed instead of showing only internal server error.
Thanks

2

Try to access as Administrator the log file(s) from this location %SystemRoot%\System32\LogFiles\HTTPERR

%SystemRoot%\System32\LogFiles\HTTPERR is the default directory for storing HTTP.sys error logs in IIS. These logs capture the HTTP-level errors, which are usually related to network connectivity, timeouts, and the non-functioning state of the application pool.

To view the HTTP.sys error logs:

  1. Open Windows File Explorer.
  2. Navigate to %SystemRoot%\System32\LogFiles\HTTPERR folder. Typically, %SystemRoot% is located at C:\Windows.
  3. You will see log files in the HTTPERR folder, named in the format “httperr-date.log.” Open the relevant log file using a text editor or a log file viewer like Notepad++ or Tail.

These logs will provide you with the details of errors related to HTTP-level issues. If the error you’re trying to troubleshoot is not in these logs, you should look into the application’s logs or other logging options mentioned earlier in the IIS Manager.

Remember that the level of detailed information in these logs depends on your IIS configuration, so you may need to enable more detailed logging if you still can’t find the information you need.

To see the detailed logs of why “/host/tenant” failed, you need to enable detailed error logging and/or application-level logging in your application or web server.

Here are the steps for enabling detailed error messages and application-level logging in an IIS environment:

  1. Open the Internet Information Services (IIS) Manager.
  2. Navigate to the server level or to the specific application or site in the tree view.
  3. Double-click on the “Error Pages” feature.
  4. In the Actions pane, select “Edit Feature Settings…”
  5. Choose “Detailed errors” or “Detailed errors for local requests and custom error pages for remote requests” depending on your needs. Click “OK”.

Next, enable application-level logging:

  1. In the IIS Manager, navigate to the server or application level.
  2. Double-click on the “Logging” feature.
  3. Make sure the “Enable” checkbox is checked.
  4. Under “Log Event Destination,” select “Both log file and ETW event” or whichever destination you prefer.
  5. Choose a format for the log files, such as “W3C” (recommended) or “IIS.”
  6. Customize fields, directory path, and time period for the log files as needed.
  7. Click “Apply” in the Actions pane to save the settings.

After these changes, IIS should provide more detailed logs on errors. You may also check the application’s error handling or logging settings and make sure it is configured to log errors in detail.

Additionally, make sure to look into the Windows Event Viewer logs, as some application-level errors can be found under “Windows Logs” → “Application” section. You might find more details about the internal server error there.

1 Like