Resolving WinCC V7.0 SQL Server 2005 Instance Not Found Error

Resolving WinCC V7.0 SQL Server 2005 Instance Not Found Installation Error

Siemens WinCC V7.0 is a SCADA/HMI platform that depends on Microsoft SQL Server 2005 and the Microsoft Message Queuing (MSMQ) Windows component. When either dependency is missing, the installation halts with instance-not-found errors that are not always self-explanatory. This reference documents the precise root cause, the prerequisite components that must be present before the installer is launched, and the field-tested recovery procedure used by automation engineers when the bundled SQL Server cannot be located by the WinCC setup routine.

1. Problem Description

During a fresh installation of Siemens WinCC V7.0 (including SP1, SP2, and SP3 updates) on a supported Windows workstation or server, the installer displays one of the following error dialogs:

• Primary error: "The instance 'WinCC' of SQL Server 2005 was not found. Setup will be terminated."
• Secondary error (after enabling MSMQ): "SQL Server installation cannot be found. Setup will be terminated."
• Tertiary error: Setup reports a missing file such as setupsql.exe or SQLSERVR.EXE in the expected redistributable path.

All three errors share the same root cause: the WinCC V7.0 setup detects that either the MSMQ Windows component is disabled or the SQL Server 2005 instance named WinCC (the instance that WinCC creates during its own setup pass) cannot be reached. Because WinCC V7.0 redistributes a licensed copy of SQL Server 2005 on its installation media, the failure almost always indicates a corrupted redistributable path, an incomplete prerequisite install, or a Windows component that has been stripped from the image.

2. Affected Products and Versions

3. Root Cause Analysis

WinCC V7.0 setup is a two-stage installer:

1. Stage 1 (SQL Server 2005 redistributable): Setup launches the embedded Microsoft SQL Server 2005 installer and provisions a named instance called WinCC. This stage requires the MSMQ Windows component to be enabled before the setup is started.
2. Stage 2 (WinCC application): Setup installs the WinCC runtime, editors, and SQL Server 2005 Service Pack 2 hotfix on top of the named instance.

When MSMQ is disabled (default on bare Windows Server 2003 R2 / Windows Server 2008 installations), the Stage 1 SQL installer fails silently or rolls back. The Stage 2 WinCC installer then attempts to attach to a SQL instance that does not exist, generating the "WinCC instance of SQL Server 2005 was not found" error.

When the second-stage installer is re-run without first repairing the SQL redistributable, the error shifts to "SQL Server installation cannot be found" because the embedded setup.exe payload expects the SQL Server 2005 bootstrap files in \\WinCC\InstData\SQLServer2005\ of the installation media.

4. Pre-Installation Prerequisites

5. Step-by-Step Resolution Procedure

5.1 Enable Microsoft Message Queuing Services

1. Open Control Panel → Add or Remove Programs.
2. Click Add/Remove Windows Components (left pane).
3. In the Windows Components Wizard, scroll to Message Queuing and place a check mark.
4. Click Details, enable Common and Triggers sub-components, then confirm with OK.
5. Insert the operating system installation media when prompted.
6. Click Next, then Finish.
7. Verify the service is running: net start MSMQ or open services.msc and confirm Message Queuing is set to Automatic and Started.

5.2 Verify SQL Server 2005 Redistributable is Intact

1. Insert the original WinCC V7.0 installation DVD (or mount the ISO).
2. Confirm the following files exist on the media:
   • InstData\SQLServer2005\Servers\setup.exe
   • InstData\SQLServer2005\Servers\setupsql.exe
   • InstData\SQLServer2005\Tools\setup.exe
3. If any file is missing or 0 bytes, copy the entire InstData folder from the original Siemens DVD image to a local folder (do not run setup from a network share).
4. Confirm the DVD is an original Siemens-licensed distribution. Third-party rebundled media often omits the SQLServer2005 payload.

5.3 Repair or Reinstall SQL Server 2005 Instance "WINCC"

1. Open Control Panel → Administrative Tools → Services.
2. Search for the service MSSQL$WINCC. If it is present but stopped, attempt to start it manually: net start MSSQL$WINCC.
3. If the service does not exist, run the WinCC V7.0 setup again. This time the installer will detect the previous partial install and offer Repair.
4. If the installer only offers Remove, use it to clean the registry entries, then re-run setup for a fresh install.

