• State Not Answered
  • Replies 2 replies
  • Subscribers 12 subscribers
  • Views 165 views
  • Users 0 members are here
Options
Related

Historian Event Storage Unknown exception caught [HistorianServerName; EventStorageDispatcher.cpp; 650]

Joris

Hi everyone,

Since upgrading to the latest version of Historian (23.1.001.000), I’ve been encountering the following error message every time I stop (shutdown and disable) and restart the Historian service:

Historian Event Storage: Unknown exception caught
[HistorianServerName; EventStorageDispatcher.cpp; 650]

The major issue is that SQL dump files are being generated every second, quickly filling up the Windows C: drive.

Has anyone else experienced this issue?
Any suggestions on how to resolve it?

At the moment, the only workaround I’ve found is to restart the entire server to get things back to normal.

Thanks in advance for your help!

Joris

Parents
  • 0

    There were similar errors reported against Historian 2017, but those have been resolved in later releases (and a hotfix available for 2017). Please reach out to Tech Support with details about the configuration and when you see this--more specifically, is it only on shutdown or is it continuously every second (the post above mentions both)?

    Also consider what the query workload is like, particularly as it relates to the shutdown/restart. For example, is it likely some SQL client is continuously querying during the shutdown process? That could be a factor in the dump files.

Reply
  • 0

    There were similar errors reported against Historian 2017, but those have been resolved in later releases (and a hotfix available for 2017). Please reach out to Tech Support with details about the configuration and when you see this--more specifically, is it only on shutdown or is it continuously every second (the post above mentions both)?

    Also consider what the query workload is like, particularly as it relates to the shutdown/restart. For example, is it likely some SQL client is continuously querying during the shutdown process? That could be a factor in the dump files.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.