Official RIVA thread

[Dean Roddey]

That's new to me. No one ever said anything so I've had no reason to look into it. Are you taking about the regular IV here?

[jkish]

That's new to me. No one ever said anything so I've had no reason to look into it. Are you taking about the regular IV here?

Yes, just a regular IV.

I haven't mentioned it before since it has been sort of random, I couldn't pinpoint anything that might have led to the problem, and I couldn't rule out something in my environment that might be sick.

But hearing another mention of the data server possibly having problems made me think that it could be related.

[VidaBox LLC]

I have also been able to get the RIVA client you developed Dean to eventually chokes and not be able to log on. It takes a couple of tries and eventually, it won't log on. CQC server reboot is the only solution. I'll check into it some more the next time it happens with what you suggested.

It's funny but I haven't had any issues with it today so haven't been able to look into it more deeply.

[brianmount]

It happens repeatably for me. Is this CQCNetTest thing something I can run? Would it help you to check if something's wrong? How do I do it?

[Mark Stega]

Open a CQC Command prompt (it is a shortcut created when you installed CQC). At the command prompt type "CQCNetTest >z.tmp" (leave off the quotes). Post the content of z.tmp here.

[Edit] Do this when you are in 'broken' state

[SamVimes2]

I got into the broken state:


but I don't see anything obviously wrong in my net test:

CQC Network Info Test
Copyright © Charmed Quark Systems


System Information
--------------------------------
OS Version: 5.2.2, Build: 3790
Node Name: odin
TCP Version: 2.2


Network Adaptor Information
--------------------------------
{ACE2EEF0-252A-4BB9-92FE-DA98AA97A97F}
Generic Marvell Yukon 88E8056 based Ethernet Controller
DHCP Enabled: True
Gateway/Mask: 192.168.0.1/0.0.0.0
Hardware Addr:
Address/Mask #0: 192.168.0.186/255.255.255.0


Environment Information
--------------------------------
CID_NSADDR: odin
CQC_DATADIR: C:\Program Files\CQC\CQCData


Name Resolution
--------------------------------
Trying to resolve name: odin...
Resolved to: 192.168.0.186

Resolving back the other way...
Host Name: odin


CQC Connection Tests
--------------------------------
Trying to connect to CQC name server...
Connected to name server successfully

Trying to connect to log server...
Connected to log server successfully

Trying to connect to Master Cfg Server...
Connected to Master Cfg Server successfully

Trying to connect to local Cfg Server...
Connected to local Cfg Server successfully

Trying to connect to installation server...
Connected installation interface successfully

Trying to connect to security server...
Connected security interface successfully

Trying to connect to macro server...
Connected macro interface successfully

Trying to connect to CQCServer on host odin
Connected CQCServer successfully


Server Statistics
--------------------------------

Stats For Process: Name Server
----------------------------
Object Id: odin.13502
Running On: odin
Up Since: Tue, Sep 29 18:33:12 2009 -0400
Client HWM: 16
Dropped Packets: 0
Cur Clients: 11
Max Clients: 92
Active Cmds: 1
Queued Cmds: 0
Registered Objs: 2
Worker Threads: 4
Targets: 0
Cmd Cache Sz: 0
Srv Cache Sz: 0
Wait List: 0


Stats For Process: Log Server
----------------------------
Object Id: odin.13503
Running On: odin
Up Since: Tue, Sep 29 18:33:12 2009 -0400
Client HWM: 13
Dropped Packets: 0
Cur Clients: 12
Max Clients: 92
Active Cmds: 1
Queued Cmds: 0
Registered Objs: 2
Worker Threads: 4
Targets: 0
Cmd Cache Sz: 1
Srv Cache Sz: 1
Wait List: 0


Stats For Process: Master Cfg Server
----------------------------
Object Id: odin.13504
Running On: odin
Up Since: Tue, Sep 29 18:33:12 2009 -0400
Client HWM: 3
Dropped Packets: 0
Cur Clients: 1
Max Clients: 92
Active Cmds: 1
Queued Cmds: 0
Registered Objs: 2
Worker Threads: 4
Targets: 1
Cmd Cache Sz: 2
Srv Cache Sz: 1
Wait List: 0


Stats For Process: Data Server
----------------------------
Object Id: odin.13505
Running On: odin
Up Since: Tue, Sep 29 18:33:16 2009 -0400
Client HWM: 4
Dropped Packets: 0
Cur Clients: 1
Max Clients: 92
Active Cmds: 1
Queued Cmds: 0
Registered Objs: 6
Worker Threads: 4
Targets: 1
Cmd Cache Sz: 2
Srv Cache Sz: 1
Wait List: 0


Stats For Process: CQCServer on odin
----------------------------
Object Id: odin.13507
Running On: odin
Up Since: Tue, Sep 29 18:33:19 2009 -0400
Client HWM: 7
Dropped Packets: 0
Cur Clients: 6
Max Clients: 92
Active Cmds: 1
Queued Cmds: 0
Registered Objs: 2
Worker Threads: 4
Targets: 1
Cmd Cache Sz: 2
Srv Cache Sz: 1
Wait List: 0

[SamVimes2]

Instead of restarting teh service, kill the CQCRemVSrv program. It'll be restarted automatically. If it comes back up, then it's clearly something specific to that remote viewer server.

This worked for me - after I got in the broken state (see above) I killed the CQCRemVSrv.exe process. It restarted automatically and I could connect again. No reboot/service restart required.

Now all we have to do is figure out why it happens in the first place!

[Dean Roddey]

OK, that makes more sense. It's the RIVA server getting wierd, not the system in general. I'll take a look at that after get the next drop out in a couple days. And this happens when you just kill the connection, right?

[brianmount]

Yes. I don't yet know whether it will happen when I send a LogOff, because I haven't gotten that part of my application done yet.

[brianmount]

Hmmm. I figured that my LogOff message was not getting through, because I was seeing the CQC log message indicating that my client dropped the connection, and the RIVA documentation talked about the LogOff being a way to avoid log warnings about communication failures. But I modified my program to wait explicitly after sending the LogOff, to make sure that it got sent before the socket was closed. And still I see the dropped connection message. Should I expect the log to look different, or is that message always logged regardless of whether LogOff is received before the connection is closed?