Citect Scada Software Protection Failure

Posted on by admin

Schneider Electric Scada Global Support Provides Troubleshooting and Technical Tips • 1. SCADA & MES Global Supportpresents troubleshooting andtechnical tips • IntroductionPresenters:L. Duguid – Senior Global Support Engineer● Top Five Issues raised with Support (SCADA)T.

Montmayeur – Senior Global Support Engineer● Best Practices for Upgrading Vijeo Citect / CitectSCADASCADA & MES Global Support Portal:www.citect.schneider-electric.comSchneider Electric - Industry - O&O Software Activity - SCADA Troubleshooting Tips Copyright © 2012 2 • Top Five Issues Raised with SupportPresented by L. Driver Debugging 2. Web Client / Server Issues 3. Cicode Debugging 4. Clustering 5.

Vijeo citect scada software

Schneider Electric Scada Global Support Provides Troubleshooting and. Software protection failure on. Upgrading SCADA guidelines http://www.citect.schneider. Oct 12, 2000  CITECT Softtware protection failure UsersList. Software protection Failure occurs when CITECT runs. My CITECT application > for a Water SCADA applicationhave. Software Protection Failure on a Web Client. The main benefit of Citect SCADA WebClient is that the majority of the configuration is „Server-Side‟. Client License - Software protection failure On our plant we have an server license, and 1 control license for client. Now i have updated the USB key, so in the key update tool is the following information.

Moderators note: Multiple responses are combined in this message. ---------- Load Citect Service Pack B We got various DR Watsons. With NT prior to Service Pack B ----- Message Separator ----- Hi Greg Try installing the latest Sentinel Driver V5.38 from the website link Check your syslog.dat for key failure messages. Regards Stephen Byrne Support Engineer Citect Support Sydney ----- Message Separator ----- We had a similar problem - running V5.20 and SP4.

The media files you download with rsymedia.com must be for time shifting, personal, private, non commercial use only and remove the files after listening. It is illegal for you to distribute copyrighted files without permission. Manvantara kannada serial song free download.

It wasnt as often as once per week. We have since upgraded to V5.21, AND changed the licence key ( as part of licence upgrade, not specifically as a fix for the problem). Changing to the latest sentinal drivers didnt help us, swapping keys between machines didnt help, problem has now gone away. Id put my money on the key, or a key / hardware combination. Its a nasty problem to fault find, because you dont get any alarms or fault logs. We found we had to re-start the COMPUTER before it could find the key again. Good luck David Flew ----- Message Separator ----- Greg, Swap the licenses between the 2 IOSERVERS and see if the problem stays on the PC or goes with the license.

Tom DENT PORTLAND ALUMINIUM PRIVATE BAG 1 PORTLAND 3305 AUSTRALIA ----- Message Separator ----- I once had a problem like this. My project crashed every 6h 30min. Citect Tech Support recommended that I upgrade the version of the Sentinel driver to 5.38. But the real cause was a leak in Citect.

Watch the file handles counter in Task Manager - this should not increase much, during the week. In my project, calling FileFind( c:fred.txt ) consumed an extra handle, 1 every 10s when it was called. After 6h 30min, there were no more file handles available to the system. When the Sentinel driver couldnt get a file handle, the authentication of the dongle must have failed. Citect reported a Software Protection Failure, and shutdown.

I modified my project to avoid using FileFind. Alternatively, release the consumed file handle by calling FileFind() repeatedly, until it returns an empty string. CiT said the problem with FileFind should be fixed some time, perhaps as a service pack for 5.21. Peter Vickery ----- Message Separator ----- Please, update now AT LEAST to SP3, SP1 can be problems accesing to parallel ports Rergards: ------------- Alvaro Llamas allamas@emuasa.es ----- Message Separator ----- Greg, The only time I have seen this problem is when a printer is connected to the same port as the dongle.

Do you have a printer connected? In my case, I have lost the connection to the key when using it in conjunction with a bi-directional printer. Since there was no error message, I could only conjecture as to the real problem. I suspect that bi-directional print drivers can hold the port busy for too long of a period causing the dongle code to return a failure to Citect. I agree that upgrading the NT service packs could help. Also, check to see if the dongle service has an update. I run Windows NT (Workstation) Service Pack 5.

I recommend at least Service Pack 4.

On our plant we have an server license, and 1 control license for client. Now i have updated the USB key, so in the key update tool is the following information: 1 full license 2 control clients Software version V7.20 + SP2 Now on second PC, i have installed runtime, and configured all settings. When i start runtime, the project opens up, and after 30 seconds, it close, and got the message: 'Software protection failure, No key found or no license available from network' The second PC is configured the same as the first PC, witch will work correctly. Only diffrence is that the new client PC is not in the same network. We have two separate networks on our plant, one for normal office, and one for factory automation. The second control PC is in office network, but we have created an route via router to the factory network. I can ping, share folders and setup an remote desktop connection to the scada PC, so the connection is OK.