ISY problem with CQC v4.60

[ellisr63]

I started getting this error...

Code:

10/27 01:24:05-Automation-PC, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
    Macro class '\MEng\System\CQC\Drivers\ISYInsteon\DriverImpl' was not found
      <CQCDataSrv> CIDOrb_ThisFacility.cpp - 536
      <CQCServer> CQCKit_MacroSrvClientProxy.cpp - 87
      <CQCServer> CQCDriver_DriverBase.cpp - 3875

}
10/27 01:24:05-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3884, Failed/Initialization
    An exception occured during driver initialization. Check the logs
}
10/27 01:24:15-Automation-PC, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
    Macro class '\MEng\System\CQC\Drivers\ISYInsteon\DriverImpl' was not found
      <CQCDataSrv> CIDOrb_ThisFacility.cpp - 536
      <CQCServer> CQCKit_MacroSrvClientProxy.cpp - 87
      <CQCServer> CQCDriver_DriverBase.cpp - 3875

}
10/27 01:24:15-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3884, Failed/Initialization
    An exception occured during driver initialization. Check the logs
}
10/27 01:24:25-Automation-PC, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
    Macro class '\MEng\System\CQC\Drivers\ISYInsteon\DriverImpl' was not found
      <CQCDataSrv> CIDOrb_ThisFacility.cpp - 536
      <CQCServer> CQCKit_MacroSrvClientProxy.cpp - 87
      <CQCServer> CQCDriver_DriverBase.cpp - 3875

}
10/27 01:24:25-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3884, Failed/Initialization
    An exception occured during driver initialization. Check the logs
}
10/27 01:24:25-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCGenDrvS, CQCGenDrvS_DriverGlue.cpp.2172, Failed/App Status
    An system exception occured in CML driver method Terminate
}
10/27 01:24:25-Automation-PC, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
    Macro class '\MEng\System\CQC\Drivers\ISYInsteon\DriverImpl' was not found
      <CQCDataSrv> CIDOrb_ThisFacility.cpp - 536
      <CQCServer> CQCKit_MacroSrvClientProxy.cpp - 87
      <CQCServer> CQCDriver_DriverBase.cpp - 3875

}
10/27 01:24:25-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3884, Failed/Initialization
    An exception occured during driver initialization. Check the logs
}
10/27 01:24:25-Automation-PC, CQCServer, CIDOrbSrvWorkThread_3
{
    CQCServer, CQCServer_DriverCtrl.cpp.203, Status/App Status
    Reconfigure of driver ISY is completed
}
10/27 01:24:35-Automation-PC, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
    Macro class '\MEng\System\CQC\Drivers\ISYInsteon\DriverImpl' was not found
      <CQCDataSrv> CIDOrb_ThisFacility.cpp - 536
      <CQCServer> CQCKit_MacroSrvClientProxy.cpp - 87
      <CQCServer> CQCDriver_DriverBase.cpp - 3875

}
10/27 01:24:35-Automation-PC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3884, Failed/Initialization
    An exception occured during driver initialization. Check the logs
}

I have tried re installing the driver but I still get the "waiting for initialization" error.

[Dean Roddey]

Did you upgrade all your systems? The driver was moved to make it consistent with the way other drivers are stored, because there are now going to be two of them (the original and the V2.) That is trying to load it from the old location.

If you go to [cqc]\CQCData\DataServer\Manifests\User\ on the Master Server do you have any ISY/Insteon driver manifest files in there? If so, you may be loading one of those instead of the shipped one, so copy those out somewhere else and restart the MS and try it again. That would mean someone gave you a User manifest but didn't change the make/model so it's being used instead of the System one.

[Dean Roddey]

I just tested it with the 4.5.25 version, which I assume is what you meant by 4.6 (I just updated the release notes to get ready for 4.6 so I don't forget it, it's not really 4.6 yet).), and it's working fine. So I'm assuming you probably have a User manifest file that was referring to the System driver, and now that I've move it, that manifest is causing problems. So check for that and remove it if so. If not, let me know.

[ellisr63]

Did you upgrade all your systems? The driver was moved to make it consistent with the way other drivers are stored, because there are now going to be two of them (the original and the V2.) That is trying to load it from the old location.

If you go to [cqc]\CQCData\DataServer\Manifests\User\ on the Master Server do you have any ISY/Insteon driver manifest files in there? If so, you may be loading one of those instead of the shipped one, so copy those out somewhere else and restart the MS and try it again. That would mean someone gave you a User manifest but didn't change the make/model so it's being used instead of the System one.

The folder is empty. Should I uninstall CQC, and start over with it?

[Dean Roddey]

No, don't uninstall CQC. There's no way that's required. There's something silly going on, nothing fundamental. I assume all of your other drivers are ok, right?

If you select the ISY driver in the Host Admin dialog, and press the Info button, what does the Version value show? The latest version is 2.2, so you should see 2.2 there.

[ellisr63]

No, don't uninstall CQC. There's no way that's required. There's something silly going on, nothing fundamental. I assume all of your other drivers are ok, right?

If you select the ISY driver in the Host Admin dialog, and press the Info button, what does the Version value show? The latest version is 2.2, so you should see 2.2 there.

I only have 2 drivers setup currently... The ISY driver says 2.2. My Denon driver is working fine.

[Dean Roddey]

It's got to be picking up the wrong manifest file. Let's try this... Import the attached package, then do a reload of the driver and see if that doesn't fix it.

[ellisr63]

It's got to be picking up the wrong manifest file. Let's try this... Import the attached package, then do a reload of the driver and see if that doesn't fix it.

Thanks Dean, that did it. :-)