xlobbysd.exe crashes server ?

Help each other out

xlobbysd.exe crashes server ?

Postby DeanB on Fri Jan 14, 2005 11:35 am

Been using Xlobby more and more, and have now decided to use it with PPC & Jowaldo's skin.

Once i figured out the ppcmenu bit in the servers file it all works fine.

But if i use just menu on PPC or another XP client everything works fine until i exit the program. XLobby server immediately closes, and an error is generated on the clients like this :-

--------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: Unable to read data from the transport connection. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at xlobby2sd.Client.SendMessage(String message)
at xlobby2sd.ClientForm.MouseDownHandler(Object o, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
xlobby2sd
Assembly Version: 1.0.1642.23901
Win32 Version: 1.0.1642.23901
CodeBase: file:///C:/Documents%20and%20Settings/Dean%20Barrett/Desktop/xlobby2sd.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
--------------

Hope that makes sense to someone :)

Is it because i'm using the close button within the XLobby Client that is making it shut the server - if so how should i be shutting the client.


Thanks



DeanB
DeanB
 
Posts: 16
Joined: Tue Jan 04, 2005 6:44 pm

Postby jowaldo on Fri Jan 14, 2005 4:55 pm

It's probably something with the way the close button is on my skin I'm betting. I'll take a look at it.
jowaldo
 
Posts: 903
Joined: Wed May 21, 2003 7:17 pm

Postby jowaldo on Fri Jan 14, 2005 6:50 pm

hmm guess i was wrong... seems to work fine here for me... What dates are on the xlobby.exe and xlobby2sd.exe that you are using?
jowaldo
 
Posts: 903
Joined: Wed May 21, 2003 7:17 pm

Postby DeanB on Fri Jan 14, 2005 7:14 pm

Yep you're right - tried it with Colby Skin, got same error.

Xlobby2.exe is dated 08/01/05

xlobbysd.exe is dated 30/06/04 - and is 40k



Thanks


Dean.
DeanB
 
Posts: 16
Joined: Tue Jan 04, 2005 6:44 pm

Postby Bubblegum Bandit on Sat Mar 19, 2005 7:56 pm

Did this ever get fixed? I'm having the same problem...posted in another place in the forum before I saw this thread.

Not sure if its coincidence or not, but it worked fine before I installed the software for my new win pvr 150 as well as ctpvr.
Bubblegum Bandit
 
Posts: 17
Joined: Sat Oct 02, 2004 4:23 pm
Location: Denver, CO

Postby DeanB on Sun Mar 20, 2005 8:20 am

Nah - never got it to work - have now moved on to Cinemar MainLobby....



Dean.
DeanB
 
Posts: 16
Joined: Tue Jan 04, 2005 6:44 pm

Postby Bubblegum Bandit on Sun Mar 20, 2005 1:59 pm

Mine was fixed by manually changing the xlobby.xml file to add the server's local ip.
Bubblegum Bandit
 
Posts: 17
Joined: Sat Oct 02, 2004 4:23 pm
Location: Denver, CO