Windows NT4.0 SNMP subagent

From: Howard (anonymous_at_discussions.microsoft.com)
Date: 07/02/04

  • Next message: Eugene Gershnik: "Re: Network Connection" 
    Date: Thu, 1 Jul 2004 23:48:58 -0700

    sorry for the duplicated message.

    I have a problem when deploying a SNMP subagent on Windows
    NT4.0 workstation. I used Windows SNMP Extension API to
    wrap a 3rd party library. The subagent runs well on
    Windows XP and 2k. But on Windows NT4.0, the SNMP service
    is always complaining "ignoring extension agent dll
    c:\work\test.dll because it is missing or misconfigured"

    what I did
    1. update the registry

    2. set the path environment variable to include c:\work,
    where all the dlls are located
    I'm very sure these 2 steps are correct. ( the first time
    I got error message when restarting SNMP service - "some
    dll are missing from path" . After I copied all the dlls
    into c:\work, there is no error message )

    3. restart the service, from the event log, I found the
    error messages

    What I guessed
    1. MS SNMP Extension API change from NT4.0 to 2k and XP ?
    2. some functions not supported on NT4.0 . But I compiled
    a master agent based on the same sources, and it runs
    well ?
    3. any dll fail? but the master agent is running well

    Any suggestions ? how to troubleshooting ? any log files
    beside event log ? any input shall be greatly appreciated

    thanks
    howard

  • Next message: Eugene Gershnik: "Re: Network Connection"

    Relevant Pages

    • Re: .Net packaging/wrapper application?
      ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Unnown process... 5eplorer.exe
      ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings. ... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ...
      (microsoft.public.win2000.general)
    • Re: WinSxS, functional under 2k ?
      ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
      (microsoft.public.win2000.general)
    • Re: Determine name and path of dropped object?
      ... MDE I would really suggest the use of external DLL to hold the subclassing ... windows after loading the Microsoft Office Visual Basic Editor, ... Public Declare Sub DragAcceptFiles Lib "shell32.dll" _ ...
      (microsoft.public.access.modulesdaovba)
    • Re: .Net packaging/wrapper application?
      ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. ... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ...
      (microsoft.public.dotnet.framework.aspnet)