Resolving WinCC Runtime Start Picture Not Found After Migration

1. Problem Description

The "Start picture not found - please select desired start picture" dialog appears the moment the WinCC Runtime is activated. The runtime fails to load the configured start screen even though the same start picture is visible in the WinCC Explorer and the Computer Properties dialog correctly references the configured Start Picture field. In many reported field cases, the issue surfaces immediately after migrating a WinCC project from a previous version (for example WinCC V7.0/V7.1 to V7.4/V7.5) or after restoring a project archive to a new server share.

The runtime prompts for a start picture because it cannot resolve the configured start picture reference at activation time. This is a runtime-side configuration lookup failure, not a graphics designer issue. The configuration data layer is in an inconsistent state.

2. Environment and Affected Versions

Confirm the installed WinCC build by opening WinCC Explorer > Help > About. Note the exact Version, Build, and any installed Hotfix (HF) numbers. Many of the file-consistency issues described below are fixed in WinCC V7.4 SP1 and later, but migration paths crossing more than one major SP revision may still trigger them.

3. Root Cause Analysis

The WinCC runtime reads its startup configuration (which picture is the start picture, which computer is the server, which packages are loaded) from a set of internal database files. When these files drift out of sync with the visible WinCC Explorer configuration, the runtime cannot resolve the start picture reference and shows the dialog asking the user to manually select one. Per the Siemens Industry Online Support entry Entry ID 109763119, the canonical cause is an inconsistent DCF file.

3.1 DCF File Inconsistency

The .dcf (Database Configuration File) in a WinCC project contains the compiled runtime configuration, including the picture-tree mapping that maps the configured start picture name to the actual .pdl file on disk. The DCF is regenerated by the WinCC server when the project is recompiled and is consumed by both the server and any clients that attach to the server. Corruption or mismatch between the DCF and the project database can produce the start picture error on the server itself, on individual clients, or on both.

3.2 Stale .dc Cache Files

The WinCC server directory also contains working copies of internal data with the .dc extension. These are not the same as .dcf files - they are temporary/rebuild artifacts produced by the internal data manager. After a migration or an aborted compile they may be left in a state where the runtime cannot reconcile the start picture entry.

3.3 Network Share Permission Mismatch

WinCC server and client computers must access the project folder using the same credentials and access rights. When the project is hosted on a UNC share (for example \\SERVERNAME\WinCC_Projects\MyPlant) and the share or NTFS permissions restrict the runtime service account, the DCF can be partially readable but not writable during regeneration. The runtime then sees a stale picture reference and fails to resolve the start picture.

3.4 Migration Path Artifacts

When a WinCC project is migrated across major versions, the migration tool upgrades .mcp, recompiles scripts, and rebuilds picture databases, but it may leave behind older .dcf, .log, and .db artifacts from the previous version. The new runtime, compiled against a newer internal schema, can refuse to honor the start picture entry if it finds an old DCF record that does not match the new schema.

4. Pre-Diagnostic Checklist

Before applying the corrective procedures, capture the following. They are required for verification and for Siemens Support if escalation becomes necessary.

1. Open WinCC Explorer > Computer Properties and screenshot the Graphics Runtime tab. Confirm the Start Picture field and the Window selection.
2. Close the runtime (WinCC Explorer > File > Activate Runtime to deactivate if needed) and close WinCC Explorer on all computers.
3. Stop the CCAgent, WinCC, S7DOS, and SQLSERVER (WINCC) Windows services on the server.
4. Take a file-level backup of the entire WinCC project folder. Do not skip this step; the corrective procedure deletes working files.
5. Copy the project folder locally (for example C:\WinCC_Projects\MyPlant_backup) before any server-side edit.

5. Solution A - Reset DCF and Working Files (Server-Side)

This is the canonical fix documented in Siemens KB 109763119.

5.1 Step-by-Step

1. Close all WinCC applications on the server and on every client that attaches to this server.
2. In Windows Explorer, navigate to the WinCC server project directory (the folder that contains the .mcp file). Example: \\SERVERNAME\WinCC_Projects\MyPlant\.
3. Search for all files with the .dc extension inside the project folder and any subfolder such as \GraCS, \Library, \PAS, \ArchiveManager, and \RT. Select them and delete.
4. Open SIMATIC Manager on the engineering station or directly on the server (the same machine that hosts the project folder).
5. Open the WinCC project, then from the menu choose File > Open and select the .mcp file if not already loaded.
6. From the project tree right-click the server and select Server Data, then choose Rebuild All (German: Serverdaten neu erzeugen). In WinCC V7.4 and later this is reachable via Tools > Server Data.
7. Wait until the rebuild completes with no errors. Inspect the Compile.log in the project root for warnings referencing picture name resolution.
8. Re-activate the runtime (WinCC Explorer > File > Activate Runtime) and confirm the start picture loads without the dialog.

5.2 Why This Works

Deleting .dc working copies forces the data manager to re-create them from the canonical .db and .dcf on next start. Rebuilding the server data regenerates the .dcf from the current configuration so the start picture mapping matches the active project database. The two actions together restore referential integrity between configuration and runtime.

6. Solution B - Restore Share Permissions (Recommended After Solution A)

