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. No Windows event log message text

No Windows event log message text

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 9.8k 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.
  • B
    B
    bdefloo
    wrote on last edited by
    #1

    Hi,

    I noticed a small problem on a number of nodes that have the NetXMS agent v1.2.4 installed.
    The Windows system event log shows messages like:

    The description for Event ID 23 from source NetXMS Win32 Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    
    If the event originated on another computer, the display information had to be saved with the event.
    
    The following information was included with the event:
    
    Counter set B is empty, collector thread for that set will not start
    
    the message resource is present but the message is not found in the string/message table
    

    instead of

    Counter set B is empty, collector thread for that set will not start
    

    Some googling led me to the registry key
    HKLM\System\CurrentControlSet\Services\Eventlog\system\NetXMS Win32 Agent\EventMessageFile
    which I found set to "C:\NetXMS\bin" rather than "C:\NetXMS\bin\nxagentd.exe". Changing it and restarting Event Viewer solved the problem on that node.

    Could this be a bug in the installer somewhere? I can't seem to pinpoint what version it exactly went wrong as I've upgraded through several versions of the agent, but I have just had the problem with a clean install of the x64 v1.2.4 agent on a Windows 2008 R2 server.

    Kind regards,
    bdefloo

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

      Hi!

      Yes, I've found a bug in event source installation code. It appears in 1.2.3, when agent was converted to UNICODE. I've fixed it in 1.2.5.

      Best regards,
      Victor

      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