Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Event Id 43 in Windows System Event Log

Event Id 43 in Windows System Event Log

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 23.7k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    L
    lbdecloedt
    wrote on last edited by
    #1

    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!! ???

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      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

      1 Reply Last reply
      0
      • L
        L
        lbdecloedt
        wrote on last edited by
        #3

        Ok, I will try this. Thanks for the quick response.

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups