This error typically occurs during the runtime startup phase. It indicates that the WinCC Runtime environment failed to initialize, often due to database corruption, SQL Server issues, or stuck background processes.
wincc problem (a basic application could not be started ) - SiePortal
Did this error start appearing after a recent or power failure ? Share public link
Check its status. If it is stopped, right-click it and select (or Restart if it is already running). Ensure the Startup type is set to Automatic .
A mismatch between the application access point and the network card causes runtime failures. A Basic Application Could Not Be Started Wincc 7.5
Sometimes project folders lose their specific network and security sharing settings.
Siemens software is often flagged by aggressive antivirus heuristics.
The phrase "check your software license" is a red herring. In many cases, the license is installed and active, but WinCC cannot communicate properly with the underlying services it relies on.
: Indicates DCOM or Windows user permission restrictions. Conclusion This error typically occurs during the runtime startup phase
: An outdated Edge browser on Windows 10 (version 20H2) can disrupt the SQL Server installation used by WinCC.
Recent Windows updates or antivirus software blocking Siemens background services (such as CC_COMDNA.exe or CCProjectMgr.exe ).
This tool manages security settings for all SIMATIC software. For the error "A basic application could not be started," the Security Controller is a key diagnostic step to repair or apply critical system security settings.
: After a successful installation, avoid making major changes to the OS, such as changing the computer name or installing other large-scale engineering software that might cause conflicts. Share public link Check its status
The error often relates to licenses, even if a valid one is present.
WinCC 7.5 relies entirely on a dedicated Microsoft SQL Server instance to run. Press Win + R , type services.msc , and press . Scroll down to find SQL Server (WINCC) .
Before diving into the fixes, it helps to understand what triggers this alert. WinCC 7.5 relies heavily on Microsoft SQL Server and specific Windows security architectures. The primary culprits include: