Hi,
I'm trying to develop a ctrl extension and I've included the rabbitmq-c, open ssl library and zlib compression library to the ctrl extension project.. (I've installed them as nuget packages from visual studio)
The code compiles with no errors but when I try to use the dll in WinCC OA, I get the fatal error message of:
5/ctrl, Location of the following log entry: , Line:1
WCCOAui (1), 2017.11.24 12:05:52.575, SYS, WARNING, 133, Could not load shared library D:\\Demo\\bin\\TestCtrlExt.dll, The specified module could not be found.
WCCOAui (1), 2017.11.24 12:05:52.587, CTRL, SEVERE, 5/ctrl, Location of the following log entry: , Line:1
54, Unexpected state, The Ctrl Extension D:\\Demo\\bin\\TestCtrlExt.dll is not compatible with the current library version 315000 of WinCC OA.
It might be from version
Ctrl Extension compatibility problem
- pavel.fiala
- Posts:5
- Joined: Fri May 15, 2015 11:19 pm
Re: Ctrl Extension compatibility problem
Hi Alper,
most of the times I see this message, it actually means that you miss some of the extension DLL dependencies in path. As dirty test, you could try to place the dependencies directly in WinCC OA installation bin directory and try to load your extension and see if it works or not.
Pavel
most of the times I see this message, it actually means that you miss some of the extension DLL dependencies in path. As dirty test, you could try to place the dependencies directly in WinCC OA installation bin directory and try to load your extension and see if it works or not.
Pavel
- riso77
- Posts:16
- Joined: Mon Jan 15, 2018 10:57 am
Re: Ctrl Extension compatibility problem
I am having the same problem :"The Ctrl Extension is not compatible with the current library version 315000 of WinCC OA."
What is funny, that my colleagues use the same version and patch of WinccOA, they do register the subproject the same way as I, but my gedi refuses to start. We all use v3.15 p013
WCCOAui (1), 2018.10.24 19:16:11.972, CTRL, WARNING, 5/ctrl, Location of the following log entry: D:\\ScadaRepository\\DSM\\DSM_20181018\\scripts\\libs\\RcmCore/RcmCoreUtils.ctc, Line:4
WCCOAui (1), 2018.10.24 19:16:11.972, SYS, WARNING, 133, Could not load shared library D:\\ScadaRepository\\DSM\\DSM_20181018\\bin\\CtrlRcmCore.dll, Access is denied.
WCCOAui (1), 2018.10.24 19:16:11.999, CTRL, SEVERE, 5/ctrl, Location of the following log entry: D:\\ScadaRepository\\DSM\\DSM_20181018\\scripts\\libs\\RcmCore/RcmCoreUtils.ctc, Line:4
WCCOAui (1), 2018.10.24 19:16:11.999, IMPL, FATAL, 54, Unexpected state, The Ctrl Extension D:\\ScadaRepository\\DSM\\DSM_20181018\\bin\\CtrlRcmCore.dll is not compatible with the current library version 315000 of WinCC OA.
It might be from version
What is funny, that my colleagues use the same version and patch of WinccOA, they do register the subproject the same way as I, but my gedi refuses to start. We all use v3.15 p013
WCCOAui (1), 2018.10.24 19:16:11.972, CTRL, WARNING, 5/ctrl, Location of the following log entry: D:\\ScadaRepository\\DSM\\DSM_20181018\\scripts\\libs\\RcmCore/RcmCoreUtils.ctc, Line:4
WCCOAui (1), 2018.10.24 19:16:11.972, SYS, WARNING, 133, Could not load shared library D:\\ScadaRepository\\DSM\\DSM_20181018\\bin\\CtrlRcmCore.dll, Access is denied.
WCCOAui (1), 2018.10.24 19:16:11.999, CTRL, SEVERE, 5/ctrl, Location of the following log entry: D:\\ScadaRepository\\DSM\\DSM_20181018\\scripts\\libs\\RcmCore/RcmCoreUtils.ctc, Line:4
WCCOAui (1), 2018.10.24 19:16:11.999, IMPL, FATAL, 54, Unexpected state, The Ctrl Extension D:\\ScadaRepository\\DSM\\DSM_20181018\\bin\\CtrlRcmCore.dll is not compatible with the current library version 315000 of WinCC OA.
It might be from version
- mkoller
- Posts:741
- Joined: Fri Sep 17, 2010 9:03 am
Re: Ctrl Extension compatibility problem
"Access is denied."
This is the information from the OS.
Any file access right problems ?
This is the information from the OS.
Any file access right problems ?
- riso77
- Posts:16
- Joined: Mon Jan 15, 2018 10:57 am
Re: Ctrl Extension compatibility problem
Thank you very much Martin,
moving the subproject over to drive C: (in Windows) did the trick. That means there must be something preventing WinccOA to access D: drive in my case.
Richard
moving the subproject over to drive C: (in Windows) did the trick. That means there must be something preventing WinccOA to access D: drive in my case.
Richard