I am currently writing an EcoStruxure Geo SCADA Expert driver using the DDK for Geo SCADA Expert version 6.81.7488, Geo SCADA Expert 2019 June 2020 update.
When I start the server the DBStartup log reports:
[DRV] <Driver Name> Version = 6.81.7488.1, Publisher = Aaawesome Solutions Ltd
[DRV] <Driver Name> ** Bad version info (<Driver Name>)
where <Driver Name> is the name of my driver
The driver is built using .Net Framework 4.5.2
The above log entries are all I have to go on at present.
Has anyone any idea what can cause this error?
Solved! Go to Solution.
The Bad Version Info error occurs if the version information in the driver assembly is missing a version number, a company or a support link: These correspond to the following attributes in the AssemblyInfo file:
https://docs.microsoft.com/en-us/dotnet/standard/assembly/set-attributes
The DDK 'help' has some info on this, have you walked through all the steps in that?
I'd normally start with the Sample DDK driver. Just compile this and make sure that it installs and runs correctly.
Then you can modify the appropriate module / driver projects to do what you need of it.
It's been quite a while since I did any DDK development, but there were a couple of other causes that resulted in the Bad Version. From memory this would happen if your driver (the DBModule portion anyway) was throwing any Exception during initialisation also, meaning it might not be exactly a 'Bad Version'.
Try to cut it down so that you just have the module (i.e. no objects etc) and see if that runs, if it does, then you can slowly add objects (commenting out any interdependencies) until you've got the whole thing working.
I don't believe it is a driver (exe) issue, too early in the startup process. Looks more like module (dll) issue.
My first guess would be missing or incorrect third party dlls being referenced from your module. Does your driver reference anything beyond the .NET and Geo SCADA dlls? For example Newtonsoft for some JSON handling? If one of those is not in the same path or there's a version mismatch it'll cause the module to fail to load
The Bad Version Info error occurs if the version information in the driver assembly is missing a version number, a company or a support link: These correspond to the following attributes in the AssemblyInfo file:
https://docs.microsoft.com/en-us/dotnet/standard/assembly/set-attributes
Andrew
Thanks, that was the issue, is this documented anywhere?
Regards
Andy
Thanks for taking the time to reply. I could find no reference to that in the help file. Which help are you referring to?
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!