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

Why WinCC V6 Requires Siemens SQL Server 2000 SP3a and Where to Obtain It

Why WinCC V6 Requires Siemens SQL Server 2000 SP3a and Where to Obtain It

Installing SIMATIC WinCC V6.0 requires a specialized Siemens OEM distribution of Microsoft SQL Server 2000 Service Pack 3a (or SP4 for WinCC V6.0 SP4) containing custom setup scripts, pre-configured database instances, and specific collation settings. Attempting to use a standard retail Microsoft SQL Server 2000 CD fails because the WinCC prerequisite installer explicitly checks for Siemens configuration files and specific registry signatures. To resolve missing installation media, obtain the official Siemens companion disc titled 'Microsoft SQL Server 2000 for WinCC V6.0' from your original software delivery package or request a licensed replacement ISO from Siemens Customer Support.

Table of Contents

The Role of SQL Server 2000 in WinCC V6 Architecture

Starting with SIMATIC WinCC V6.0, Siemens transitioned its underlying SCADA database engine from Sybase SQL Anywhere to Microsoft SQL Server 2000. In WinCC V6.0, SQL Server is not merely an optional data warehouse; it is the core repository for all SCADA functions:
* Configuration Data (CS): Graphics Designer objects, tag management, alarm logging definitions, and user permissions.
* Runtime Data (RT): Process value archives (Tag Logging Fast/Slow), alarm status lists, and audit trails.

WinCC automates database creation, segment rotation, and backup management by issuing direct API commands to the local SQL Server database instance named WinCC.

Why Commercial Retail SQL Server Media Is Incompatible

When WinCC V6 setup halts with the prompt Microsoft SQL Server 2000 Service Pack 3a must be installed from CD, engineers often attempt to insert standard retail or MSDN Microsoft SQL Server 2000 discs. This consistently fails due to four strict OEM customizations:

  1. Custom Siemens Setup Wrapper: The Siemens distribution contains specialized batch routines and answer files (SqlRun01.bat, Setup.iss) tailored for unattended, hardened deployment.
  2. Instance Naming: WinCC requires an instance named specifically WINCC. Standard SQL setups defaulting to the default instance (MSSQLSERVER) are ignored by the WinCC setup launcher.
  3. Collation and Sorting Order: WinCC demands a precise collation: Latin1_General_CI_AS (Case-Insensitive, Accent-Sensitive) with binary code page 1252. If an incorrect collation is selected during manual installation, WinCC runtime fails to open projects.
  4. License Integration: The Siemens OEM package incorporates a client access license (CAL) tied directly to SIMATIC WinCC runtime licensing.

Legitimate Methods to Obtain the Siemens SQL 2000 Package

Because Microsoft retired SQL Server 2000 over a decade ago, it is not available on public Microsoft download portals. To obtain the verified installation media:

  • Original Software Shipment Box: Locate the physical CD envelope labeled SIMATIC HMI WinCC V6.0 - Microsoft SQL Server 2000 SP3a (Siemens Part Number 6AV6392-1...).
  • Official Siemens Support Ticket: Contact Siemens Industry Online Support (SIOS) with your valid WinCC V6.0 license certificate or dongle number. Siemens Technical Support provides authenticated download access to legacy software ISO images for registered license holders.
  • WinCC V6 Service Pack DVDs: If migrating to WinCC V6.0 SP3 or SP4, the comprehensive service pack DVD media includes the required SQL Server 2000 SP3a/SP4 installation files in the InstData\SQL2000 directory.

Installation and Instance Configuration Workflow

To install Microsoft SQL Server 2000 correctly for WinCC V6:

  1. Log into Windows 2000 Professional / Windows XP Professional with an account holding local Administrator privileges.
  2. Insert the Siemens SQL Server 2000 CD or mount the official ISO image.
  3. Run Setup.exe from the root of the Siemens SQL CD. Do not run the generic SQL setup inside nested subdirectories.
  4. When prompted, select Install Database Server (WinCC Instance).
  5. Accept the default configuration parameters. The Siemens installer automatically configures:
    - Named instance: WINCC
    - Authentication mode: Mixed Mode (Windows Authentication and SQL Server Authentication)
    - Network libraries: Named Pipes and TCP/IP (Port 1433)
  6. Upon completion, install SQL Server 2000 Service Pack 3a (or SP4) by launching the service pack updater provided on the disc.
  7. Reboot the computer. Re-launch the WinCC V6.0 setup. The prerequisite checker will detect the active WINCC SQL instance and proceed with installation.

Verification

To verify that Microsoft SQL Server 2000 is installed properly for WinCC:

  1. Open the Windows Services management console (services.msc).
  2. Verify that the following services are installed and running with startup type Automatic:
    - MSSQL$WINCC (SQL Server - WINCC instance)
    - SQLAgent$WINCC (SQL Server Agent - WINCC instance)
  3. Open a command prompt and execute:
    cmd osql -S .\WINCC -E -Q "SELECT @@VERSION"
  4. Confirm that the query returns Microsoft SQL Server 2000 - 8.00.760 (for SP3a) or 8.00.2039 (for SP4) and that the instance name confirms WINCC.

Limitations and Operational Precautions

  • Operating System Boundaries: WinCC V6.0 and SQL Server 2000 are supported strictly on Windows 2000, Windows XP, and Windows Server 2003. They cannot run on Windows 7, Windows 10, or Windows Server 2016+.
  • Security Exposure: SQL Server 2000 contains known security vulnerabilities (such as the SQL Slammer worm). Industrial systems running WinCC V6 must be completely isolated from enterprise IT networks and the internet.
  • Do Not Change the SA Password: The internal communication components of WinCC V6 rely on fixed system credentials configured during the automated Siemens setup. Changing the SQL sa account password corrupts WinCC runtime database operations.

Engineer FAQ

Can I install Microsoft SQL Server 2005 or 2008 instead of SQL Server 2000 for WinCC V6?
No. WinCC V6.0 is hardcoded to interact with SQL Server 2000 API interfaces and database architectures. SQL Server 2005 was introduced with WinCC V6.2; WinCC V7.0 adopted SQL Server 2005/2008.

Is it legal to copy the SQL Server 2000 installation files from another WinCC installation?
You may use the Siemens SQL Server media across stations provided that each station possesses an official, licensed copy of SIMATIC WinCC V6.0.

Why does the WinCC installer claim SQL Server is missing even after manual installation?
This occurs if SQL Server was installed as a default instance (MSSQLSERVER) instead of the named instance WINCC, or if the computer name was altered after installing SQL Server.

Technical References

  • Siemens Industry Online Support Entry ID 18832840: Installation requirements for SIMATIC WinCC V6.0
  • Siemens Industry Online Support Entry ID 21923848: Delivery release of WinCC V6.0 SP3 with SQL Server 2000 SP3a
  • SIMATIC HMI WinCC V6.0 Manual: Working with WinCC (Document No. 6AV6392-1CA06-0AA0)

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic+wincc
  • https://industrialautomation.net/search?query=sql+server+2000
  • https://industrialautomation.net/search?query=scada+database
  • https://industrialautomation.net/search?query=legacy+automation
20 respuestas