Resolving WinCC v7.4 SP1 Update 5 License and SQL Errors

Resolving WinCC v7.4 SP1 Update 5 'A Basic Application Could Not Be Started' and SQL Server Startup Errors

Siemens WinCC V7.4 SP1 is a 32-bit SCADA/HMI engineering runtime platform that is tightly coupled to its licensing service (Automation License Manager) and the bundled SQL Server instance that hosts project archives, user administration, and the runtime database. After deploying Update 5 (Upd5) on a Windows 10 engineering station, several field reports surface a consistent symptom: launching WinCC Explorer yields A basic application could not be started. Please check your software license, immediately followed by Project could not be created. This reference documents the root-cause matrix, the supported Windows 10 build matrix per Update level, and a deterministic recovery procedure validated on production engineering laptops.

1. Problem Description

1.1 Symptom Set

• WinCC Explorer launches; the splash screen appears, then closes with a Windows message box: A basic application could not be started. Please check your software license.
• A second dialog follows: Project could not be created.
• Event Viewer » Application log records CCAlgTestCtrl or CCLicenseCtrl errors with source WinCC.
• No new project (.MCP) can be created; existing projects fail to open with a generic "License missing" prompt even when a valid license key is plugged in.
• sqlservr.exe may or may not be visible in Task Manager depending on whether the SQL Server service has been started by the WinCC bootstrapper.

1.2 Affected Builds

The fault is reported most frequently on the following configuration:

1.3 Error Code Mapping

2. Root Cause Analysis

Three independent causes can each produce the symptom chain, and on a freshly deployed laptop they often co-exist. Treat the matrix below as a checklist.

2.1 Operating System / Update Mismatch

WinCC V7.4 SP1 Upd5 is qualified against Windows 10 Creators Update 1709 (build 16299). When the engineering station is upgraded to Windows 10 October 2018 Update 1809 (build 17763) – either by Windows Update or by a fresh image – the internal COM bootstrapper of Upd5 fails to register the CCAlgTestCtrl.dll and the SQL Server instance fails to start in mixed-mode authentication. The fix is to upgrade to WinCC V7.4 SP1 Update 9 or higher, which is the first update level officially released against Windows 10 1809. The Siemens official entry for the Update 5 package is available at Update 5 for WinCC V7.4 SP1 and WinCC V7.4 SP1 ASIA — ID 109756812.

2.2 Active Directory Domain Privilege Drop

If WinCC V7.4 SP1 was originally installed while the workstation was joined to an Active Directory domain and the SQL Server (WINCC) service was granted domain credentials, the service account may no longer have log-on-as-service rights after a domain policy change, machine re-imaging, or temporary removal from the domain. The license service cannot start the SQL instance, which cascades into the "basic application" message. Siemens recommends that, when feasible, the workstation be removed from the domain for the install, the service account re-bound, and the workstation re-joined only after a successful project launch.

2.3 Corrupt / Stuck SQL Server WINCC Instance

WinCC V7.4 SP1 ships with Microsoft SQL Server 2014 SP2 (32-bit) and registers a named instance WINCC. The WinCC bootstrapper calls net start SQLServerWINCC on first launch. If the instance is in Recovery Pending state, the instance folder is missing, or the protocol encryption negotiation fails, the bootstrapper exits with the generic license message even though the underlying fault is SQL. Always confirm sqlservr.exe presence in Task Manager » Details before assuming a license fault.

2.4 Automation License Manager (ALM) Not Running

The ALMService.exe (Siemens Automation License Manager service) and its helper s7oiehsx64.exe (or the 32-bit equivalent s7oiehsx.exe) must be running. When ALM is stopped or its License Server is mis-routed to an unreachable network node, WinCC reports a license failure even on stations that hold a valid local USB license key.

3. Pre-flight Checklist

1. Verify Windows 10 build: winver. Record the OS build (e.g., 16299.x = 1709, 17763.x = 1809).
2. Verify installed WinCC components: Control Panel » Programs » Programs and Features. Note the version string of SIMATIC WinCC V7.4 SP1 and any installed Update entries.
3. Confirm the ALM service is set to Automatic and is Running: services.msc » Siemens Automation License Manager.
4. Confirm the SQL instance: services.msc » SQL Server (WINCC) must be Running; startup type Automatic.
5. Run the diagnostics collector: SIMATIC Assessment Suite – Data Collector (SAS-DC), formerly SIMATIC Diagnostics Tool, available per SAS-DC entry 65976201. The bundle gathers ALM traces, SQL logs, Windows event logs, and installed-component inventory into a single .zip that can be attached to a Siemens Service Request.

4. Step-by-Step Recovery Procedure

Step 1 – Match the OS to the Update Level

Cross-reference the Windows 10 build against the WinCC Update matrix:

