Skip to main content
InSource KnowledgeCenter

TN Hist286 Historian Client Trend shows Nulls and Historian logger says "buffer overflow."

Description

 

Historian Client Trend shows Nulls and Historian logger says "buffer overflow."

  • Author: Mike Viteri
  • Published: 2/20/2018
  • Applies to: Historian 10.0 or greater

Details

When using Historian you will see a message below in the smc log viewer.

Server is too busy.

Buffer overflow.

historian.jpg

This error will cause data graps in your trend. The most likely reason you are seeing this issue is that a time sync is running and changing the historian clock time. This is especially true if you are running your Historian on Hyper-V or VMware. The way to fix this error is to not change the Historian time. Have all you clients sync their time to the Historian using net time. The attach technote explains how to setup net time.