Migrating WinCC v7.0 SP3 to v7.5 SP1: SQL 2008 Fix & Path

Migrating WinCC v7.0 SP3 to v7.5 SP1: SQL 2008 Repair, Migration Path, and Verification

Upgrading a Siemens WinCC V7 SCADA project is not a single jump. The supported migration chain from WinCC V7.0 SP3 to WinCC V7.5 SP1 requires an intermediate stop at WinCC V7.2, and the bundled Microsoft SQL Server 2008 R2 installer is the most common failure point on legacy virtual machines. This reference documents the proven recovery sequence (SQL repair from the WinCC installation media), the recommended host platforms, the log file locations used to diagnose installer failures, and the optional branch into TIA Portal WinCC Professional.

1. Why an Intermediate Version Is Required

WinCC V7 databases are not forward-compatible across major releases. Siemens ships a project migrator inside each WinCC installation that opens a project from the previous major version, translates the underlying SQL schema, regenerates the picture tree references, and re-compiles the C-scripts and global scripts. Because the V7.5 migrator only understands the schema produced by V7.2, attempting to open a V7.0 SP3 project directly in V7.5 produces the dialog:

"The project was created with an older version of WinCC. Use the WinCC Project Migrator to convert the project."

The supported chain is therefore:

Skipping step 1 is technically possible with the V7.5 migrator, but it bypasses the schema validation and licensing tests that V7.2 performs on the V7.0 SP3 archive. Field reports show that direct V7.0 SP3 → V7.5 migrations can succeed on small projects but frequently fail on multi-server, redundant, or C-script-heavy projects. Use V7.2 as the pivot.

2. Prerequisites

Before beginning the migration, verify the following on the engineering workstation:

• OS (WinCC V7.2): Windows XP Professional SP3 (32-bit), Windows 7 SP1 (32/64-bit), Windows Server 2003 R2 SP2, Windows Server 2008 R2 SP1.
• OS (WinCC V7.5 SP1): Windows 7 SP1 (32/64-bit), Windows Server 2008 R2 SP1 (64-bit), Windows 10 (with KB updates per release notes).
• RAM: Minimum 4 GB, recommended 8 GB for projects > 500 tags.
• Disk: 10 GB free for installation + 2× project size for backup/archive.
• Hypervisor (lab use): VMware Workstation/ESXi or Hyper-V provide the best compatibility for legacy OS images. VirtualBox works for WinCC V7.0 SP3 / V7.2 on Windows XP SP3 but has known issues with SQL Server 2008 R2 installer hooks — see Section 6.
• SQL Server pre-check: Confirm no existing SQL Server instance (any version) is present before running the WinCC setup. Conflicting instances are the leading root cause of the bundled SQL 2008 R2 install failure.
• Administrative rights: Local Administrator account is required for both setup and SQL repair.
• Source media: WinCC V7.2 DVD/ISO and WinCC V7.5 SP1 DVD/ISO (both 64-bit recommended).

3. Root Cause of the SQL Server 2008 R2 Installation Failure

The error reported during the V7.2 setup — typically a generic "SQL Server 2008 R2 setup failed" message with an MSI exit code in the 1603 / 233 / 2229 range — is almost always caused by one of three conditions on a Windows XP SP3 / VirtualBox image:

1. Remnant SQL instance: A previous aborted install left orphaned registry keys under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server and folders under %ProgramFiles%\Microsoft SQL Server.
2. Missing prerequisites: Windows Installer 4.5, .NET Framework 3.5 SP1, or Windows PowerShell 1.0 are not installed on the XP SP3 base image.
3. Pending file rename / reboot: A prior installer requested a reboot that was never performed; SQL setup refuses to continue with the flag set.

The repair path is to run the bundled SQL repair from the setup media instead of uninstalling/reinstalling manually.

4. SQL Server 2008 R2 Repair Procedure

The bundled installer ships a repair utility on the WinCC V7.2 media. Execute the following steps from an elevated (Run as Administrator) command prompt:

1. Open the installation folder:

   X:\WinCC_V7.2_Siemens\InstData\SQL\SQL2008R2STD\SQLFULL_ENU

   where X is your DVD drive or mounted ISO.
2. Locate setup.exe inside the SQLFULL_ENU directory.
3. Launch the SQL repair tool:

   setup.exe /ACTION=REPAIR /INSTANCENAME=WINCC /QS

   The /INSTANCENAME=WINCC argument matches the default instance name created by WinCC setup. If a custom instance was used during a prior install, substitute that name. The /QS flag runs quietly and only displays errors.
4. Wait for completion. The repair can take 5–15 minutes depending on disk speed.
5. Reboot the system regardless of the prompt (the pending file rename flag must be cleared).
6. Re-launch the WinCC V7.2 setup from setup.exe at the root of the media. The installer will detect the existing SQL instance and continue with the WinCC components.

5. Locating SQL Setup Logs for Diagnosis

When the installer dialog hides the underlying failure, the SQL Server setup writes detailed logs to the current user's temp folder. This is the canonical location for diagnosing V7.2 SQL failures:

