APAR status
Closed as program error.
Error description
nsd running on Windows 2003 x64 Edition returns the errors listed below any time nsd runs. The PIDs are system processes. Just run nsd on Windows 2003 x64 Edition to reproduce the problem. nsd log attached. Generated Messages: ERROR (0): EnumProcModules failed pid=02dc,ppid=0004 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0324,ppid=02dc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0344,ppid=02dc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0370,ppid=0344 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=037c,ppid=0344 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=00e4,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=015c,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=01c8,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=01f4,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0200,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=043c,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0458,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=04f0,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0520,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=07c4,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=08b0,ppid=0370 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0778,ppid=00e4 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0dcc,ppid=0514 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0838,ppid=0dcc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0e9c,ppid=02dc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0b70,ppid=02dc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0fe4,ppid=0b70 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=03b4,ppid=0a4c - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=020c,ppid=0820 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0d60,ppid=0dcc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=053c,ppid=0344 - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed. ERROR (0): EnumProcModules failed pid=0f6c,ppid=0dcc - (299) Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
Local fix
Fixed in 702
Problem summary
A programming error was found and will be corrected in a future release.
Problem conclusion
A programming error was found and will be corrected in a future release.
Temporary fix
Comments
APAR Information
APAR number
LO49110
Reported component name
DOMINO SERVER
Reported component ID
5724E6200
Reported release
802
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-22
Closed date
2010-04-29
Last modified date
2010-04-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DOMINO SERVER
Fixed component ID
5724E6200
Applicable component levels
R802 PSN
UP
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
29 April 2010