If the OS is 1809 and the installed WinCC is Update 5..8, the corrective action is to upgrade WinCC to Update 9 or later. The Update 5 base package is documented at Update 5 for WinCC V7.4 SP1 — download entry; later Updates (9, 10, 14) follow the same self-extracting archive delivery model.

Step 2 – Re-verify the License Service

1. Start the Automation License Manager UI from the Start menu.
2. If the local license is greyed out, plug the USB key into a different USB port and click Refresh.
3. If a network license is used, open Connect to License Server, enter the floating-server hostname, click Test Connection.
4. If ALM service is stopped, open an elevated command prompt and run:

   net start "Siemens Automation License Manager"
   sc qc "Siemens Automation License Manager"

Step 3 – Reset the SQL Server (WINCC) Instance

1. Stop the SQL service: net stop SQLServerWINCC.
2. Move the per-user database files aside (do not delete):

   cd C:\Windows\SysWOW64\config\systemprofile\Documents\WinCC\Database
   mkdir _backup
   move *.mdf _backup\
   move *.ldf _backup\

   For per-project databases, also inspect %ProgramFiles(x86)%\Siemens\Automation\WinCC\bin\<project>\ for *.mdf / *.ldf pairs and back them up.

3. Start the service again: net start SQLServerWINCC.
4. Launch WinCC Explorer; the bootstrapper will recreate the empty CC_WINCC_<computername>_<project> database.

Step 4 – Domain Re-binding (Conditional)

1. Remove the workstation from the Active Directory domain.
2. Reboot, log on as the local Administrator.
3. Re-launch WinCC Explorer; confirm a project can be created.
4. Re-join the workstation to the domain and re-issue the SQL service log-on credentials through SQL Server Configuration Manager » SQL Server Services » SQL Server (WINCC) » Properties » Log On.

Step 5 – Capture Diagnostics with SAS-DC

Run the SIMATIC Assessment Suite – Data Collector. The bundle, available via SAS-DC entry 65976201, captures the ALM trace, the SQL Server ERRORLOG, the WinCC project structure, and Windows event logs. The output .zip is the standard attachment when raising a Service Request at Siemens Industry Online Support.

5. Verification

1. Launch WinCC Explorer. The splash screen should complete without the "basic application" dialog.
2. From the menu, choose File » New and create a test project verify_wccc_test.
3. Confirm the project folder is created under %ProgramFiles(x86)%\Siemens\Automation\WinCC\WinCCProjects\verify_wccc_test\.
4. Open the WinCC Explorer » Computer » Properties dialog and verify the runtime database connection string resolves to WINCC instance.
5. Open Control Panel » Administrative Tools » ODBC Data Sources (32-bit) and verify the System DSN CC_WINCC_<computername>_<project> points to SQL Server Native Client 11.0 on (local)\WINCC.
6. Start the runtime; verify tag simulation updates without "Database not available" alarms.

6. Field-Proven Troubleshooting Matrix

7. Compatibility Notes and Constraints

• 32-bit only: WinCC V7.4 SP1 is delivered exclusively as a 32-bit application. The 32-bit ODBC administrator (odbcad32.exe in %windir%\SysWOW64) is the correct tool for editing System DSNs. Using the 64-bit applet will not see the WinCC entries.
• SQL Server 2014: The embedded SQL Server is locked to the WINCC named instance. Side-by-side installations of SQL Server Express 2016/2019 will not break WinCC but should not be promoted to the default instance on a WinCC engineering station.
• Windows 10 Enterprise LTSC: Versions based on build 17763 (LTSC 2019) behave identically to consumer Windows 10 1809 and require Update 9 minimum.
• Virtualization: VMware Workstation and Hyper-V pass-through of the USB license key requires the Siemens ALM daemon extension to be installed in the guest, not just on the host. RDSH/RemoteApp deployments are not supported for engineering; only runtime.
• Antivirus interference: Several commercial AV packages (notably products with "ransomware shield" features) interfere with the WinCC COM registration. Excluding the WinCC install tree from real-time scanning is documented best practice.

8. Service Request Path

When the matrix above does not resolve the fault on the first pass, raise a Service Request via the Siemens Industry Online Support portal at support.industry.siemens.com. Attach the SAS-DC archive (see Step 5) and reference the WinCC Update 5 entry 109756812. Siemens support typically responds within one business day for active warranty / Subscription contracts.

9. Preventive Maintenance

1. Track WinCC Update level alongside the Windows 10 build in your CMMS. A simple matrix table printed beside each engineering station is sufficient.
2. Schedule the SQL Server (WINCC) instance backup with sqlcmd -S (local)\WINCC -E -Q "EXEC sp_BackupDatabase ..." on a weekly cadence; the WinCC runtime databases grow proportionally to the tag archive size.
3. Periodically export the license inventory via ALM UI » License » Export; store alongside the SAS-DC output.
4. When applying Windows 10 feature updates, defer WinCC engineering until the new Windows build is reflected in the Siemens compatibility matrix.

10. Glossary