Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: .Net RIVA Client
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Mark Stega Wrote:Put the mouse on some part of the dialog that doesn't have a control and do a click. That definitely stops the countdown.


Turn the logging to verbose on the RIVA client and capture about 10 seconds of log (it will be in the executing directory) and post that please.

I turned on Verbose logging, but I don't see any log files in the default installation directory:
Code:
05/21/2009  04:19 PM               512 click.wav
05/28/2009  04:44 PM             7,168 CQCDefinitions.dll
05/28/2009  04:44 PM            33,792 GraphicFramework.dll
05/28/2009  04:44 PM            27,648 MessageFramework.dll
06/12/2009  12:59 PM               497 RIVA.NetClientFF.config
05/28/2009  04:44 PM            13,824 RIVA.NetClientFF.exe
04/17/2009  01:12 PM               881 RIVA.NetClientFF.exe.config
05/10/2005  02:35 PM             3,638 RIVA.NetClientFF.ico
06/12/2009  12:59 PM         3,500,934 RIVA.NetClientFF.Log
05/28/2009  04:44 PM            23,040 SecurityFramework.dll
10/13/2008  05:44 PM           667,648 System.Core.dll
05/28/2009  04:44 PM            17,408 SystemFramework.dll
You must of had the logging on for a while, it's this one:

Quote:06/12/2009 12:59 PM 3,500,934 RIVA.NetClientFF.Log

I'd say delete that, run for just a 10 seconds or so, and then post the new log file contents...
Mark Stega Wrote:You must of had the logging on for a while, it's this one:



I'd say delete that, run for just a 10 seconds or so, and then post the new log file contents...

