C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Installing SIMATIC PCS 7 PowerControl V8.1 - Resolving PendingFileRenameOperations Loops and DBA Licensing

Installing SIMATIC PCS 7 PowerControl V8.1 - Resolving PendingFileRenameOperations Loops and DBA Licensing

When installing SIMATIC PCS 7 PowerControl V8.1 and the setup continuously aborts with the persistent error 'Please restart your system before installing any new component' despite multiple reboots, the failure is caused by a locked Windows Registry key: PendingFileRenameOperations. Windows Installer or third-party background utilities repeatedly regenerate pending file rename flags upon restart. To bypass this loop, open regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager, delete or clear the PendingFileRenameOperations value, and immediately launch the PowerControl setup without rebooting. Following installation, ensure that the dedicated engineering license SIMATIC PCS 7 PowerControl DBA is installed in Automation License Manager; otherwise, creating an AS Source Node will fail with 'License not granted'.

Table of Contents

SIMATIC PCS 7 PowerControl Architecture and the DBA Installation Engine

SIMATIC PCS 7 PowerControl integrates electrical switchgear, protection relays, and power distribution infrastructure (medium/low voltage switchgear) into the central PCS 7 process control system. It bridges the gap between process automation and electrical power management.

The PowerControl installation suite comprises several interdependent components:

  1. PCS 7 PowerControl Core: System libraries, driver blocks (PC_FEEDER, PC_TRAFO), and WinCC graphic typicals.

  2. PCS 7 PowerControl DBA (Database Automation): The specialized engineering tool used to parse electrical engineering files (such as IEC 61850 *.SCD files or PROFIBUS GSDs) and automatically generate WinCC OS tags, alarms, and block icons.

  3. Communication Drivers: S7-400 PROFIBUS DP drivers and WinCC Industrial Ethernet IEC 61850 MMS channel drivers.

When installing PowerControl onto an existing PCS 7 engineering machine, engineers frequently hit setup execution barriers.

The Windows Installer 'PendingFileRenameOperations' Deadlock Mechanism

The notorious installation error:

'Please restart your system before installing any new component.'

is enforced by the Siemens setup bootstrapper to guarantee that operating system files, DLLs, and registry hooks are not locked in memory by pending Windows updates or previous uninstalls. The mechanism operates as follows:

  • The setup checks the Windows Registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations.

  • If this multi-string value contains any file paths scheduled for deletion or renaming during boot, Siemens setup assumes a reboot is pending and halts.

  • The Deadlock: Certain third-party software (such as antivirus scanners, backup agents, or Windows Update services) repeatedly write entries into PendingFileRenameOperations upon every system startup. As a result, the engineer restarts repeatedly, but the registry value is instantly repopulated, creating an infinite reboot loop.

Step-by-Step Registry Intervention to Clear the Reboot Loop

To break out of the infinite reboot cycle, an explicit manual intervention in the Windows Registry is required:

  1. Open the Windows Run dialog (Win + R), type regedit, and press Enter.

  2. Navigate to the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.

  3. In the right-hand panel, locate the value PendingFileRenameOperations.

  4. Right-click PendingFileRenameOperations and select Delete (or double-click and clear all text strings inside it).

  5. Critical Step: Do NOT restart the computer! Launch the PowerControl Setup.exe immediately while the registry key is clean. The setup bootstrapper will detect zero pending operations and proceed with package installation.

PCS 7 PowerControl DBA Licensing Requirements (AS Source Node Creation)

Once the software installs successfully, engineers frequently encounter a second stumbling block when opening the DBA tool to configure IEC 61850 substation data: clicking 'Create AS Source Node' triggers the error:

'License not granted. The application will be closed.'

This occurs because the Database Automation tool requires an explicit commercial license in Automation License Manager:

  • SIMATIC PCS 7 PowerControl DBA: The dedicated engineering license authorizing the DBA compiler to parse SCD files, generate AS source nodes, and compile tags into WinCC.

  • Without this license installed on the local Engineering Station drive, DBA operates in demo mode or locks access to AS source node generation.

Comparative Diagnostic Matrix: PowerControl Installation and Startup Faults

The following table diagnoses common errors encountered during PowerControl V8.1 deployment:

