About Corvil. Corvil is the leader in performance monitoring and analytics for electronic financial markets. The world’s financial markets companies turn to Corvil analytics for the unique visibility and intelligence we provide to assure the speed, transparency, and compliance of their businesses globally.
We have recently patched all client PC's to [Windows XP] SP2. We
are running SAPGUI 640 for Windows (Patch 20).
Since the XP SP2 patch we are getting 'WSAECONNRESET connection
reset bypeer' errors on multiple PC's throughout our site.
are running SAPGUI 640 for Windows (Patch 20).
Since the XP SP2 patch we are getting 'WSAECONNRESET connection
reset bypeer' errors on multiple PC's throughout our site.
The error always appears after inactivity in the GUI - ie the
user hasn't done anything for about an hour or more. The
connection dropout will show in dev_disp when it occurs. The
user sees a pop-up Window with the error when they next do an
action in the GUI (This pop-up reports WSAECONNRESET, Error No
10054, Module ninti.c).
user hasn't done anything for about an hour or more. The
connection dropout will show in dev_disp when it occurs. The
user sees a pop-up Window with the error when they next do an
action in the GUI (This pop-up reports WSAECONNRESET, Error No
10054, Module ninti.c).
The log entry in dev_disp:
*** ERROR => DpCheckTerminals: NiCheck2(rc=-23) failed for tid:
83
(60secs)-> disconnecting [dpxxdisp.c 10334]
RM-T83, U16334, 100 USER, HOSTNAME, 09:26:12, M0, W2, IW38, 2/1
83
(60secs)-> disconnecting [dpxxdisp.c 10334]
RM-T83, U16334, 100 USER, HOSTNAME, 09:26:12, M0, W2, IW38, 2/1
There's no log in SM21.
What I've Tried:
- Obviously is some problem with network/OS, not necessarily SAP.
Our network guys have looked in detail thru the network and
report no errors.
- Windows Firewall is enabled in Group Policies, although SAPGUI
is explicity allowed in the Defined Program Exceptions.
- I have performed niping tests on the affected PC's and all has
returned ok.
- We have added the registry fix suggested in SAP Note 413330
(setting
TcpMaxDataRetransmissions to 7) with no success. Also changed
message server timeout setting in GUI to 30 secs.
- THE PROBLEM DOESN'T OCCUR WHEN WINDOWS FIREWALL IS DISBALED.
Our corp security reqs are that this needs to be enabled.
- Obviously is some problem with network/OS, not necessarily SAP.
Our network guys have looked in detail thru the network and
report no errors.
- Windows Firewall is enabled in Group Policies, although SAPGUI
is explicity allowed in the Defined Program Exceptions.
- I have performed niping tests on the affected PC's and all has
returned ok.
- We have added the registry fix suggested in SAP Note 413330
(setting
TcpMaxDataRetransmissions to 7) with no success. Also changed
message server timeout setting in GUI to 30 secs.
- THE PROBLEM DOESN'T OCCUR WHEN WINDOWS FIREWALL IS DISBALED.
Our corp security reqs are that this needs to be enabled.
Are there any other known issues with the Windows Firewall/SP2
and SAP
GUI? Has anyone else had this when upgrading client PCs?
and SAP
GUI? Has anyone else had this when upgrading client PCs?
We are running BASIS 620(55), kernel 640(126)
Many thanks,
James
James