%TEMP%\sqlsetup*.log
%TEMP%\sqlsetup*_core.log
%TEMP%\sqlsetup*_engine.log
%TEMP%\sqlsetup*_rs.log
%TEMP%\sqlsetup*_fulltext.log

Open the most recently modified *_core.log first; it contains the high-level phase results. Drill into *_engine.log for database engine failures. Useful search terms:

After WinCC is installed, the runtime SQL logs are written to:

C:\Program Files\Microsoft SQL Server\MSSQL10_50.WINCC\MSSQL\Log\ERRORLOG
%ProgramData%\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2008 R2\

6. VirtualBox, VMware, and Hyper-V Considerations

The original report uses Oracle VM VirtualBox on Windows XP Professional SP3. WinCC V7.0 SP3 / V7.2 will install on this configuration, but VirtualBox's emulated ACPI and storage controllers expose two recurring SQL setup problems:

• Pending reboot detection: VirtualBox guest additions sometimes leave PendingFileRenameOperations populated. SQL 2008 R2 interprets this as a fatal state and exits silently.
• Disk controller emulation: The default SATA AHCI emulation triggers an SQL Server Setup has encountered the following error: Value cannot be Null message when the MSI attempts to enumerate disks.

The recommended remediation is to switch the virtual disk controller to LSI Logic SAS or IDE in the VirtualBox VM settings. If SQL setup still fails after two attempts, migrate the VM to VMware Workstation or Hyper-V. Both hypervisors are officially supported by the WinCC V7.2 system documentation for virtualization scenarios.

For a fresh lab environment, build Windows 7 SP1 x64 directly under VMware or Hyper-V. Windows 7 avoids the XP-specific .NET / PowerShell prerequisite chain and is the longest-supported host for both V7.2 and V7.5 SP1.

7. Project Migration Procedure: V7.0 SP3 → V7.2 → V7.5 SP1

Once the SQL repair above completes and WinCC V7.2 is installed, execute the project migration:

7.1 Migrate V7.0 SP3 → V7.2

1. On the V7.0 SP3 source system, archive the project with WinCC Project Duplicator to a network share or external drive.
2. Copy the *.zip archive to the V7.2 workstation.
3. Open WinCC Explorer on the V7.2 workstation. The first launch prompts for the project migration of any older archive.
4. Select File → Open → Retrieve, navigate to the archive, and confirm the migration dialog.
5. The migrator updates the SQL schema, regenerates picture references, and recompiles C-scripts. Compile the project (right-click → Rebuild all) to confirm.
6. Open the migrated project in runtime for at least 10 minutes to verify tags, alarms, and archives populate correctly.

7.2 Migrate V7.2 → V7.5 SP1

1. On the V7.2 system, archive the now-migrated project with the Duplicator again. This is mandatory — the V7.5 migrator reads a fresh archive, not a live project.
2. Transfer the archive to the V7.5 SP1 workstation.
3. Open WinCC Explorer on the V7.5 SP1 workstation. The Project Migrator dialog appears automatically when an older archive is selected.
4. Confirm migration. The V7.5 migrator performs a schema upgrade to SQL Server 2012 format and re-registers the OPC DA / OPC A&E servers.
5. Recompile all C-scripts and VBS actions. V7.5 enforces stricter script syntax; legacy printf and uninitialized COM pointers may need updates.
6. Run the project for a controlled burn-in (1 hour minimum) before decommissioning the V7.2 host.

8. Verification Checklist

Run the following checks on the V7.5 SP1 target before signing off the migration:

9. Troubleshooting Matrix

10. Optional Path: Migrate to TIA Portal WinCC Professional

If the long-term target is TIA Portal rather than WinCC V7.5 SP1, Siemens provides a separate migration entry point. Per Siemens support entry ID 109963167 — Migration of WinCC V7 projects to TIA Portal, the supported source range for WinCC Professional migration is:

• Minimum source: WinCC V7.0 SP1
• Maximum source: WinCC V7.5 (without Service Pack)

V7.5 SP1 archives must first be downgraded / re-archived with V7.5 base before the TIA migrator can read them. The TIA migration uses the TIA Portal Project Migration tool, not the WinCC V7-to-V7 migrator. Note the differences:

11. Field-Proven Caveats

• Always archive with Duplicator, never copy the project folder. Copying \<ProjectName>\ directly leaves behind open file handles and inconsistent SQL transaction logs.
• Do not install WinCC V7.2 and V7.5 SP1 on the same host. Both share the WINCC SQL instance name; side-by-side installs corrupt the databases. Use separate physical or virtual machines.
• Document the V7.0 SP3 license before archiving. V7.5 SP1 requires a new license; the V7.x RT/RC keys are not portable.
• Back up the archive twice. One copy for migration, one offline copy in case the V7.5 migrator fails partway and corrupts the original.
• Check the C-script locale. German-locale strings inside C-scripts sometimes fail under English-locale SQL Server collations. Set the OS locale of the V7.5 host to match the V7.0 SP3 source.

12. Quick-Reference Command Summary