WinCC V7.2 Update 8: Troubleshooting Start Picture Not Found

David Krause2 min read
SiemensTroubleshootingWinCC
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

A WinCC V7.2 Update 8 client reports “start picture not found” even though the client can ping the server by both IP address and server name. The evidence points to two separate checks: whether the client can open the configured start picture from the server and whether the client has the required system connectivity.

Confirmed configuration and symptoms

Item Observed condition
Server operating system Windows Server 2008 R2
Client operating system Windows 7 Professional
WinCC version V7.2 Update 8 on both computers
Name and IP reachability Client-to-server ping succeeds using the IP address and server name
Firewalls Temporarily disabled on both computers during testing
Client message “start picture not found”
Additional symptom The client cannot connect to the field system

A successful ping confirms basic IP and name reachability only. It does not prove that the client can open the configured picture file or access the required folder.

Test access to the start picture

  1. On the WinCC client, open WinCC Graphics Designer.
  2. Attempt to open the configured start picture directly from the server.
  3. If the picture does not open, investigate file or folder access restrictions between the client and the server. The available evidence identifies security access to the relevant folder as the primary hypothesis, but it does not specify the folder, account, or required permission set.
  4. If the picture opens successfully, file visibility is not disproved completely, but the diagnostic focus should move to the configured start-picture reference and the separate connectivity symptom.

Separate network reachability from system connectivity

The reported inability of the client to connect to the field system may be related, but the evidence does not establish that it causes the missing-picture message. Treat it as a separate fault until testing demonstrates a dependency.

Do not use disabled firewalls as proof that security is no longer involved: the suggested diagnostic concerns permission to open files in a specific folder. Restore the intended firewall configuration after testing rather than leaving both firewalls disabled.

Resolution and verification criteria

Correct the access restriction or start-picture reference identified by the direct Graphics Designer test. Then restart the client runtime and confirm that it loads the configured start picture without the message. Independently confirm whether the client now connects to the field system; if it does not, continue that diagnosis separately because basic ping success does not verify application or field communication.

FAQ

Why does WinCC V7.2 Update 8 say “start picture not found” when ping works?

Ping by IP address and server name confirms basic reachability, but it does not confirm that the client can open the configured picture file. Test the start picture directly in WinCC Graphics Designer on the client.

How do I test whether WinCC folder security causes “start picture not found”?

Use Graphics Designer on the client to open the configured start picture from the server. Failure to open it supports investigating the client account's access to the relevant file and folder.

Does disabling both firewalls rule out a WinCC security problem?

No. In this case, the identified security hypothesis is permission to open files in a specific folder, which is distinct from firewall filtering. Restore the intended firewall settings after the temporary test.

Back to blog