5.4 Clear Partial Installation Artifacts

If the setup fails repeatedly after Repair, manually purge remnants:

1. Stop and delete the SQL service: sc delete MSSQL$WINCC
2. Delete registry keys:
   • HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\WINCC
   • HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\WINCC
   • HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1 (only if no other SQL instance uses it)
3. Delete folders C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL and C:\Program Files\Microsoft SQL Server\MSSQL$WINCC.
4. Delete data directories under C:\Program Files\Siemens\Automation\WinCC\ only after backing up project archives.
5. Reboot the machine.
6. Run setup as Administrator.

6. Verification Steps

After the install completes, verify the system is healthy:

1. SQL Service Status: sc query MSSQL$WINCC must return STATE: 4 RUNNING.
2. SQL Connectivity: Open C:\Program Files\Microsoft SQL Server\MSSQL$WINCC\MSSQL\Binn\sqlcmd.exe and execute:

   sqlcmd -S .\WINCC -E
   SELECT @@VERSION
   GO

   Expected output: Microsoft SQL Server 2005 - 9.00.xxxx.xx (Intel X86)

3. MSMQ Status: sc query MSMQ returns STATE: 4 RUNNING.
4. WinCC Project Manager: Launch from Start Menu → Siemens Automation → WinCC → WinCC Explorer. The console opens without "Database connection failed" prompts.
5. Alarm Logging Test: Create a temporary project, open Alarm Logging, and confirm the editor opens and shows the default column headers (Date, Time, Number, Status, etc.).
6. Tag Logging Runtime Test: Open Tag Logging, insert a process tag, start runtime, and confirm the values are archived in the SQL database: sqlcmd -S .\WINCC -E -d CC_<ProjectName>_<timestamp> -Q "SELECT COUNT(*) FROM dbo.PDE#TAGs"

7. Common SQL Installation Errors and Codes

8. Troubleshooting Matrix

9. Post-Installation Hardening

1. Apply the latest WinCC V7.0 SP available (SP4 if licensed) and the matching SQL Server 2005 hotfix rollup. See Siemens Product Support Entry ID 63409384 for the SP4 release notes.
2. Move the SQL Server data files (.mdf, .ldf) off the system partition onto a dedicated data drive.
3. Configure daily backups of the WinCC project directories and the SQL databases using sqlmaint.exe or the Siemens WinCC/Dat@Monitor backup agent.
4. Set the WinCC project to Multilingual mode and pin the user interface to a single language to avoid DLL version conflicts.
5. Enable Windows Event Log forwarding to a central syslog/SCADA event collector; alarm acknowledgement is logged under WinCC → ConnectionEvents.

10. Migration Path Off WinCC V7.0

Because WinCC V7.0 is in Extended Support per the Siemens Product Lifecycle Portal, new deployments should consider migration to:

• WinCC V7.5 SP2 / V8.0 — drop-in upgrade for V7.0 with SQL Server 2014/2017 instead of SQL Server 2005.
• WinCC Professional (TIA Portal) — integrated engineering for S7-1500/ET200SP targets.
• WinCC Unified (PC) — HTML5-based UI for multi-device operation.

The MSMQ dependency is removed in WinCC V7.4 and later; the resolver stack now uses TCP-based communication, eliminating the entire root cause described in this article.

11. Field-Proven Caveats

• Disable any third-party antivirus before starting the SQL stage; McAfee, Symantec Endpoint Protection, and Trend Micro have all been documented to quarantine sqlservr.exe mid-install.
• Never run WinCC V7.0 setup from a UNC path (\server\share). The SQL bootstrap is not designed for remote install and will fail with error 1706 even if the share is reachable.
• If the system has Windows Update KB3072630 or later installed, verify the SQL Server 2005 instance starts after reboot. The 2016 TLS hardening update can break the legacy SQL handshake.
• On Windows 7 / Server 2008 R2 with UAC, the WinCC setup must be elevated even if the installing user is a member of the local Administrators group.
• Project directory paths longer than 260 characters break the SQL connection string parser. Keep C:\Program Files\Siemens\Automation\WinCC\<ProjectName> paths under 100 characters.