Xmanager Forum

WSAAyncSelect() on fd 11 failed, event: 33

Last post: Friday, April 12, 2002 1:59 PM by Support, 1 reply

 
Friday, April 12, 2002 6:41 AM - Terry Duncan

WSAAyncSelect() on fd 11 failed, event: 33

 
Installing the latest version has fixed all of our problems except one. One user continues to experience XManager crashes on his PC with a Solaris host. After this happens, the PC can no longer access the network. The following is a listing of the log file...

Xmanager Version 1.3.9.5 Build 12
Copyright (c) 1997-2002 NetSarang Computer, Inc.
All rights reserved.

UTC Date: Wed Apr 10 16:03:28 2002
Local Date: Wed Apr 10 09:03:28 2002

X Server Directory: "C:Program FilesXmanager1.3.9"
Log File Path: "C:Program FilesXmanager1.3.9Xmanager.log"
Server Generation 1
XDMCP UDP Port: 177
Product Serial #: 011103-110XXX-XXXXXX
WinSock Version 1.1
Highest Version 2.2
Description: WinSock 2.0
System Status: Running
Max Sockets: 32767
Max UDP Datagram: 65467
Local Hostname: 'CBACHMANN'
Local Host IP Address: 192.168.0.178
Xdmcp Init State: 0
Xdmcp Query Address: 192.168.0.114
Screen Resolution: 1024 x 768
Size of Palette: 0
Number of Reserved Colors: 20
Resolution of Color: 16
Depth of Screen: 16
Maximum Cursor Width: 32
Maximum Cursor Height: 32
Frame Width: 4
Frame Height: 4
Border Width: 1
Border Height: 1
Maximum Client Area Width: 1024
Maximum Client Area Height:749
Width of Display(mm): 320
Height of Display(mm): 240
Dots Per Inch X: 96
Dots Per Inch Y: 96
Icon Width: 32
Icon Height: 32
Caption Height: 19
DBCS Enabled: 0
GDI batch limit: 20
Mouse buttons: 3
Waveform Output Devices: 1
Mouse wheel present: 1
Monitors: 1
Same display format: 1
Virtual screen (x, y): (0, 0)
Virtual screen w x h: 1024 x 768
Screen 0: 1024 x 768
Keyboard file: US 101 keyboard
Keyboard type: 0
nKeys, minKC, maxKC, mapWidth, nCompose: 101, 8, 109, 4, 0
Number of keycodes: 102
Number of KeySyms: 408
Bytes of KeySyms: 1632
=== OS Version Information ===
Platform id : 2
Major Version : 5
Minor Version : 0
Build Number : 2195
Description : "Service Pack 2"
Country Code : 1
Country String: United States
==============================
Xdmcp Request Address: 192.168.0.114
Xdmcp Connection Address 0: 192.168.0.178
Xdmcp: sent a REQUEST message
Xdmcp: received an ACCEPT message
Xdmcp: sent a MANAGE message.
Xdmcp: Connection has been established. Going to run session...
Xdmcp KeepAliveTime: 0 seconds
WSAAyncSelect() on fd 11 failed, event: 33
Error: fd 11 not openned in ../../.././lib/xtransXtranswinsock.c, 321
XdmcpFill: too few bytes(-1) received
SocketINETAccept: accept() failed, errno: 10035
WSAAyncSelect() on fd 3 failed, event: 33
WSAAyncSelect() on fd 18 failed, event: 33
Error: fd 3 not openned in ../../.././lib/xtransXtranswinsock.c, 321
Error: fd 18 not openned in ../../.././lib/xtransXtranswinsock.c, 321
XdmcpFill: too few bytes(-1) received
SocketINETAccept: accept() failed, errno: 10035
User forces server termination.
Xdmcp: Control client is closed and the entire session is closed.
All clients are closed down. Going to server reset...
Terminate at server reset is active.
X server was terminated normally.


Friday, April 12, 2002 1:59 PM - Support

Re: WSAAyncSelect() on fd 11 failed, event: 33

 
According to the Xmanager log message, Xmanager has been closed normally but somehow the network subsystem of the PC doesn't work. It might happen because of a massive network traffic used by Xmanager.

Our suggestion is to upgrade the network driver(LAN interface driver) to the latest version.

And also we are planning to post a new patch that can reduce problems soon.

----
Technical Support