Comprehensive PCS 7 System Diagnostics and Software Inventory Profiling via s7aversx.exe

In SIMATIC PCS 7, systematic troubleshooting requires exporting an exact software and hardware inventory using the Siemens Installed Software Information utility (s7aversx.exe). Located in the Common Files directory or accessible via Windows search, s7aversx.exe queries the Windows registry and component manifests to export a complete CSV file detailing installed PCS 7 versions, Service Packs, Update Collections (UC), standalone component updates (CFC, SFC, WinCC, BATCH), and SIMATIC Device Drivers. Along with s7aversx.exe exports, technical support tickets require: operating system build, migration pedigree, failure recurrence frequency, active workarounds, recent changes, hardware order numbers (MLFBs), and firmware revisions.

Executive Summary

Troubleshooting complex engineering, communication, or runtime anomalies in SIMATIC PCS 7 often stalls due to incomplete system profile data. Because PCS 7 integrates dozens of interconnected software subsystems—including STEP 7, CFC, SFC, WinCC, SIMATIC NET, and specialized driver libraries—subtle version disparities between an Engineering Station (ES) and redundant Operator Stations (OS) induce unpredictable runtime faults. Relying on generic version claims (e.g., 'PCS 7 V9.0') is insufficient. This guide establishes the mandatory technical support data-gathering framework and details the execution of s7aversx.exe to produce audit-grade software inventories.

Architecture and Fundamental Mechanics

The SIMATIC PCS 7 software architecture is a coordinated federation of independent packages. Each package (such as CFC V9.0 SP3 Upd5 or WinCC V7.4 SP1 Upd7) installs specific dynamic link libraries (.dll), automation servers, and database schema extensions. Siemens maintains a central component registration registry monitored by the Version Information tool s7aversx.exe (SIMATIC Version Viewer).

When executed, s7aversx.exe interrogates the Windows registry, the SIMATIC product registration database, and file headers across %ProgramFiles(x86)%\Siemens and %CommonProgramFiles(x86)%\Siemens. It generates an exhaustive breakdown categorized into:
1. Top-Level Product: The core PCS 7 installation package, release tier, and active Service Pack.
2. Sub-Components: Granular versions, build numbers, and patch levels for engineering tools (STEP 7, CFC, SFC, PDM, TH).
3. Runtime Engines: WinCC core components, SQL Server database instances, and SIMATIC NET communication layers.
4. Device Drivers: Installed Hardware Support Packages (HSPs) and communications processor drivers.

Exporting this inventory to CSV eliminates version ambiguity during technical support investigations, vendor audits, and migration planning.

Step-by-Step Implementation Procedure

Launch the Installed Software Utility (s7aversx.exe):
a. On the Engineering Station or target PC, press the Windows key or open the Run dialog (Win+R).
b. Enter s7aversx.exe and press Enter. (Alternatively, navigate to C:\Program Files (x86)\Common Files\Siemens\s7aver\s7aversx.exe).
c. The 'Installed Software' dialog displays tabs for 'Products', 'Components', and 'Hotfixes'.
Export System Inventory to CSV:
a. In the 'Installed Software' window, select the 'Products' tab.
b. Click the 'Export' button located in the lower-right section.
c. In the file save dialog, specify a destination path and save the export as a .csv file.
d. Compress the resulting .csv file into a .zip archive for transmission to Siemens Technical Support or engineering archives.
Compile Core Environmental and Migration Metadata:
a. Record the host operating system, build version, and installed Windows Cumulative Updates (via winver and Windows Update history).
b. Document project migration history: record the originating PCS 7 version (e.g., created in V7.1 SP4, upgraded through V8.2, currently hosted in V9.0 SP2).
c. Check virtualization architecture (e.g., VMware ESXi / SIVaaS host version, virtual machine hardware compatibility level).
Extract Controller and Communications Processor Hardware Data:
a. In SIMATIC Manager, open HW Config online or connect via 'PLC -> Module Information'.
b. Record the exact MLFB order numbers and firmware versions of all CPUs (e.g., CPU 410-5H 6ES7410-5HX08-0AB0 FW V8.2.1) and communications processors (CP 443-1, CP 1623).
c. Save the CPU Diagnostic Buffer to text (PLC -> Diagnostic Buffer -> Save As...).

Verification

Open the exported CSV file in Microsoft Excel or a text editor: confirm all columns (Product, Version, Release, Order Number, Component Description) are populated.
Cross-reference the exported WinCC and CFC versions against the official Siemens Compatibility Tool to verify system-wide release harmony.
Verify that all nodes across the PCS 7 architecture (ES, OS Server A, OS Server B, OS Clients) share identical software component baselines.
Confirm that the CPU Diagnostic Buffer export captures the exact hexadecimal event IDs and timestamps corresponding to recent system anomalies.

Limitations and Operational Precautions

The utility s7aversx.exe only inspects software installed on the local Windows PC; distributed environments require running the export individually on the ES, each OS server, and representative clients. The tool does not inspect firmware revisions of field devices or remote I/O modules connected via PROFIBUS or PROFINET; those must be gathered via HW Config or SIMATIC PDM.

Engineer FAQ

Where is s7aversx.exe located if it cannot be found via Windows search?

It resides in C:\Program Files (x86)\Common Files\Siemens\s7aver\s7aversx.exe or C:\Program Files (x86)\Siemens\SIMATIC_Product_Information.

Why is exporting software inventory necessary if I already know my PCS 7 version?

Individual hotfixes (such as CFC updates or WinCC Update Collections) alter component behavior without changing the overall PCS 7 release title, making granular version tracking essential.

Can s7aversx.exe be executed silently from a script?

Yes, executing s7aversx.exe /csv /out:C:\Diagnostics\Inventory.csv generates a silent export suitable for automated maintenance routines.

What information should accompany an s7aversx export when opening a support request?

A detailed problem description, reproduction steps, error screenshots, diagnostic buffer text files, and hardware MLFB/firmware numbers.

Does running s7aversx.exe impact running control processes?

No. The tool performs read-only registry and file-system inspection and has zero impact on active STEP 7 or WinCC runtime operations.

Technical References

Related Tags

s7aversx.exe
System Diagnostics
Technical Support
Software Inventory
SIMATIC PCS 7
Hardware Compatibility

Hardware Compatibility

20 respuestas

Comprehensive PCS 7 System Diagnostics and Software Inventory Profiling via s7aversx.exe