Posts: 1,277
Threads: 142
Joined: Oct 2005
Hi,
I think I read something about this but now I can't find it. I have drivers that used to be user ones (like SNMP 1.8) that are now "official."
What do I have to do to get these drivers to work?
Thanks!
Posts: 40,483
Threads: 491
Joined: Aug 2002
The latest version should be shipped now. What you will want to do is go to [cqc]\CQCData\DataServer\Manifests\User and get rid of the old manifest there, then restart your system. It should come up with the new driver installed at that point. This is one of those things that aren't supposed to happen, but the development driver didn't change the model I don't think, so the new and old one have the same make and model.
Dean Roddey
Explorans limites defectum
Posts: 1,277
Threads: 142
Joined: Oct 2005
thanks as always for prompt response.
I am pretty sure I did that, yet i still get these errors in the log:
Code: 09/06 23:20:00-Automation, CQCServer, CQCDrv_Rack_Thread14
{
CQCKit, CQCKit_DriverBase.cpp.3211, Failed/Initialization
An exception occured during driver initialization. Check the logs
}
09/06 23:20:03-Automation, CQCEventSrv, CQCEventWorkerThread3
{
CQCKit, Test Events.0, Status/App Status
This is the test minutely event
}
09/06 23:20:06-Automation, CQCDataSrv, CIDOrbSrvWorkThread_2
{
CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
Macro class '\MEng\System\CQC\Drivers\SNMP\DriverImpl' was not found
CIDOrb_ThisFacility.cpp - 364
CQCKit_MacroSrvClientProxy.cpp - 86
}
09/06 23:20:06-Automation, CQCServer, CQCDrv_Cabinet_Thread19
{
CQCKit, CQCKit_DriverBase.cpp.3211, Failed/Initialization
An exception occured during driver initialization. Check the logs
}
09/06 23:20:10-Automation, CQCDataSrv, CIDOrbSrvWorkThread_2
{
CQCDataSrv, CQCDataSrv_MacroServerImpl.cpp.133, Failed/Not Found, Error: 5000/0/0
Macro class '\MEng\System\CQC\Drivers\SNMP\DriverImpl' was not found
CIDOrb_ThisFacility.cpp - 364
CQCKit_MacroSrvClientProxy.cpp - 86
}
09/06 23:20:10-Automation, CQCServer, CQCDrv_Rack_Thread14
{
CQCKit, CQCKit_DriverBase.cpp.3211, Failed/Initialization
An exception occured during driver initialization. Check the logs
}
Posts: 40,483
Threads: 491
Joined: Aug 2002
Hmmmm... It still doesn't look like you got rid of the old one though, because the manifest file for the shipped one doesn't reference that file. It appears to be pointing at the correct file.
Is this driver running on a machine other than the master server? If so, restart it also since it's already picked up the old manifest and may still be trying to use that info.
Dean Roddey
Explorans limites defectum
Posts: 1,277
Threads: 142
Joined: Oct 2005
OK, i tried to unload and reload the drivers. I selected Generic SNMP. I have to point it at a config file located in the MacroFileRoot\SNMP directory.
I am now getting these errors and the drivers will not initialize:
Code: 09/07 00:01:48-Automation, CQCServer, CQCDrv_Rack_Thread22
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.116, Status/App Status
LoadFile Exception: Could not open file '\Drivers\SNMP\SNMPConfig.xml'
}
09/07 00:01:48-Automation, CQCServer, CQCDrv_Rack_Thread22
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.110, Status/App Status
Rack-LoadConfig: Failed to Load Configuration File.
}
Posts: 40,483
Threads: 491
Joined: Aug 2002
Is the file named SNMPConfig.xml? And also, just to be sure, is it on the same machine where the driver is running? You might want to turn up the verbosity to see if that really means it couldn't open it, or that it opened it but didn't like what it found.
Dean Roddey
Explorans limites defectum
Posts: 1,277
Threads: 142
Joined: Oct 2005
I eventually got this all to work. Everything is running on the same machine.
Is the following the expected behavior:
In the old version it defaulted to \\SNMP\ConfigFileName.xml, which is the correct form.
This new one defaults the path to \Drivers\SNMP\ConfigFileName.xml and I have to change it manually.
Posts: 40,483
Threads: 491
Joined: Aug 2002
Oh, OK. Yeh, he changed it to follow the correct conventions for driver files. That keeps all driver related files under a single scope. I should have put that into the upgrade notes, but it slipped through somehow.
Dean Roddey
Explorans limites defectum
Posts: 1,277
Threads: 142
Joined: Oct 2005
what path in the windows directory structure should the files now live in?
Posts: 40,483
Threads: 491
Joined: Aug 2002
It's the same as before, just down a level into a Drivers subdirectory. All of the files related to device drivers, by convention are in \Drivers\[moniker] type directories under MacroFileRoot. That one hadn't been following that convention and was changed to correct that.
Dean Roddey
Explorans limites defectum
|