A Basic Application Could Not Be Started Wincc 75 Best -

Troubleshooting Guide: "A Basic Application Could Not Be Started" in WinCC v7.5 – 7 Best Fixes

If you are a Siemens WinCC user (specifically version 7.5), you may have encountered a frustrating roadblock right at startup: the dreaded error message "A basic application could not be started."

This error typically appears immediately after launching the WinCC Explorer or when trying to activate a project. It halts all progress, preventing you from accessing your runtime environment, graphics designer, or tag management. For plant operators and automation engineers, time is money. This article breaks down the root causes of this issue and provides the 7 best, most effective solutions to get your WinCC 7.5 environment running again.

Final Checklist: 2-Minute Emergency Response

When the error pops up in a live environment:

| Step | Action | Time | |------|--------|------| | 1 | Run as Administrator | 10 sec | | 2 | Restart SQL Service (services.msc) | 30 sec | | 3 | Check Dongle / License Manager | 30 sec | | 4 | Delete cache folders (GRACS, NO_MSG) | 20 sec | | 5 | Restart PC | 2 min |

If none of these work, you are likely dealing with a corrupted SQL instance or a Windows OS conflict. In that case, the "best" ultimate solution is a clean installation of Windows 10 LTSC 2019 (the officially recommended OS for WinCC 7.5) followed by a fresh WinCC installation. a basic application could not be started wincc 75 best

Fix 6: Check Siemens License Management (No License = No Basic App)

Without a valid license, WinCC will stall at the "basic application" stage. However, the error message does not explicitly say "license missing." It’s a silent killer.

How to verify:

  1. Open Siemens Automation License Manager from the Start menu.
  2. Check that:
    • Your license key (dongle or software license) is visible.
    • The license type is "WinCC RT" or "WinCC RC" (for engineering).
    • The license is not "defective" (red cross icon).
  3. If you use a USB dongle, try a different USB port or reinstall the ALM driver.
  4. Run the "License Cleanup Tool" (available from Siemens support) to remove ghost licenses.

Hidden fix: Delete the folder C:\AX NF ZZ (license cache) and restart the ALM service. The folder will be recreated with fresh license data.

Fix 5: Repair the SQL Server Instance (Most Common for WinCC 7.5)

WinCC 7.5 uses a named instance of SQL Server (typically WINCC). If this instance is corrupted, the basic application cannot start because the database is the "basic application." Troubleshooting Guide: "A Basic Application Could Not Be

How to repair:

  1. Open Control Panel > Programs and Features.
  2. Find Microsoft SQL Server 2014/2016/2017 (WINCC).
  3. Right-click and select Change > Repair.
  4. If the repair fails, uninstall only the WINCC instance (do not touch other SQL instances) and then run the WinCC 7.5 Setup again. Select "Modify" and reinstall the SQL Server component.

Critical Note: Always backup your WinCC projects before repairing SQL. Use the CCCMigrate.exe tool (found in C:\Program Files (x86)\SIEMENS\WinCC\Tools\) to export your data.

3. Step-by-Step Troubleshooting

5. Re-register COM Components (Advanced)

Open Command Prompt as Administrator and run:

regsvr32 "C:\Program Files (x86)\Common Files\Siemens\Bin\CCBasicApplication.dll"
regsvr32 "C:\Program Files (x86)\Siemens\WinCC\bin\CCBasicApplicationServer.exe"

(Adjust paths to your installation)

Step 2: Check Windows Event Viewer

Navigate to Windows Logs → Application. Look for errors from:

Typical event IDs: 1000, 1001, 1026 (indicating a crash in RTSS.exe or CCERuntime.exe).

2. Corrupt Runtime Database (Tag Logging)

A very common cause for this specific error message is a corrupt Tag Logging database. If the Quick Start file or the database archive is damaged, the runtime manager crashes immediately.

8. Community and Forums