|
Short Description
|
identify user in event log messages
|
|
Entered
|
By:
PeteL
When: 1998-09-02 08:02:49 Build: 1.03.20d
|
|
Categories
|
Type:
Suggestion
Department: Product
Category:
Troubleshooting
|
Description
|
as we have discussed, certain error messages are very difficult to diagnose without further information. many of those messages would benefit from inclusion of the LU name and/or IP address and/or LU number (from the LU group) and/or currently recognized screen name (if not global.default) and/or certain pieces of screen data, depending on the message. actual event log has been emailed.
|
|
|
|
Append
|
By: WindSurfer When: 1998-09-02 09:24:49 New Status:
Accepted
|
|
Comment
|
We have added the last recognized screen to the standard component error display, and have added current section and screen to some errors that were not being reported using standard component techniques (such as the attribute write errors).
We will try to get you a build today with the user's IP address added to all errors as well as the LU name.
|
|
|
|
Append
|
By: PeteL When: 1998-09-04 13:17:48 New Status:
Pending IE
|
|
Comment
|
A socket error code 40 occurred during:
Termport task 1: Overlapped receive on HTTP port
EXPLANATION:
The system description for this error code is: The specified network name is no longer available. (0x40)
here's another message that I'd love some more information on - i don't like the sounds of it after monday's episode
|
|
|
|
Append
|
By: WindSurfer When: 1998-10-06 11:47:38 New Status:
Accepted
|
|
Comment
|
Am working on this today.
|