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. Failed to set ODBC version AFTER several hours

Failed to set ODBC version AFTER several hours

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 14.4k 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.
  • C
    C
    civieroc
    wrote on last edited by
    #1

    Sorry I'm new... I Have the same same same problem of this topic:
    General Support / ODBC.Nxagentd: 1.2.2 (I'm not able to write there, is closed?)

    The agent will run successfully however at the moment the ODBC subagent seems to stop after around 12 hours or so..

    [05-Nov-2014 08:26:26.535] ODBC connect error: Failed to set ODBC version ([Micr
    osoft][SQL Server Native Client 11.0]TCP Provider: Timeout error [258]. )

    Restart of the Nxagent service sucessfully resolves the issue until the same error will return.

    Thanks for all and for your beautiful program!

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

      Hi,

      I recommend you to switch to DBQuery subagent as ODBC subagent is deprecated. It is very similar but allows using DB drivers (as server do) so you can avoid ODBC altogether. Configuration is described here: https://www.netxms.org/documentation/adminguide/subagents.html#dbquery.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • C
        C
        civieroc
        wrote on last edited by
        #3

        Yes I know DBQuery subagent and I tried it, but it doesn't work with the DB SQL server 2012 of the agent.. give me an error about the driver.. if you want I can post it....

        ...and so I use ODBC that works fine until the error that I write up in this post.

        thanks

        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