Posts: 341
Threads: 53
Joined: Nov 2018
Updated LAN and Audio drivers on the server going to mess with CQC Voice again and after reboot I'm getting these messages repeatedly in the log.
Code:
01/30 20:49:11-CQC-Prime, CQCDataSrv, CIDOrbSrvWorkThread_3
{
CIDOrb, CIDOrb_ThisFacility.cpp.563, Failed/Not Found, Error: 6503/0/0
Object '{825C0E370D8C5D6C-0B3B6D941AB56445}1E7AB11B02FA941E-9EFDFE6157D70A87' was not found on this server
<CQCServer> CQCKit_InstClientProxy.cpp - 214
<CQCServer> CQCServer_ThisFacility.cpp - 2666
}
01/30 20:49:17-CQC-Prime, CQCDataSrv, CIDOrbSrvWorkThread_3
{
CIDOrb, CIDOrb_ThisFacility.cpp.563, Failed/Not Found, Error: 6503/0/0
Object '{825C0E370D8C5D6C-0B3B6D941AB56445}1E7AB11B02FA941E-9EFDFE6157D70A87' was not found on this server
<CQCServer> CQCKit_InstClientProxy.cpp - 214
<CQCServer> CQCServer_ThisFacility.cpp - 2666
}
Posts: 341
Threads: 53
Joined: Nov 2018
On the master I stopped client service and app service and waited a couple of minutes then I started the client service and waited little and then started the app service. After it loaded things are now fine. Something strange with startup or something not loading?
Posts: 40,483
Threads: 491
Joined: Aug 2002
That is CQCServer (the program that hosts drivers) calling to the data server to load a driver and not finding the correct interface there. If something like that happens again, run CQCNetTest and get the output so we can see more about what's going on. That's a pretty unusual scenario that generally would tend to happen if a server failed unexpectedly and restarted (CQCServer) but the client still had the old connection info (which it hangs onto for a while for efficiency.)
Dean Roddey
Explorans limites defectum
Posts: 341
Threads: 53
Joined: Nov 2018
(01-30-2020, 06:24 PM)Dean Roddey Wrote: That is CQCServer (the program that hosts drivers) calling to the data server to load a driver and not finding the correct interface there. If something like that happens again, run CQCNetTest and get the output so we can see more about what's going on. That's a pretty unusual scenario that generally would tend to happen if a server failed unexpectedly and restarted (CQCServer) but the client still had the old connection info (which it hangs onto for a while for efficiency.)
I had an IV client running on my desktop when I rebooted the master. Would that have done it? I may of had a AI running but I thought I had closed that. However when I did re-open the AI after the master was "up" I did get a error about unable to load driver data from the remote AI session.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Rebooting the master with stuff up could potentially do it. But that was CQCServer so another machine besides the MS would have to be hosting drivers for that to have done it. If you are only hosting drivers on the master server, then CQCServer should have gone down along with the rest of the MS.
Generally, if it does happen, it should resolve itself within a minute or so worst case though. The client will give up and the cached info it has and go back and get new info.
Dean Roddey
Explorans limites defectum
Posts: 341
Threads: 53
Joined: Nov 2018
After the weirdness and another restart of the service things did clear up and no problems since. Yes all drivers are hosted on the single master.
