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

How to Resolve WinCC Web Publishing Wizard Errors and Update Outdated WebNavigator Graphics

How to Resolve WinCC Web Publishing Wizard Errors and Update Outdated WebNavigator Graphics

In SIMATIC PCS 7 WinCC WebNavigator, Web Publishing Wizard errors or published graphics failing to update on remote web clients are caused by file locking from active Internet Information Services (IIS) worker processes (w3wp.exe) or corrupted caching in the published web directory. The Web Publishing Wizard compresses and converts WinCC process pictures into web-compliant formats; if existing published files are locked by connected clients, the wizard silently skips or aborts the publication. Stopping the WebNavigator website, clearing the published pictures directory, and re-running the Web Publishing Wizard resolves the fault.

Table of Contents

Architecture of WinCC Web Publishing and Graphic Conversion

SIMATIC WinCC WebNavigator enables thin-client operator visualization across local intranets and plant networks using standard web browsers (such as Internet Explorer with ActiveX controls or WinCCViewerRT).

Unlike standard OS Clients that open native .pdl graphic pictures directly from the OS Server share, WebNavigator clients require process graphics to be pre-processed into optimized web-compatible formats:
1. The Web Publishing Wizard: An engineering tool executed in WinCC Explorer that parses native .pdl pictures, scripts, and referenced graphic resources (.bmp, .png, .jpg, .emf).
2. Compression and Staging: The wizard generates compressed data streams, extracts dynamic tag linkages, and stages the published assets in the web server publication directory (typically <Project_Folder>\Web\Pictures or <Project_Folder>\WebNavigator\Graphics).
3. IIS Delivery: Microsoft Internet Information Services (IIS) hosts the WebNavigator application pool, serving published pages to authenticated thin clients.

Root Cause Analysis for Publishing Wizard Aborts and Stale Graphics

When modifying process pictures on the Engineering Station or OS Server, engineers frequently run the Web Publishing Wizard, only to discover that the wizard halts with an error, or remote web clients continue rendering obsolete, outdated graphics.

Underlying Causes

  • File Locking by Active IIS Worker Threads: When operators are actively viewing graphics on WebNavigator clients, the IIS worker process (w3wp.exe) maintains shared file read locks on the published files in the web root. When the Web Publishing Wizard attempts to overwrite a modified picture, Windows denies write access, causing the wizard to abort or skip the file.
  • Corrupted Publishing Cache: If a previous publishing session was cancelled midway or encountered an unhandled exception, temporary .tmp files and orphaned registry pointers remain in the web directory, preventing the wizard from completing contiguous compilations.
  • Non-Web-Compliant Graphic Objects: Custom third-party ActiveX controls, Windows Forms components, or nested complex grouped shapes that are unsupported by the WebNavigator client engine can cause the conversion parser to crash.

Step-by-Step Web Publishing Recovery Procedure

To resolve publishing errors and force a clean, complete regeneration of all web graphics:

Step 1: Temporarily Halt WebNavigator IIS Services

  1. On the WebNavigator Server (OS Server or dedicated Web Server), open Windows Command Prompt as Administrator.
  2. Stop IIS services to release all file locks held by connected web clients:
    cmd iisreset /stop
  3. Open Windows Task Manager; confirm that w3wp.exe is completely terminated.

Step 2: Purge the Published Graphics Directory

  1. Open Windows Explorer and navigate to the WinCC project directory.
  2. Locate the WebNavigator publication directory:
    <Project_Directory>\WebNavigator\Pictures (or <Project_Directory>\Web\Pictures).
  3. Delete all files inside the Pictures folder (or move them to a temporary backup directory).
    (Note: Do not delete the native project GraCS directory; only clear the published web cache folder).

Step 3: Execute the WinCC Web Publishing Wizard

  1. Open the WinCC project in WinCC Explorer.
  2. In the navigation pane, right-click Web Navigator and select Web Publishing Wizard (or launch from Tools).
  3. In the wizard dialog:
    * Select Publish pictures and scripts.
    * Under Picture Selection, select All pictures (or specifically select the modified pictures).
    * Ensure that 'Save pictures in compressed format' is checked.
  4. Click Start. The wizard will compile each .pdl cleanly into the empty directory without file-lock collisions.

Step 4: Restart IIS and Reconnect Web Clients

  1. In the administrative command prompt, restart IIS:
    cmd iisreset /start
  2. On the WebNavigator client machine, clear the browser cache or delete temporary Internet files to ensure the client downloads the newly published assets.

WebNavigator Component and Diagnostic Log Reference Matrix

The following table outlines the diagnostic files and service components associated with WinCC WebNavigator publishing:

Component / FileFile System LocationPrimary FunctionFault Indicator / ActionWeb Publishing WizardWinCC Explorer EditorCompiles .pdl to web formatWizard aborts; stop IIS and purge cachePublished Web Directory<Project>\WebNavigator\PicturesStores converted web assetsStale graphics; delete files and re-publishw3wp.exeWindows IIS Worker ProcessServes HTTP/ActiveX streamsHolds file locks; restart via iisresetWebNavigator.logSiemens\WinCC\DiagnoseDiagnostic error logCheck for conversion parsing errorsClient Download CacheC:\Users\<User>\AppData\Local\TempLocal client cacheClear browser cache if display doesn't update

Maintaining clean publication folders ensures 100% reliable graphic synchronization across remote clients.

Verification

To verify that web publishing was successful:
1. Confirm that the Web Publishing Wizard completes with the message: 'Web Publishing Wizard completed successfully. 0 Errors'.
2. Open Windows Explorer and verify that the <Project>\WebNavigator\Pictures directory is populated with freshly dated converted files.
3. Launch WinCCViewerRT or Internet Explorer on a remote WebNavigator client.
4. Log on and navigate to the newly published process picture.
5. Confirm that all graphical modifications, newly added block icons, and dynamic analog values update in real time without rendering artifacts.

Limitations and Operational Precautions

  • Halting IIS via iisreset /stop temporarily disconnects all active remote web operators; execute publishing during low-activity operating windows.
  • Never publish graphics directly across a slow WAN connection; always run the Web Publishing Wizard locally on the WebNavigator server.
  • Ensure all custom fonts used in process pictures are installed on the WebNavigator client workstations to prevent text overlapping.
  • Verify that user process pictures do not exceed 1920x824 pixels to avoid horizontal and vertical scrollbars on standard thin-client displays.

Engineer FAQ

Why do web clients show old pictures even after the publishing wizard finished?

Web clients cache downloaded graphic files locally in Internet Explorer temporary files or WinCCViewerRT cache. Clearing the client browser cache forces a fresh download from the server.

Can I publish a single modified picture without publishing the entire project?

Yes. In the Web Publishing Wizard, select 'Select pictures' instead of 'All pictures', and choose only the modified .pdl files to save publishing time.

What does the error 'Picture cannot be converted' indicate during publishing?

This error occurs when a .pdl contains unsupported third-party OCX controls, corrupted grouped objects, or when the picture file itself is locked by Graphics Designer.

Technical References

Related Articles

Related Tags

  • WebNavigator
  • Web_Publishing_Wizard
  • IIS
  • Graphics_Designer
  • Thin_Client
6 respuestas