I feel dumb now. I was looking for the LOG file type (temporary box, didn't configure it to show file extensions), and didn't pay attention to the dir output.

I have attached the log file.
Mark Stega Wrote:And it may be helpful to see the exception message
Quote:(7:55:29.586 AM - Error) Image request failure: System.Net.Sockets.SocketException: An error message is available for this exception but cannot be displayed because these messages are optional and are not currently installed on this device. Please install ‘NETCFv35.Messages.EN.wm.cab’ for Windows Mobile 5.0 and above or ‘NETCFv35.Messages.EN.cab’ for other platforms. Restart the application to see the message.

et voila, messr.

Quote:(2:42:33.246 PM - Error) Image request failure: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.ReceiveNoCheck(Byte[] buffer, Int32 index, Int32 request, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 size, SocketFlags socketFlags)
at CQC.MessageFramework.MessageEngine.ReceiveMessage(MessagePacket& p_MessagePacket)
at CQC.MessageFramework.MessageEngine.RequestImage(Rectangle p_Rectangle, Byte[] p_SessionCookie)
at CQC.MessageFramework.CommunicationThreadImage.DoWork()

(2:42:33.359 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: NullReferenceException
(2:42:33.382 PM - Error) Communication failure
(2:42:33.409 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: A blocking operation was interrupted by a call to WSACancelBlockingCall
(2:42:33.432 PM - Error) Communication failure
(2:43:07.315 PM - Error) ERROR RECEIVING: Bad header byte count: 3
(2:43:07.403 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 3
(2:43:07.427 PM - Error) Communication failure
(2:43:07.554 PM - Error) Image request failure: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.Socket.ReceiveNoCheck(Byte[] buffer, Int32 index, Int32 request, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at CQC.MessageFramework.MessageEngine._RawReceive(UInt32 c4DataSize, Byte[]& payloadBytes)
at CQC.MessageFramework.MessageEngine.RequestImage(Rectangle p_Rectangle, Byte[] p_SessionCookie)
at CQC.MessageFramework.CommunicationThreadImage.DoWork()

(2:43:07.601 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: NullReferenceException
(2:43:07.721 PM - Error) Communication failure
(2:43:23.206 PM - Error) ERROR RECEIVING: Bad byte count (UTF8ByteCount/UTF8BufferCount/available): 8192 / 0 / 0
(2:43:23.286 PM - Error) Image request failure: System.Exception: Byte count error in received message!
at CQC.MessageFramework.MessageEngine._RawReceive(UInt32 c4DataSize, Byte[]& payloadBytes)
at CQC.MessageFramework.MessageEngine.RequestImage(Rectangle p_Rectangle, Byte[] p_SessionCookie)
at CQC.MessageFramework.CommunicationThreadImage.DoWork()

(2:43:23.373 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: NullReferenceException
(2:43:23.413 PM - Error) Communication failure
(2:43:23.485 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: NullReferenceException
(2:43:23.510 PM - Error) Communication failure
(2:44:48.657 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:44:48.716 PM - Error) Image request failure: System.Exception: Byte count error in received header: 0
at CQC.MessageFramework.MessageEngine.ReceiveMessage(MessagePacket& p_MessagePacket)
at CQC.MessageFramework.MessageEngine.RequestImage(Rectangle p_Rectangle, Byte[] p_SessionCookie)
at CQC.MessageFramework.CommunicationThreadImage.DoWork()

(2:44:48.747 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: NullReferenceException
(2:44:48.770 PM - Error) Communication failure
(2:44:49.258 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: A blocking operation was interrupted by a call to WSACancelBlockingCall
(2:44:49.280 PM - Error) Communication failure
(2:44:55.185 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:44:55.213 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 0
(2:44:55.245 PM - Error) Communication failure
(2:45:04.675 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:45:04.754 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 0
(2:45:04.807 PM - Error) Communication failure
(2:45:14.745 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:45:14.793 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 0
(2:45:14.831 PM - Error) Communication failure
(2:45:25.285 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:45:25.307 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 0
(2:45:25.328 PM - Error) Communication failure
(2:45:34.363 PM - Error) ERROR RECEIVING: Bad header byte count: 0
(2:45:34.409 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: Byte count error in received header: 0
(2:45:34.432 PM - Error) Communication failure
(2:46:21.675 PM - Error) CONNECTING: ERROR - Null socket
(2:46:22.498 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: ThreadAbortException
(2:46:22.599 PM - Error) Communication failure
(2:46:22.751 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: ThreadAbortException
(2:46:22.906 PM - Error) Communication failure
(2:46:23.061 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: ThreadAbortException
(2:46:23.230 PM - Error) Communication failure
(2:46:23.379 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: ThreadAbortException
(2:46:23.597 PM - Error) Communication failure
(2:46:23.780 PM - Error) EXCEPTION in ListenSocketAcceptAndProcessMessages: ThreadAbortException
(2:46:23.945 PM - Error) Communication failure
electron Wrote:I feel dumb now. I was looking for the LOG file type (temporary box, didn't configure it to show file extensions), and didn't pay attention to the dir output.

I have attached the log file.

So what I see is this:

Quote:(3:28:56.639 PM - Info) ---> 2E 02 00 4B 00 68 F1
(3:28:56.639 PM - Info) RECEIVED: Intermediate buffer: 75
(3:28:56.639 PM - Info) RECEIVED: Payload buffer: 75
(3:28:56.639 PM - Info) Dumping PayloadBytesReceived which has a length of 75
(3:28:56.639 PM - Info) ---> 00 45 55 01 AA F9 F0 45 22 0C 9D E7 43 8B E6 A1 4A A8 35 00 00 00 54 68 65 72 65 20 69 73 20 6E 6F 20 64 65 66 61 75 6C 74 20 74 65 6D 70 6C 61 74 65 20 64 65 66 69 6E 65 64 20 66 6F 72 20 75 73 65 72 20 27 41 64 6D 69 6E 27

This is the login status return and it indicates an error (first byte in the payload is zero). The message is 53 bytes and is "There is no default template defined for user 'Admin'

I guess this is showing up in the dialog too briefly to be read but is the cause of your issue...
IVB Wrote:et voila, messr.

Not much help, I am afraid. I'd suggest starting on the desktop version and making certain that that works to rid ourselves of any lingering license issues, etc. If it works, I am pretty certain we are looking at some kind of network issue.

So if the desktop version is working, delete the log file on the phone, run the viewer for about 10 seconds and post the complete log here please.
Mark,
My RIVA client is dropping the connection every few minutes. Here is the CQC log file.

Can you point me in the right direction.
bryanb Wrote:Mark,
My RIVA client is dropping the connection every few minutes. Here is the CQC log file.

Can you point me in the right direction.

It is as if the network was getting reliably interrupted ( :-) ) every few minutes. Presuming that the client is a handheld on the wireless network, the first thing I'd do is to make a desktop wireless connection to your network and see if the FF RIVA client exhibits the same issue. If it does, it points us toward the network, if it doesn't, it points us toward something on the handheld.
What's interesting is that I set logging on the client to high about 10 -15 minutes ago and it hasn't lost it's connection since. Before it was dropping in about every 2 - 3 minutes. I'll keep playing with it.
Mark,

I'll work on getting the FF client running. Normally I don't use it.

I did three tests, different log levels, with the CF client. The low and med log levels failed within 2-3 minutes. The high log level ran 10 minutes, but then failled. Enclosed is the high log file from the iPaq. The iPaq is on a wireless network but it's only about 6 ft from the access point and it's in its' dock.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15