November 30, 2020 at 7:32 pm #7621
I have installed the Automatic Control Module v126.96.36.199 in Rapid Scada v188.8.131.52.
No matter how, the module doesn’t display the Computor Code to allow for purchase/registration.
I have restarted the ScadaServer service (as stated) and also the Administrator and even the Windows Server machine to no avail.
Your assistance with this issue, please.
Thanks in advance.December 1, 2020 at 12:00 pm #7624
The module also writes the code to it’s log file C:\SCADA\ScadaServer\Log\ModAutoControl.log
Please check the file.December 1, 2020 at 12:16 pm #7628
I’m afraid this didn’t work. The ModAutoControl.log file is empty.
Just to note I had to “Unblock” the module’s DLL (Win Server 2012 R2) to allow the module to be activated, but even after that the ‘Computer code’ text box appears grayed out.
I have tried Deactivating and re-Activating the module several times (restarting server service and even rebooting the machine), to no avail.
December 2, 2020 at 2:07 pm #7632
- This reply was modified 6 months, 2 weeks ago by Mikhail.
The ModAutoControl.log file is empty.
It means that the module doesn’t work.
Please check ScadaServerSvc.log for additional info.December 2, 2020 at 7:16 pm #7637
I have scanned the ScadaServerSvc.log file and found no indication whatsoever of a problem. There’s also no mention to the ModAutoControl module in it.
¿Could this be a permissions or a .NET runtime lib issue?December 3, 2020 at 12:43 pm #7639
We have solved the issue.
At first we followed the procedure for installation of the module and then activating it, uploading the config and then restarting the server and Administrator.
The problem was the module was blocked by Windows Server (WS2012R2) and we had to “Unblock” it from the .dll file Properties dialogue.
After that was done, there was no indication the module was running because the config had to be uploaded again to the Scada server.
After that was done, we got the module to write to the log file, return the computer ID and running as expected.
Just to note: We tried this procedure in a new machine with Windows Server 2019 and it worked too, but in this case the ModAutoControl.dll file wasn’t blocked by the OS and the procedure was more straightforward.December 3, 2020 at 12:54 pm #7640
Thank you for the description of the final solution. I’m glad that you fixed it.
- You must be logged in to reply to this topic.