If Solution A produces a temporary fix but the error returns after the next service restart or runtime activation, the root cause is a Windows share/NTFS permission mismatch. This is the second confirmed fix from the field discussion.

6.1 Required Permissions

6.2 Procedure

1. Stop WinCC Runtime and WinCC Explorer.
2. Open Computer Management > System Tools > Shared Folders > Shares on the server hosting the project.
3. Locate the share used for the WinCC project (for example WinCC_Projects$). Right-click Properties > Share Permissions and clear any restrictive ACL entries (especially Read-only or password-protected share settings).
4. Add Everyone with Full Control at the share level only as a temporary diagnostic step. Production deployments should restrict this to a dedicated WinCC service group.
5. Open Security tab on the project folder. Grant SYSTEM, the WinCC runtime service account, and the local Administrators group Full Control. Propagate to all child objects.
6. On each client, verify that the user account running the WinCC client can browse the project folder by typing the UNC path in Windows Explorer and creating a test file (then deleting it).
7. Restart the CCAgent service and the SQL Server instance WINCC.
8. Reactivate the runtime from the server.

7. Solution C - Clean Migration Workflow

When the start picture error is tied directly to a version migration, perform a controlled re-migration rather than carrying the old artifacts forward.

1. On the source server, archive the project using WinCC Project Duplicator (Start > Siemens Automation > WinCC > Project Duplicator). This strips runtime-only state.
2. Restore the archive on the target machine using WinCC Project Migrator for the destination version.
3. Open the migrated .mcp and run Tools > Project Documentation > Cross Reference to confirm that the start picture *.pdl still exists in \GraCS and is referenced.
4. Run Tools > Compile > Multiple OS Projects > All and inspect for any error code that references picture resolution.
5. Perform Solution A (delete .dc files and rebuild server data) one more time after migration is complete.

8. Diagnostic and Verification Procedures

8.1 Inspecting the DCF

1. Open the project folder and locate MyPlant.dcf (or the .dcf matching the project name).
2. Open it in a text editor such as Notepad++. Search for the configured start picture name (matches the value in Computer Properties > Graphics Runtime > Start Picture). Example expected token: Pictures:Start.PDL or \GraCS\Start.pdl.
3. If the picture name is missing or points to a path that no longer exists, the start picture reference in the DCF has drifted. Rebuild server data (Solution A).

8.2 Runtime Log Inspection

1. Open WinCC Explorer > Tools > Diagnostics or read \WinCC_Projects\MyPlant\diagnostics log files.
2. Filter the log for the keyword Start picture or for picture name tokens used in the configuration.
3. Open \WinCC_Projects\MyPlant\RT\RTLog.log for runtime-time picture loading entries.

8.3 Database Verification

1. On the server, open SQL Server Management Studio and connect to WINCC instance.
2. Query the dbo.PDLPicture or equivalent picture-management table to confirm the start picture row exists and points to a valid PDLFile.
3. Run dbcc checkdb('WINCC') to confirm database integrity. Migrations that crash mid-process can leave the picture tables in an inconsistent state.

8.4 Verification After Fix

1. Activate WinCC Runtime from the server.
2. Confirm the start picture loads within 5-10 seconds without prompting.
3. Restart the server cold and verify the start picture loads automatically.
4. Activate WinCC Runtime from each client and verify the picture loads.
5. Deactivate and reactivate 3-5 times to rule out first-run vs subsequent-run inconsistencies.

9. Troubleshooting Matrix

10. Prevention Checklist

• Always archive the project via WinCC Project Duplicator before any migration, restore, or major edit.
• Use a dedicated service account for the WinCC runtime and SQL Server WINCC instance. Document the account and password lifecycle.
• Avoid placing the project folder under a user's Documents profile or under OneDrive/DFS-R replicated paths. Replication collisions can corrupt the DCF.
• Disable Windows Defender real-time scanning exclusions for *.dcf, *.db, *.pdl, and the project root to prevent locking during regeneration.
• Schedule annual validation of share/NTFS permissions against the matrix in Section 6.1, especially after group policy changes.
• After any hotfix or service pack installation on WinCC, perform Solution A as a preventive measure before the next runtime activation.
• Maintain a documented procedure for client-side project folder cleanup. The WinCC client side stores cached .dc files that can be deleted without data loss.

11. Related Configuration Pitfalls

11.1 Picture Tree Naming Conflicts

If two pictures share the same display name in the Graphics Designer but reside in different folders, the runtime can resolve the wrong one. Always use unique picture names and document them in the project naming convention.

11.2 Incorrect Picture Server Assignment

On clients, Computer Properties > Server must point to the correct server prefix used by the picture tree. A mismatched prefix causes the runtime to look for the picture under a path that does not exist on the server.

11.3 Corrupt Package Container

When the start picture is part of an imported package and the package container (*.pck) is missing, the runtime will not load the picture even though it appears in the picture tree. Reimport the package via Project > Package Import.

12. References to Official Documentation

• Siemens KB 109763119 - Why do you get the message "Start picture not found" on the client although it has been configured?
• SIMATIC WinCC V7.5 SP2 system manual, sections on Runtime Configuration and Server/Client Architecture
• WinCC Project Duplicator and Project Migrator user guides (shipped with the WinCC installation media)
• Microsoft Windows Server documentation for SMB share permissions and NTFS ACL inheritance

FAQ