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

Fix a WinCC SIMATIC Logon Dialog That Does Not Reopen After Cancellation

Fix a WinCC SIMATIC Logon Dialog That Does Not Reopen After Cancellation

In the reported PCS 7 V9.0 SP3 configuration, first resolve the version discrepancy and verify the installed WinCC and SIMATIC Logon updates. Siemens lists WinCC V7.4 SP1 Update 19 as the component level for PCS 7 V9.0 SP3 UC04, but the Update 19 notes do not confirm a fix for this exact canceled-dialog symptom. Treat that update as a supported candidate baseline to test, not a guaranteed repair.

Table of Contents

Applies To

The report gives conflicting WinCC versions. The opening says WinCC V7.5, while the clarification identifies SIMATIC PCS 7 V9.0 SP3 with WinCC V7.4 SP1 Update 14, and uses the OS Project Editor plus a SIMATIC Logon button in an overview PDL. Confirm the installed versions from the actual OS before acting. The guidance below is bounded to the clarified PCS 7 V9.0 SP3 configuration.

What the Update Evidence Establishes

Siemens' PCS 7 V9.0 SP3 Readme lists WinCC V7.4 SP1 Update 14 for the base SP3 release, Update 19 for UC04, Update 20 for UC05, and Update 21 for UC06. Therefore Update 19 is part of the PCS 7 V9.0 SP3 UC04 component baseline. Siemens' WinCC Update 19 Readme includes Update 5 for SIMATIC Logon and lists various WinCC improvements, but the checked notes do not identify the reported canceled-login-dialog behavior as a corrected defect.

The thread's Update 19 suggestion is a useful version-specific lead, not proof that installing it resolves this symptom. The ticket contains no follow-up confirming the result.

Controlled Update and Reproduction Procedure

  1. On the affected OS server, record the exact PCS 7 version/update, WinCC version/update, SIMATIC Logon version/update, OS Project Editor configuration, and whether the behavior occurs on another project. Resolve the V7.5 versus V7.4 SP1 discrepancy before selecting media.
  2. If the installation is PCS 7 V9.0 SP3, compare its component levels with the PCS 7 Readme for the intended Update Collection. For UC04, the Readme lists WinCC V7.4 SP1 Update 19 and SIMATIC Logon V1.6 Update 5. Do not choose Update 19 solely because the forum reply named it; verify the full UC baseline and compatibility for every installed component.
  3. In a maintenance window, back up the project and system, review the applicable PCS 7/WinCC readmes and prerequisites, and plan a coordinated update of every PC on which WinCC V7.4 SP1 is installed. Siemens' Update 19 notes say to exit applications before installation and state that clients and servers in a distributed system must be updated; different update levels prevent configuration changes in the WinCC project.
  4. Reproduce the sequence in a controlled test or approved maintenance condition: activate the OS project, cancel the initial SIMATIC Logon dialog, then use the configured login button. Record whether the dialog opens and whether project deactivation/reactivation is still required. Repeat with the site's normal user/session conditions.
  5. If the symptom persists at a supported, consistent update level, collect the project configuration, Windows/WinCC/SIMATIC Logon versions, reproduction steps, and relevant diagnostics for Siemens support. Do not change button scripts or OS Project Editor settings without identifying a documented setting that applies to the installed release.

Expected Result and Interpretation

The practical target is that the login button can open the SIMATIC Logon dialog again after the initial dialog is canceled. The thread does not confirm that Update 19 achieved this. A successful update installation alone is not verification; test the interaction in the intended project and record the result.

Verification

Verify all distributed OS nodes have the intended, consistent component levels, then execute the cancel-and-reopen sequence on the affected OS. Confirm the dialog appears without deactivating and reactivating the project, and separately check another project if the issue was reported there. If this behavior remains reproducible, retain the version inventory and diagnostic evidence for escalation.

Limitations and Operational Precautions

The initial V7.5 statement conflicts with the later PCS 7 V9.0 SP3 / WinCC V7.4 SP1 Update 14 clarification. Update 19's release notes do not identify this specific symptom as fixed, and the source does not report an outcome after the suggested update. Treat Update 19 as a candidate component level within PCS 7 V9.0 SP3 UC04, not a guaranteed repair. A distributed PCS 7 update affects multiple stations; use a tested backup, a planned maintenance window, and site-specific rollback and availability controls.

Engineer FAQ

Does WinCC V7.4 SP1 Update 19 fix this exact login-popup symptom? The checked Update 19 notes do not identify that defect, and the thread reports no test result. The fix remains unverified.

Is Update 19 applicable to PCS 7 V9.0 SP3? Siemens' PCS 7 Readme lists WinCC V7.4 SP1 Update 19 in the PCS 7 V9.0 SP3 UC04 component baseline. Apply a full compatible UC only after checking the installed system and prerequisites.

Why must the version discrepancy be resolved first? The post says V7.5 initially but later identifies V7.4 SP1 Update 14. Those are different baselines; instructions for one should not be assumed to apply to the other.

Technical References

  • Siemens, PCS 7 Readme V9.0 SP3 UC06, section 6, software-component baseline table: https://cache.industry.siemens.com/dl/files/521/109778521/att_1026553/v2/pcs7-readme_en-US.pdf
  • Siemens, SIMATIC HMI Update 19 (K7.4.1.19) to WinCC V7.4 SP1 — Notes for Installation and Use, including scope of delivery, installation in distributed systems, and listed improvements: https://cache.industry.siemens.com/dl/files/846/109806846/att_1096668/v1/WinCC_V74_SP1_Update19_Readme.pdf

Related Articles

Related Tags

PCS 7 V9.0 SP3, WinCC V7.4 SP1, Update 19, SIMATIC Logon, OS Project Editor, runtime login

20 respuestas