Resolving Web View Publisher Run-Time Error 5 and Typicals Corruption in PCS 7 Web Navigator

In SIMATIC PCS 7 Web Navigator (V8.1 and V8.2), Web View Publisher crashing with 'Run-time error 5: Invalid procedure call or argument' occurs when parsing master block typical pictures (@PCS7TypicalsBasisLibraryV8.PDL or @PCS7TypicalsAPL.PDL) that contain corrupted user objects, deleted property references (e.g., DataSet1:Double0), or missing COM/ActiveX controls. To resolve this, restore pristine typical templates from the WinCC installation path, run a consistency check on affected PDLs in Graphics Designer, and publish only active runtime process pictures.

Root Cause Analysis of Web View Publisher Run-Time Error 5

In SIMATIC PCS 7 Operator Stations equipped with the WinCC Web Navigator option, publishing process screens using the Web View Publisher tool converts native WinCC screens (.pdl) into web-optimized vector graphics and JavaScript/VBScript runtime modules.

When an engineer launches the publishing wizard on Windows Server or Windows 7, the process halts unexpectedly with the fatal Visual Basic runtime exception:
Run-time error '5': Invalid procedure call or argument

Inspection of the publisher diagnostic log file reveals repeated error entries:
* Error in picture @PCS7TypicalsBasisLibraryV8.PDL
* Property DataSet1:Double0 referenced an object that no longer exists
* Property Text on @@SFC_TYPE/2 missing binding descriptor

This failure is caused by Graphic Template Schema Corruption:
1. When projects are migrated across PCS 7 versions (e.g., from V7.1 or V8.0 to V8.1) or opened on systems with different installed optional packages, master template screens (such as @PCS7TypicalsBasisLibraryV8.PDL and @PCS7TypicalsAPL.PDL) accumulate orphaned user-object property links.
2. The Web View Publisher uses a strict COM-based parsing engine. When the parser encounters an object property referencing a deleted sub-object or an unregistered ActiveX control, Windows API functions return an invalid argument exception, crashing the publisher with Error 5.

Web Publishing Error Codes and Graphic Artifact Matrix

Understand typical failure signatures encountered during WinCC Web Navigator publishing:

Publisher Error / Diagnostic EntryUnderlying Graphic DefectTarget File in GraCSCorrective ActionRun-time error '5'Orphaned COM property pointer or invalid procedure call@PCS7TypicalsBasisLibraryV8.PDLRestore clean typical template from install mediaDataSet1:Double0 property missingBroken dynamic dialog binding on user object@PCS7Typicals...Re-save picture in Graphics Designer to purge orphan linksActiveX control not registeredMissing 32-bit OCX component on Web ServerProcess Faceplates (@pg_*.pdl)Register OCX via regsvr32 from SysWOW64Run-time error '429': ActiveX cannot create objectMissing Web Navigator server runtime componentsSystem-wideReinstall Web Navigator Server components

Engineering notice: Master typical pictures (@PCS7Typicals) are engineering templates and do NOT need to be published for Web Clients.

Repairing Corrupted Typical Master Screens (@PCS7Typicals*.pdl)

To restore integrity to the project's graphic master templates:

Restore Pristine Master Typicals from Delivery Directory:
* Navigate to the master installation delivery path:
C:\Program Files (x86)\Siemens\WinCC\Options\PDL\Faceplates_PCS7_EU\
* Locate the original clean template files:
- @PCS7TypicalsBasisLibraryV8.PDL
- @PCS7TypicalsAPL.PDL
- @PCS7Typicals.PDL
- Copy these files and overwrite the corrupted files in your project's GraCS directory:
  <ProjectPath>\GraCS\
Re-Save Screens in Graphics Designer:
* Open the newly restored @PCS7TypicalsBasisLibraryV8.PDL in Graphics Designer.
* Perform a dummy modification (e.g., move an object by 1 pixel and move it back).
* Click Save: This forces the Graphics Designer compiler to validate all internal user object pointers and purge legacy database fragments.
* Close Graphics Designer.

Configuring Web View Publisher Scope to Exclude Master Libraries

Master typical pictures exist solely on the Engineering Station to allow the OS Compiler to spawn block icons; they are never viewed by operators:

Launch Web View Publisher:
* In WinCC Explorer, right-click Web Navigator and select Web View Publisher.
Configure Publishing Scope:
* In the Select Pictures step, select Select Pictures Individually.
* Check all actual operator process screens (e.g., Overview.pdl, Unit_Reactor.pdl, @Overview1.pdl, and standard faceplates @pg_*.pdl).
* UNCHECK all master template files:
- Uncheck @PCS7Typicals*.pdl
- Uncheck @Template.pdl
- Click Publish: Because the corrupted engineering templates are excluded from the conversion queue, the publisher processes all runtime screens cleanly to 100% completion without encountering Error 5.

Verification

Verify web publishing execution:
1. Run Web View Publisher on the Engineering Station: Confirm that the publishing progress bar advances smoothly from 0% to 100% with zero runtime errors.
2. Download the OS project to the Web Server.
3. Open a remote Web Navigator client session: Confirm that process screens load crisply, faceplates open, and live values update without script errors.

Limitations and Operational Precautions

Never attempt to publish corrupted graphics by ignoring publisher errors; corrupted web scripts can cause Internet Explorer or WinCCViewerRT to crash unexpectedly on operator workstations.
Always back up custom user-created typicals before restoring catalog templates from the Siemens installation folder.
Ensure all Web Clients have the matching version of Web Navigator Client plugins installed (e.g., V8.1 plugins for V8.1 Web Server).

Engineer FAQ

Do operators on Web Clients need @PCS7Typicals pictures?

No. Operators only view instantiated process screens. '@PCS7Typicals' pictures are used strictly by the OS Compiler during engineering to generate block icons.

Why did Web View Publisher work on Windows 7 but fail on Windows Server?

Windows Server enforces strict User Account Control (UAC) and Data Execution Prevention (DEP). Corrupted COM pointers that Windows 7 ignored will trigger fatal access violations and runtime errors under Windows Server.

Can I publish only modified pictures to save time?

Yes. In Web View Publisher, check 'Publish modified pictures only'. The wizard evaluates timestamps and publishes only screens that were edited since the last run.