An older posting had same issue. Microsoft replied, but
their suggestion did not work. Any other thoughts (other
than wiping windows and starting over).
Thanks,
Gregg
>-----Original Message-----
>I have seen this happen when the SNMP binaries are
replaced by another
>application. Use sfc /scannow in a cmd window to replace
swapped system
>binaries or check in the WINNT and WINNT\system32
directories and verify
>snmpapi.dll and wsnmp32.dll are from microsoft.
>
>I have also seen where a the WINNT directory is inserted
into the path
>before system32 and the application throws their snmpapis
into WINNT.
>--
>Alan Morris
>Windows Printing Team
>Search the Microsoft Knowledge Base here:
0:004> k
ChildEBP RetAddr
00caf3fc 77f4318f SharedUserData!SystemCallStub+0x4
WARNING: Stack unwind information not available. Following frames may be
wrong.
00caf44c 77c5874f ntdll!NtRequestWaitReplyPort+0xc
00caf834 73071dca RPCRT4!I_RpcSendReceive+0x1f
00caf8fc 749762c0 WINSPOOL!GetPrinterDataW+0xef
00caf9a8 00720070 printui!bFolderRefresh+0xaba
005c0032 02470000 0x720070
00020000 000007b8 0x2470000
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gregg" <anon...@discussions.microsoft.com> wrote in message
news:4a9e01c3e473$e2925a40$a001...@phx.gbl...