Posts: 1,094
Threads: 69
Joined: Mar 2006
When I try to launch the CQC Driver Test Harness, I get a dialog that says:
CQC Driver Test Harness
An unknown exception occured
With the option to click OK
(Well, it's not really OK, but what do you do?)
This has just started happening. I rebooted the server, and when that didn't clear it, reinstalled 2.2.4 over the existing install, still no change.
No relevant entries that I can see in the CQC or Windows logs.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Are there any .ErrorInf files anywhere in the CQC directory? And does this happen when you are just starting it up or when you try to open a new session?
Dean Roddey
Explorans limites defectum
Posts: 1,094
Threads: 69
Joined: Mar 2006
No, there are two 0-byte files in C, but i don't think they are relevant:
Code:
Directory of C:\
09/03/2006 09:19 PM 0 CQCClient_908.ErrorInf
09/03/2006 09:18 PM 0 CQCIntfView_3584.ErrorInf
This happens when I try to start the test harness. The macro workshop, and protocol driver harness both load correctly, but the driver test harness errors before painting any windows except the error dialog.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Yeh, those are old. Just for funzies, try opening the CQC Command Prompt and doing:
CQCDrvDev /NoState
And see if it comes up. If so, just close it and go back and open it via the start menu.
Dean Roddey
Explorans limites defectum
Posts: 1,763
Threads: 76
Joined: Jun 2007
Where is the State data for the various IDE's located? Is it internally in CQC somewhere or in the Registry?
Posts: 1,094
Threads: 69
Joined: Mar 2006
Dean Roddey Wrote:Yeh, those are old. Just for funzies, try opening the CQC Command Prompt and doing:
CQCDrvDev /NoState
And see if it comes up. If so, just close it and go back and open it via the start menu.
That did it. Resolution by 11:34 am on a Sunday.
Posts: 40,483
Threads: 491
Joined: Aug 2002
It's in the local CQC configuration repository. I need to just make that code failsafe and if anything goes wrong, just blank it out and go back to defaults I guess. Somehow it must have stored some bogus data, and sometimes the issue occurs when you access from different RDP sessiosn causes problems. So it should just recover when problems occur and just go back to default state. I'll see about that for the upcoming drop.
Dean Roddey
Explorans limites defectum
Posts: 1,094
Threads: 69
Joined: Mar 2006
Dean Roddey Wrote:It's in the local CQC configuration repository. I need to just make that code failsafe and if anything goes wrong, just blank it out and go back to defaults I guess. Somehow it must have stored some bogus data, and sometimes the issue occurs when you access from different RDP sessiosn causes problems. So it should just recover when problems occur and just go back to default state. I'll see about that for the upcoming drop.
FWIW, I rarely ever access the Test Harness except through RDP, so that fits the scenario.
Posts: 1,094
Threads: 69
Joined: Mar 2006
For when I need to search for this thread again, this is to remind myself that /NoState is case sensitive.
Posts: 1,094
Threads: 69
Joined: Mar 2006
Dean Roddey Wrote:It's in the local CQC configuration repository. I need to just make that code failsafe and if anything goes wrong, just blank it out and go back to defaults I guess. Somehow it must have stored some bogus data, and sometimes the issue occurs when you access from different RDP sessiosn causes problems. So it should just recover when problems occur and just go back to default state. I'll see about that for the upcoming drop.
When I try to run the interface editor, I get an unknown exception. I tried /NoState on the command line (CQCIntfDes.exe /NoState), but no luck.
QCQ INTERFACE EDITOR
An unhandled exception occured during GUI processing. Please see the log file.
Error details:
Facility: CIDLib
Error #: 2473/0/0
Severity: API Failed
Error Class: Can't Do
Line: CIDLib_process.cpp/67
Error while settings single process instance information
