Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Schneider Electric Global Website×
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
Goals and Symptoms
When attempting to access the project in the web client for Powerlogic SCADA (PLS), all values return as #COM and a popup message of "No Protection Key is Found" is received. However, everything is functioning properly in Runtime on the server machine; there are no #COMs being returned.
Causes and Fixes
Ensure that the Loopback IP Address (127.0.0.1) is NOT being used in the project. This includes the primary project AND any of the included projects.
1. Highlight the project in the Citect Explorer.
2. In the Citect Project Editor, click on "Servers" and select "Network Addresses"
3. Scroll through the Network Addresses and change any that are using the Loopback Address to the actual assigned IP address for the network card connecting to the system devices.
4. Repeat this process for all Included Projects.
Note: You can determine which projects (if any) are included in the primary project by clicking on "System" and selecting "Included Projects" in the Citect Project Editor, while the primary project is highlighted in the Citect Explorer.
The Loopback Address is convenient for testing purposes; however, it is highly recommended to use the actual assigned IP addresses for the Network Addresses when putting the project into Live Conditions. This is necessary because remote clients need to know where to look (which IP on the network) for data from the devices. If the Loopback Address is used in the project, remote clients look to themselves for data and for licensing, which results in the aforementioned behavior.
Keywords: PowerLogic SCADA v7.10 r01, r01.1, r01.2, PLS 7.1, Power SCADA, PowerSCADA, webclient, communication loss, software protection failure