Error SymptomUnderlying Root CauseVerificationCorrective Action'Please restart your system' loopLocked PendingFileRenameOperations registry keyInspect Session Manager in regeditDelete PendingFileRenameOperations; run setup immediately'License not granted' on AS NodeMissing PowerControl DBA engineering licenseCheck ALM for PowerControl DBA keyInstall SIMATIC PCS 7 PowerControl DBA license via ALMWinCC Component IncompatibilityWinCC update mismatch (e.g., V7.3 SE Upd1 vs Upd4)Check WinCC Installed UpdatesInstall certified WinCC update matching PowerControl releaseSCD Import Fails (Schema Error)Incompatible IEC 61850 SCL schema versionInspect XML headers of *.SCD fileUpdate device descriptions or use IEC 61850 Edition 2 schemaChannel Diagnosis Error 0x4104Missing MMS channel license or wrong IPWinCC Channel DiagnosisVerify IED IP address and WinCC IEC 61850 MMS driver license

Commercial Accuracy Disclaimer

Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

SIMATIC PCS 7 PowerControl requires distinct software licenses for engineering (PowerControl DBA) and runtime operations (WinCC PowerControl OS RT POs and IEC 61850 driver tags). Verify all required MLFBs with an authorized Siemens distributor prior to project commissioning.

Step-by-Step Procedure to Install and License PCS 7 PowerControl V8.1

Follow this complete procedure to deploy PowerControl V8.1 successfully:

  1. Clear Registry Deadlock:
    - Launch regedit as Administrator.
    - Delete PendingFileRenameOperations under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.

  2. Execute Installation:
    - Insert or mount the SIMATIC PowerControl V8.1 DVD.
    - Right-click Setup.exe and select Run as administrator.
    - Select components: PCS 7 PowerControl Core, DBA Tool, and Documentation.
    - Allow the installer to complete without interruption.

  3. Install Required Licenses in ALM:
    - Open Automation License Manager.
    - Transfer the SIMATIC PCS 7 PowerControl DBA license key to drive C:.
    - Verify that the license state is 'Valid' with green checkmarks.

  4. Configure DBA Project and AS Source Node:
    - Open PCS 7 DBA from the Start Menu.
    - Link the DBA project to your active PCS 7 Multiproject.
    - Right-click AS Nodes -> New AS Node....
    - Confirm that the AS Node creates successfully without licensing popups.
    - Import the substation SCD file and compile to WinCC.

Verification

Verify correct installation and operation through these checks:

  1. Open SIMATIC Manager -> Help -> Installed Software. Confirm that PCS 7 PowerControl V8.1 and PCS 7 PowerControl DBA are listed.
  2. Launch PCS 7 DBA. Create an AS Source Node and confirm that the license handshake succeeds.
  3. Import a sample *.SCD file. Confirm that electrical IEDs and protection blocks populate the DBA tree.
  4. Execute an OS compile from DBA. Open WinCC Graphics Designer and verify that PowerControl block icons (PC_FEEDER) generate cleanly in process pictures.

Limitations and Operational Precautions

  • WinCC Update Alignment: PowerControl V8.1 base requires WinCC V7.3 SE Upd1 to Upd3. PowerControl V8.1 SP1 requires WinCC V7.3 Upd4 to Upd14. Installing mismatched updates can crash the WinCC Graphics Designer during typical generation.
  • Registry Backup: Always export a backup of the Session Manager registry key before editing regedit.
  • Antivirus Exclusion: Add the Siemens PowerControl installation temporary extraction directory to your antivirus exclusions to prevent antivirus locks from re-triggering PendingFileRenameOperations.

Engineer FAQ

Why does Windows regenerate PendingFileRenameOperations?

Operating system updates, printer drivers, or antivirus utilities place files in a temporary staging area and register them to be renamed or deleted during the next system reboot.

Is it safe to delete PendingFileRenameOperations?

Yes. Deleting the registry key is a standard, widely documented Siemens workaround that allows installations to proceed. It does not harm the operating system.

What is the difference between standard PCS 7 DBA and PowerControl DBA?

Standard DBA is used to integrate non-PCS 7 PLCs (S7-300, S7-1500). PowerControl DBA includes specialized parsers for IEC 61850 substation configuration files (*.SCD, *.CID, *.ICD).

What should I do if deleting the registry key doesn't work?

Check for a second registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired. If present, delete RebootRequired as well.

Where can I find the PowerControl DBA application manual?

Siemens documents the complete workflow in SIOS Application Example 64196173 ('DBA Configuration for PowerControl').

Technical References

Related Articles

Related Tags

  • PowerControl
  • DBA
  • PendingFileRenameOperations
  • Registry Fix
  • IEC 61850
  • Installation Loop
  • WinCC V7.3
6 respuestas