[ISS Support Case] Unable to Connect to Logger

Last updated: March 6th, 2025

Description

Client reached out initially due to issue with Historian, but user was unable to open logger receiving the following error message: "Unable to connect to logger on 'Hostname'. If running on Windows Server 2003 SP1 or Windows XP SP2, verify that you have run the OS configuration Utility to ensure correct services login. This may have been caused by the logger Service having been shutdown possibly by a product being installed. The Microsoft Windows Data Execution Prevention (DEP) feature may also cause the problem. To disable DEP, add '/noexecute=AlwaysOff' to the Boot.ini file, then reboot."

Author: Kevin Modlin
Published: March 6th, 2025

Details:

Product: Historian

Version: 2020 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	10/02/2024
Case:	87938

Give feedback about this article

Recommended articles

[ISS Support Case] Historian loses connection after shutting down

If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.

[ISS Support Case] Trying to access old history blocks

They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.

[ISS Support Case] Trend SQL Login Failure

Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.

[ISS Support Case] Wanting to pull 9 months of historized data

-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.