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

How to Resolve False Missing .NET Framework 4.5 Error During Process Historian Installation

How to Resolve False Missing .NET Framework 4.5 Error During Process Historian Installation

When installing SIMATIC Process Historian on Windows Server 2016 or Windows Server 2019, setup halts with an error dialog stating that 'Microsoft .NET Framework 4.5 must be installed', even when a newer .NET version (such as .NET 4.7 or 4.8) is present on the computer. This occurs because the Siemens installer queries specific operating system component registrations and dependent sub-features—specifically .NET Framework 3.5 and .NET 4.x Advanced Services (such as WCF HTTP Activation and TCP Port Sharing)—that are not installed by standalone Microsoft .NET web packages. To resolve this blocker, mount the Windows Server installation media and activate the required .NET features using the Deployment Image Servicing and Management (DISM) tool targeting the side-by-side (sources\sxs) repository.

Table of Contents

Root Cause: Windows Server Feature Architecture vs. Web Installers

In server operating systems such as Windows Server 2016 and Windows Server 2019, Microsoft manages .NET assemblies as integrated operating system features rather than standalone application packages:
* Legacy Registry Query: The SIMATIC Process Historian pre-requisite checker inspects the Windows Registry at:
text HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
It checks both the Release DWORD and the presence of underlying Windows Communication Foundation (WCF) feature keys.
* Component Absence: While modern Windows Servers include .NET 4.7/4.8 in the base image, critical runtime components required by Process Historian's database indexing services (such as HTTP Activation, Message Queuing Activation, and .NET Framework 3.5 backward-compatibility runtimes) are disabled by default.
* The False Missing Prompt: When Process Historian's installer detects that WCF services are uninitialized, it generates a generic message indicating that .NET Framework 4.5 is missing, misleading engineers into downloading web runtimes that refuse to install.

Why Standalone .NET 4.5 Installers Fail on Modern Windows Servers

Downloading dotNetFx45_Full_setup.exe from Microsoft and executing it on Windows Server 2016 or 2019 produces a secondary Windows error:
Microsoft .NET Framework 4.5 is already a part of this operating system. You do not need to install the .NET Framework 4.5 redistributable.

This creates a deadlock where the operating system refuses the standalone installer while the Siemens installer refuses to proceed without feature registration. The only supported resolution is enabling the native Windows Server components directly from the OS media payload.

Method 1: Enabling .NET Framework 3.5 and 4.x via DISM (Recommended)

Using the Windows Command Line tool DISM is the fastest and most reliable method to enable all dependent components without requiring an active internet connection:

  1. Insert the Windows Server installation DVD or mount the official Windows Server ISO (for example, to drive letter D:).
  2. Right-click the Windows Start menu and select Windows PowerShell (Admin) or Command Prompt (Admin).
  3. Execute the following command to install .NET Framework 3.5 using the local side-by-side payload:
    cmd DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs
  4. Execute the following command to enable all .NET Framework 4.x Advanced Services required by Process Historian:
    cmd DISM /Online /Enable-Feature /FeatureName:NetFx4Extended-AS /All DISM /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation45 /All DISM /Online /Enable-Feature /FeatureName:WCF-TCP-PortSharing45 /All
  5. Wait for the DISM console to confirm: The operation completed successfully. 100.0%.
  6. Reboot the Windows Server.
  7. Relaunch the Process Historian installation setup.

Method 2: Configuring Features via Windows Server Manager

If you prefer using the graphical administration interface:

  1. Open Server Manager and select Manage > Add Roles and Features.
  2. Click Next until you reach the Features tab.
  3. Check the box for .NET Framework 3.5 Features (ensure both .NET Framework 3.5 and HTTP Activation are checked).
  4. Expand .NET Framework 4.x Features > WCF Services:
    - Check HTTP Activation.
    - Check TCP Port Sharing.
  5. On the confirmation screen, click the link at the bottom: Specify an alternate source path.
  6. Enter the path to the installation media payload: D:\sources\sxs.
  7. Click Install. Once installation completes, restart the server and re-run Process Historian setup.

Verification

To verify that the .NET prerequisite is satisfied and that Process Historian is ready for installation:

  1. In PowerShell (Admin), query the feature status:
    powershell Get-WindowsFeature Net-Framework*
  2. Confirm that Net-Framework-Core (.NET 3.5) and Net-Framework-45-Features report an Install State of Installed.
  3. Launch the SIMATIC Process Historian Setup.exe.
  4. Observe the system prerequisite check screen: verify that the .NET Framework line displays a green checkmark and that the Next button is active.

Limitations and Operational Precautions

  • Media Version Matching: The sources\sxs directory must come from the exact Windows Server build installed on the machine (e.g., Windows Server 2019 Build 17763 requires a matching 2019 Build 17763 ISO). Using a Windows Server 2016 ISO on a 2019 OS results in DISM error 0x800f081f (source files could not be found).
  • Windows Update Conflicts: In enterprise environments where WSUS (Windows Server Update Services) is deployed, local DISM commands may fail if Group Policy forces feature acquisition from WSUS. The /LimitAccess switch in the DISM command prevents Windows from querying WSUS and forces use of the local sxs folder.
  • Server Role Dedication: Siemens Process Historian requires a dedicated physical or virtual server. Do not install Domain Controller (AD DS), DNS, or Office suites on the Process Historian host.

Engineer FAQ

Why does Process Historian require .NET 3.5 if it is asking for .NET 4.5?
Certain legacy Microsoft SQL Server installer subroutines and Siemens diagnostic collectors bundled inside Process Historian rely on .NET 2.0/3.5 runtime libraries.

Can I download the sxs folder from the internet instead of mounting the ISO?
No. The sxs folder contains digitally signed, operating-system-specific binary packages that must strictly match your installed Windows Server build number.

Does installing .NET Framework 3.5 impact other installed PCS 7 components?
No. Modern Windows operating systems run .NET 3.5 and .NET 4.x side-by-side in completely isolated runtime environments without version conflicts.

Technical References

  • Siemens Industry Online Support Entry ID 109742323: SIMATIC Process Historian Administration and Installation Manual
  • SIMATIC Process Historian Manual (Document No. A5E03588264)
  • Siemens Industry Online Support Entry ID 109809264: Installation Requirements for SIMATIC Process Historian

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=process-historian
  • https://industrialautomation.net/search?query=windows-server
  • https://industrialautomation.net/search?query=net-framework
  • https://industrialautomation.net/search?query=simatic-pcs7
20 respuestas