Known Issues Web Reader

Issue: The web app starts but errors when visiting any of the pages.

Possible Cause

Your app settings file is invalid or is not being loaded.

Suggestions

• Check the log file (see the Application Logs page for more info) for the root cause.

• If nothing is found, increase the logging level to Debug and turn on Detailed errors (see Logs page for more info) and retry. The log file should have more information now and potentially the root cause.

• Open developer tools in your browser and reload the page. The console may show the root cause if Detailed Errors is enabled.

Issue: No response from website, receive error page or different page when trying to visit site.

Possible Causes

.NET is failing to start or run the site because:

1. The port (default: 80) is already being used.

2. The service cannot start because the correct .NET runtime is not installed.

Suggestions

• Use a different port, please see Configuration and Diagnostics to make a change.

• Startup failures (if .NET can even run) should be logged to the CommonApplicationDataFolder which is usually C:\ProgramData\FastClose\ReaderWebAppServer\Logs

• Have you installed the correct .NET runtime files and restarted IIS if applicable?

• Restart the Reader web app service, especially after making configuration changes.

• If you open a command line within the install folder and run FastClose.WebReader.exe you will see logging and exception data in the command line.

Issue: Service fails to start and/or install.

Error logs show: An attempt was made to access a socket in a way forbidden by its access permissions

Possible Cause

Something using or blocking the port, likely IIS.

Suggestions

• Restart the Windows Firewall Service

• Reboot the Server

• In a command console window try: Restart-Service hns before retrying the installer.

• Use IIS rather than hosting as a service.

Issue: When using the Reader embedded within Nextworld: drill through does not work in macOS or iOS. A new tab is opened but the user is not logged in.

Possible Cause

macOS and iOS have blocked cross-site tracking on the browsers or the device. Safari engine is used under the hood despite what browser the user chooses.

Suggestions

• Disable 'Prevent Cross-Site Tracking' on your device/safari settings.

• Disable 'Block Pop-ups' on your device/safari settings.

iOS - Safari

iOS - Chrome

For Chrome you must enable cross-website tracking.

macOS