<![CDATA[Event Id 43 in Windows System Event Log]]>I am getting these errors in the event log for selected nodes. Below are two of the messages I have seen.

Source: NetXMSCore      Event ID:43
Event Type: Error
Event Source: NetXMSCore
Event Category: None
Event ID: 43
Date: 1/14/2009
Time: 10:16:03 AM
User: N/A
Description:
SQL query failed (Query = "INSERT INTO idata_1734 (item_id,idata_timestamp,idata_value) VALUES (1324,1231946163,'HP NC373i Multifunction Gigabit Server Adapter #232')"): General SQL Server error: Check messages from the SQL Server.

Event Type: Error
Event Source: NetXMSCore
Event Category: None
Event ID: 43
Date: 1/14/2009
Time: 10:16:03 AM
User: N/A
Description:
SQL query failed (Query = "INSERT INTO idata_1734 (item_id,idata_timestamp,idata_value) VALUES (1532,1231946163,'0')"): General SQL Server error: Check messages from the SQL Server.

It appears to be an issue inserting the date into the MSSQL database, but I am not sure why. Yesterday the system log had no errors.

I am running version 2.22 for both server and agents; on Windows Server 2003 SP2 with SQL Server 2005. With 107 nodes being monitored most which are not connected to the network at this time.

Has anyone run into this issue or can provide any insight into this issue?

Thanks in advance!! ???

]]>https://forum.netxms.org/topic/587/event-id-43-in-windows-system-event-logRSS for NodeFri, 13 Nov 2026 07:26:14 GMTWed, 14 Jan 2009 16:55:35 GMT60<![CDATA[Reply to Event Id 43 in Windows System Event Log on Wed, 14 Jan 2009 20:59:59 GMT]]>Ok, I will try this. Thanks for the quick response.

]]>https://forum.netxms.org/post/2851https://forum.netxms.org/post/2851Wed, 14 Jan 2009 20:59:59 GMT<![CDATA[Reply to Event Id 43 in Windows System Event Log on Wed, 14 Jan 2009 19:50:15 GMT]]>Hello!

Below are some possible reasons:

  1. Lost database connection.
  2. Heavily corrupted database, where some tables for collected data (like idata_1734) does not exist.
  3. Clock shift on server - if clock shifted back, server occasionally may try to write collected data with already existing timestamp.

You can try to run failed query in SQL query analyzer - it should give more diagnostic output.

Best regards,
Victor

]]>https://forum.netxms.org/post/2850https://forum.netxms.org/post/2850Wed, 14 Jan 2009 19:50:15 GMT