Troubleshooting TIA Portal V15.1 Installation Failure on Windows 7 Pro SP1
The TIA Portal V15.1 installer (TIA_Portal_STEP_7_Pro_WINCC_Adv_V15_1.exe) is a complex multi-package deployment that bundles STEP 7 Professional, WinCC Advanced, Startdrive, S7-PLCSIM, the Safety option, the WinCC Migration Tool, and the Automation License Manager V6.0 SP1 (ALM) into a single transaction. When the host system is Windows 7 Professional SP1 64-bit with co-installed legacy engineering software (TIA V13, V14, V15, WinCC Flexible 2008, Starter 5.1), the installer frequently aborts during the first package without rolling back cleanly. This article documents the exact failure modes — most notably SQL Server 2014 Express instance collisions and Automation License Manager post-reboot failure — and the field-proven recovery paths.
1. Documented Failure Symptoms
The reported installation behavior is consistent across multiple field reports. The error progression is as follows:
- User launches
TIA_Portal_STEP_7_Pro_WINCC_Adv_V15_1.exeas Administrator on Windows 7 Pro SP1 64-bit with 32 GB RAM, SSD, Intel Core i7 (2.5 GHz-class). - The installer unpacks the first package, performs prerequisites checks, and aborts with a Windows Installer rollback. The
summary.login%TEMP%\Siemens\SIA_LOG\reports an SQL Express 2014 dependency failure. - Stopping Microsoft SQL Server (MSSQL) services tied to WinCC, S7, or TIA does not allow the installer to proceed.
- Re-running with the option to install only TIA Portal (deselecting Migrate Project from WinCC Flexible 2008) succeeds for the portal core, but the post-install Automation License Manager package then fails during reboot-triggered configuration.
- Installing the additional TIA components (S7-PLCSIM V15.1, Safety Advanced V15.1, Startdrive V15.1) subsequently updates the ALM to 6.0 SP1, completing the deployment.
- The WinCC Flexible migration option remains uninstalled.
2. TIA Portal V15.1 System Requirements
Verify that the engineering workstation meets the supported baseline before troubleshooting. Per the official SIMATIC TIA Portal V15.1 System Requirements entry in the Siemens Industry Online Support (SIOS) knowledge base:
| Parameter | Required Value (Windows 7) | Notes |
|---|---|---|
| Operating system | Windows 7 Professional SP1 / Enterprise SP1 / Ultimate SP1, 64-bit | Home editions are not supported |
| Processor | Intel Core i5-6440EQ or equivalent | i7-class recommended for WinCC Professional |
| RAM | 8 GB minimum, 16 GB recommended | 32 GB is the practical upper bound for V15.1 |
| Free disk space | ≥ 35 GB for the full bundle (STEP 7 + WinCC Adv + PLCSIM + Startdrive + Safety) | SSD strongly recommended |
| Display | 1920 × 1080 minimum | 15.6" Full HD or larger |
| .NET Framework | 4.7.2 (or later 4.x installed by TIA setup) | Setup is permitted to install/update 4.7.2 |
| SQL Server | SQL Server 2014 SP2 Express (installed by TIA setup) | Co-installed instances must be enumerated |
| Automation License Manager | V6.0 SP1 (bundled with V15.1) | Replaces V5.x from prior TIA versions |
| Web Server / IIS | Disabled or configured for WinCC WebNavigator | Required only for WinCC Web UX |
3. Root Cause Analysis: SQL Server 2014 Express Instance Collision
TIA Portal V15.1 requires a dedicated SQL Server 2014 Express instance named SQLEXPRESS (default) or a Siemens-defined named instance. The installation routine calls SQL Server 2014 Setup in install-or-upgrade mode. When a pre-existing SQLEXPRESS instance is already bound to WinCC Flexible 2008 (or any other engineering product that uses SQL Server 2014 for archive logging), the Siemens setup cannot upgrade the instance atomically and aborts the transaction.
The collision is detected by reading:
- The registry key
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL - The Windows service
MSSQL$SQLEXPRESSand any named SQL instances - The
summary.logline:Product: SIMATIC WinCC Engineering — Error 1316. Setup cannot continue because the SQL Server instance 'SQLEXPRESS' is in use by another application.
Common collateral applications holding the SQL Express 2014 instance:
- SIMATIC WinCC Flexible 2008 (RT/ES archive database)
- SIMATIC ProTool/Pro RT
- Third-party MES or SCADA packages installed by the plant
- Older TIA Portal versions (V13, V14, V15) using
SQLEXPRESSas a shared instance
4. Root Cause Analysis: Automation License Manager 6.0 SP1 Post-Reboot Failure
The Automation License Manager (ALM) V6.0 SP1 is installed by the TIA Portal setup as a chained MSI that performs a pending-file-rename and triggers a reboot. After the workstation reboots, the ALM service almserver64 must register its DCOM endpoints, write the C:\Program Files (x86)\Siemens\AutomationLicenseManager\almserver.ini file, and bind to TCP port 4410 (RPC) plus 4411 (almp). The post-reboot task fails when:
- The previous ALM service (
almserverfrom V5.x) still holds a handle onC:\Program Files (x86)\Siemens\AutomationLicenseManager. - The DCOM launch permissions on the
almserverapplication GUID are corrupted from a prior interrupted setup. - The Visual C++ 2015–2019 redistributable (x86) required by ALM 6.0 SP1 was not staged in
C:\ProgramData\Package Cachedue to a prior rollback.
The failure leaves the file set under %ProgramFiles(x86)%\Siemens\AutomationLicenseManager partially copied, the service not registered, and the TIA Portal returns license errors 000001 and 000010 on first start.
5. Pre-Installation Diagnostics
Before re-running the TIA Portal V15.1 installer, capture the host state so the rollback path is auditable. Run the following from an elevated Command Prompt:
REM 1. Enumerate installed SQL Server instances and versions
reg query "HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL" /s
REM 2. List all Siemens-related services
sc query | findstr /I "siemens\|sql\|alm\|s7\|wincc"
REM 3. Confirm ALM service version
reg query "HKLM\SOFTWARE\Siemens\AutomationLicenseManager" /v Version
REM 4. Free space on system drive
wmic logicaldisk where "DeviceID='C:'" get FreeSpace,Size
REM 5. Pending file rename operations (the ALM reboot trap)
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations
Additionally, inspect the Siemens installation log directory:
dir /a "%LOCALAPPDATA%\Temp\Siemens\SIA_LOG"
type "%LOCALAPPDATA%\Temp\Siemens\SIA_LOG\summary.log"
The summary.log file lists every MSI invoked, the result code, and the user deferred actions. Capture it before any repair attempt so the failure is reproducible.
6. Resolution Path A — Resolve the SQL Express 2014 Conflict
Pick exactly one of the three sub-paths below. Do not chain them without a reboot in between.
6.1 Sub-path A1 — Stop & Re-Use the Existing Instance (Preferred)
- Stop and disable the SQL service:
sc stop MSSQL$SQLEXPRESS && sc config MSSQL$SQLEXPRESS start= demand - Set the SQL service logon to
NT AUTHORITY\NETWORK SERVICEviaSQL Server Configuration Manager. - Grant the user account
NT AUTHORITY\SYSTEMandNT SERVICE\MSSQL$SQLEXPRESSsysadmin rights inSSMS. - Re-run
TIA_Portal_STEP_7_Pro_WINCC_Adv_V15_1.exeas Administrator. The setup will detect the existing instance and run the upgrade scriptSetup\SQL\S7_SETUP.SQL.
6.2 Sub-path A2 — Uninstall the Conflicting SQL Express 2014
- Open Programs and Features. Identify which product installed the
SQLEXPRESSinstance (usually WinCC Flexible 2008 or TIA V13). - From the host's Programs and Features, choose Uninstall/Change → Remove the SQL Server 2014 Express instance. Do not remove the parent application yet.
- Reboot. Verify the instance is gone:
reg delete "HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\SQLEXPRESS"(read-only check). - Run the TIA Portal V15.1 setup. The setup installs a fresh
SQLEXPRESSinstance and binds it.
6.3 Sub-path A3 — Open a Siemens Support Request
If the SQLEXPRESS instance is shared with plant software you do not own (e.g., a third-party MES or a customer-deployed archive tool), do not remove it. Open a Support Request via the Siemens Industry Online Support portal and request the V15.1 Setup Advanced package, which lets you point the TIA installer at a user-defined SQL instance. Attach the summary.log and a screenshot of the registry tree above.
7. Resolution Path B — Recover the Automation License Manager
When the TIA Portal setup completes the main package but the ALM 6.0 SP1 package is still listed in Programs and Features with status (incomplete), execute the following repair sequence.
- Open an elevated cmd.exe. Clear any pending file rename operations:
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations /f
then reboot. - After reboot, stop the legacy service if present:
sc stop "Automation License Manager" && sc delete "Automation License Manager" - Manually remove the old installation directory:
rd /s /q "%ProgramFiles(x86)%\Siemens\AutomationLicenseManager" - Mount the original TIA Portal V15.1 ISO or extract the EXE to a writable folder:
TIA_Portal_STEP_7_Pro_WINCC_Adv_V15_1.exe /extract:"D:\TiaV15_1_Extracted" - Browse to
D:\TiaV15_1_Extracted\Support\LicenseManager\ALM_V60_SP1\Disk1and runsetup.exeas Administrator. The ALM 6.0 SP1 installer runs standalone, registersalmserver64, and writes the registry keys for DCOM access. - Verify the service:
sc query "almserver64"→ stateRUNNING. Verify the TCP port:netstat -ano | findstr :4410→ listening on PID ofalmserver64.exe.
Once ALM 6.0 SP1 is installed standalone, the TIA Portal V15.1 setup will detect the existing ALM and skip its own copy. This is the most reliable path on Windows 7 Pro SP1.
8. Resolution Path C — Component-by-Component Installation
If the chained setup continues to fail after A + B, install the TIA Portal V15.1 family in the explicit order below. This is the path that ultimately resolved the field case described in the source report.
- Install the TIA Portal main package without the Migrate Project from WinCC Flexible 2008 option, and without the Startdrive, PLCSIM, and Safety options.
- Install S7-PLCSIM V15.1 (
S7_PLCSIM_V15_1.exe). - Install STEP 7 Safety Advanced V15.1 (
STEP7_Safety_Advanced_V15_1.exe). - Install Startdrive V15.1 (
Startdrive_V15_1.exe). - Install WinCC Advanced V15.1 update if not already present in the main package.
- Reinstall or repair the Automation License Manager per Path B.
Each of the three optional components (PLCSIM, Safety, Startdrive) carries a copy of the ALM 6.0 SP1 MSI. When the first two of them are installed, the ALM is upgraded in place, and the third install cleanly completes the ALM state. This is why the field case reached a working state only after all three optional components were installed.
9. The WinCC Flexible 2008 Migration Option — Known Limitation
The TIA Portal V15.1 Migrate Project from WinCC Flexible 2008 sub-package is the last component to install. It uses the same SQLEXPRESS instance as the TIA Portal itself and the WinCC Flexible 2008 RT. On a host where the original WinCC Flexible 2008 installation is still present (i.e., Programs and Features still lists SIMATIC WinCC flexible 2008), the migration tool installation will refuse to proceed because it cannot install a second, distinct SQLEXPRESS instance named WINCCFLEX.
Field options when the migration tool cannot be installed:
- Open WinCC Flexible 2008 SP5, use Project → Migrate Project → To TIA Portal to convert each project to TIA Portal V15.1 directly, without using the migration option. The conversion is performed in-process and does not require the setup option.
- Install TIA Portal V15.1 on a clean Windows 10 / Windows 7 image without WinCC Flexible 2008 and use the option there to host the migration tool.
- Defer the migration. TIA Portal V15.1 can open and edit projects migrated by a separate V15.1 installation that does have the migration tool.
The TIA Portal V15.1 Readme, available from the TIA Portal V15.1 Delivery Release entry, documents the WinCC Flexible migration tool as not mandatory for runtime; it is required only for batch migration of legacy HMI projects.
10. Side-by-Side Installation: TIA V13 / V14 / V15 / V15.1
Siemens supports parallel installation of TIA Portal versions starting from V14 onward, but the following rules apply:
| Combination | Supported? | Notes |
|---|---|---|
| V13 + V15.1 | Yes (with V14/V15 in between) | V13 ALM 5.3 remains the primary ALM; V15.1 ALM 6.0 SP1 runs as a secondary service |
| V14 SP1 + V15.1 | Yes | ALM 6.0 SP1 takes precedence for license hosting |
| V15 + V15.1 | Yes | Both share SQLEXPRESS instance; install order = newest last |
| V13 + V14 + V15 + V15.1 | Yes (validated, with limitations) | Each must use its own project directory; do not share Siemens\Automation working folder across versions |
| V15.1 + Startdrive V15 | No | Startdrive V15 conflicts with Startdrive V15.1; uninstall V15 first |
When three or more TIA versions are co-resident, the highest ALM version should be the last one installed. The ALM 5.3 service from TIA V13 must not be downgraded by the V15.1 setup; the V15.1 setup will detect and skip the ALM upgrade if ALM 6.0.x is already present. The reverse — V15.1 installed first, then V13 — will corrupt the ALM 6.0 SP1 service registration. Always install in ascending version order.
11. Post-Installation Verification
After each repair or component install, run the verification matrix below. A green row is required before opening the TIA Portal:
| Check | Command / Action | Expected |
|---|---|---|
| ALM service running | sc query almserver64 |
STATE: 4 RUNNING |
| ALM RPC port | netstat -ano | findstr :4410 |
LISTENING on almserver64 PID |
| SQL Express instance | reg query "HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL" |
SQLEXPRESS present, version 12.0.5000+ (SQL 2014 SP2) |
| TIA Portal start | Launch Totally Integrated Automation Portal V15.1
|
Splash → project view, no license errors |
| License diagnostics | Open ALM V6.0 SP1 → Help → About | Version 6.0.0.20180101+ |
| WinCC Advanced start | Open TIA Portal → Add new device → HMI → WinCC Advanced | Device catalog populates; no SQL initialization failed |
| PLCSIM start | Start → S7-PLCSIM V15.1 | PLCSIM window opens; download a test LAD/FBD block to a simulated S7-1500 |
| Startdrive start | Open TIA Portal → Devices & Networks → Add SINAMICS | G120, S120, S210 catalog populated |
12. Field-Proven Commissioning Sequence (Windows 7 Pro SP1, 64-bit)
For a green-field Windows 7 Pro SP1 64-bit engineering workstation that will host TIA Portal V13 / V14 / V15 / V15.1 plus WinCC Flexible 2008, use the following sequence to avoid all known V15.1 installation failures:
- Install Windows 7 Pro SP1 with all critical and recommended updates. Confirm
winvershows Service Pack 1. - Install Microsoft .NET Framework 4.7.2 manually before any Siemens product. Reboot.
- Install Microsoft SQL Server 2014 Express SP2 manually on a
SQLEXPRESSnamed instance bound toNT AUTHORITY\NETWORK SERVICE. Reboot. - Install SIMATIC WinCC Flexible 2008 SP5. Verify its RT/ES functions.
- Install SIMATIC TIA Portal V13 SP2 (optional). Reboot.
- Install SIMATIC TIA Portal V14 SP1. Reboot.
- Install SIMATIC TIA Portal V15. Reboot.
- Install SIMATIC TIA Portal V15.1, with all options disabled in the first pass. Reboot.
- Run S7-PLCSIM V15.1 setup. Reboot.
- Run STEP 7 Safety Advanced V15.1 setup. Reboot.
- Run Startdrive V15.1 setup. Reboot.
- Run WinCC Advanced V15.1 update (if not in main package). Reboot.
- Run the full TIA Portal V15.1 setup a second time with the Migrate Project from WinCC Flexible 2008 option enabled. If the option is still refused, accept the limitation and use the in-process migration in WinCC Flexible 2008 SP5.
- Capture the final
summary.logfor the engineering record. Verify the matrix in Section 11.
msiexec /regserver from an elevated prompt is the standard fix if the service is corrupted.13. Frequently Asked Questions
Why does TIA Portal V15.1 fail on Windows 7 Pro SP1 when SQL Express 2014 is already installed?
TIA Portal V15.1 requires a dedicated SQL Server 2014 SP2 Express instance and will not silently re-use one bound to WinCC Flexible 2008 or a prior TIA Portal version. The setup aborts with error 1316 in the summary.log. The supported remedies are: stop the existing SQL service, grant the new setup upgrade rights, or remove the conflicting instance (see Resolution Path A).
Can the Automation License Manager V6.0 SP1 be installed separately from the TIA Portal V15.1 setup?
Yes. Extract the EXE with TIA_Portal_STEP_7_Pro_WINCC_Adv_V15_1.exe /extract:"C:\TiaV15_1", then run C:\TiaV15_1\Support\LicenseManager\ALM_V60_SP1\Disk1\setup.exe as Administrator. The ALM 6.0 SP1 installs as a standalone product, registers the almserver64 service on TCP 4410, and is then recognized by the TIA Portal V15.1 setup as a present prerequisite.
Is the WinCC Flexible 2008 project migration option required to use TIA Portal V15.1?
No. The migration tool is only required to batch-convert WinCC Flexible 2008 projects to TIA Portal. Projects can be migrated one at a time directly from WinCC Flexible 2008 SP5 (Project → Migrate Project → To TIA Portal) without the setup option being installed. The TIA Portal V15.1 Readme, available from the official Siemens support entry 109760750, lists this option as optional.
How can multiple TIA Portal versions (V13, V14, V15, V15.1) coexist on Windows 7?
Siemens supports side-by-side installation from V14 onward, but the install order must be ascending (oldest first, V15.1 last). The highest-version Automation License Manager must be the last ALM installed. The SQLEXPRESS instance is shared across versions and upgraded in place by each setup pass. Each TIA Portal version uses its own project directory; do not share the %USERPROFILE%\Documents\Automation working folder across versions.
What is the minimum disk space for a full TIA Portal V15.1 installation including Startdrive, PLCSIM, and Safety?
Siemens specifies ≥ 35 GB of free disk space for the full bundle. With WinCC Flexible 2008 RT/ES, the Starter V5.1 commissioning tool, and the SQL Server 2014 Express instance, the practical floor on a Windows 7 Pro SP1 64-bit engineering workstation is 60–80 GB. SSDs are required for the WinCC Professional and PLCSIM co-simulation workflows.