How to Troubleshoot a PCS 7 V8.2 Server Missing from SIMATIC Shell

When a PCS 7 V8.2 server disappears from SIMATIC Shell after a system restart, first verify that WinCC is using the intended terminal-bus network adapter on both the server and the station viewing it. Siemens documents checking the SIMATIC Shell adapter selection and, on systems with multiple adapters, placing the terminal-bus adapter first in Windows connection order. Then check IP initialization and computer-name resolution. A generic network check alone does not establish that WinCC is using the correct interface, and the reported case does not identify a confirmed cause.

What SIMATIC Shell Shows

SIMATIC Shell is a WinCC component for centralized maintenance and diagnostics of computers integrated into a WinCC client-server system. The source describes two servers and reports that server1 is missing after power-off; it does not say whether the WinCC runtime or client connection also failed. Treat Shell visibility and process-runtime availability as separate observations.

Check the SIMATIC Shell Terminal-Bus Adapter

Perform these checks on server1 and on the engineering station or WinCC client from which server1 is missing. Siemens' WinCC Diagnostics guide directs engineers to open Windows Explorer, select the SIMATIC Shell folder, and inspect the computers shown in its navigation tree. If a station is absent, inspect the network-adapter order and the terminal-bus selection.

In Windows Explorer, open the SIMATIC Shell folder and note whether server1 appears. Check from another WinCC station if available; this helps distinguish one viewing station's configuration from a server-side issue.
Right-click the SIMATIC Shell entry and choose Settings.... In the terminal-bus selection dialog, identify the adapter or IP address selected for WinCC communication and compare it with the approved terminal-bus design.
If the computer has multiple network adapters, open Windows Network Connections > Advanced > Advanced Settings and inspect the Connections order. Siemens' WinCC Diagnostics guide says the terminal-bus adapter must be at the top of that list.
Do not change the selected adapter casually. In the procedure reported with the case, confirming a changed selection opens a reinitialization prompt; reinitialization can interrupt communication briefly. Coordinate any selection change with the site operations plan and use the installed WinCC version's local help.

Verify Addressing and Name Resolution

WinCC V7.4 SP1 documentation says WinCC uses TCP/IP on the terminal bus and, with multiple adapters, the IP address used for communication with other WinCC stations must be selected in SIMATIC Shell Settings. It also cautions that DHCP address assignment can be too slow in some configuration or project-management situations. This is relevant guidance for the WinCC component version, not proof that the reported PCS 7 installation has a particular WinCC update.

Record the selected terminal-bus adapter and its current IP address on server1 and the observing station. Confirm each address is valid for the intended terminal-bus subnet and has not changed unexpectedly after restart.
From Windows, compare reachability by IP address and by computer name using the site's approved diagnostic method. Siemens' WinCC Diagnostics guide documents using nslookup to query host-name resolution. A name-resolution mismatch points to a different fault branch than an unreachable IP address; neither result alone proves that SIMATIC Shell or runtime communication is healthy.
If the address is supplied by DHCP and initialization delay or address changes are evidenced, involve the network administrator to review the address plan. Siemens documents static IP configuration as a possible response to slow DHCP assignment in this context; do not impose a static address without network approval.

Check Restart and Multi-Adapter Context

For a recurrence only after restart, compare startup behavior and the multi-user project startup sequence with the site's approved PCS 7/WinCC design. The WinCC V7.4 SP1 manual describes possible delays after restart in distributed systems related to the operating system's master-browser service and domain or workgroup administration, and says to start multi-user projects first to prevent such delays. This is a documented consideration, not a guaranteed explanation for server1's absence.

The same manual points users to the WinCC Information System section Configurations > Distributed Systems > System behavior in Runtime > Special features of communication using a server with several network adapters. Review that version-applicable guidance before changing routing or adapter behavior. The exact WinCC version and network topology in the reported system are not specified.

Corrective Actions by Finding

Use the observation to select a bounded next action:

FindingNext actionSIMATIC Shell selects the wrong terminal-bus adapterHave the WinCC/network administrator confirm the intended interface, then change it in a coordinated window and accept reinitialization only when its brief communication interruption is acceptable.Terminal-bus adapter is not first in connection order on a multi-adapter stationCorrect the order according to the Siemens guidance and the site's approved network design; repeat the check on relevant WinCC stations.IP address is invalid, changed, or not initialized at startupResolve addressing with the network administrator; verify that the approved address plan is stable for runtime.IP reachability works but name lookup returns a wrong or missing mappingCorrect the applicable DNS/name-resolution configuration through the responsible Windows/network administrator, then retest by name.The checks pass but Shell still omits server1Compare the exact WinCC version and local Information System guidance, then collect station-specific diagnostics for Siemens or the system integrator. The available case information does not establish another specific repair.

Verification

After any approved correction, reopen or refresh the SIMATIC Shell view and confirm server1 is listed from the affected station. Recheck the selected adapter and address, then independently verify the WinCC client-server connection and runtime behavior using the site's normal operational checks. A visible Shell entry confirms discovery in that view; it does not by itself prove process communication, redundancy state, or correct runtime data.

Limitations and Operational Precautions

The reported configuration is PCS 7 V8.2 with two servers, but it does not specify WinCC service pack/update, Windows version, whether the server pair is redundant, adapter layout, address method, startup sequence, or any diagnostic result. WinCC V7.4 SP1 documentation is therefore used as relevant historical guidance only; confirm the installed WinCC component version before applying version-specific details. Changing an adapter selection can trigger network reinitialization and a brief interruption. Schedule configuration changes with operations and follow the site's change, backup, and recovery procedures. No case-specific root cause or successful repair was reported.

Engineer FAQ

Does “network is OK” rule out an adapter-selection problem? No. Basic network reachability does not establish that WinCC selected the intended terminal-bus interface. Check SIMATIC Shell Settings and the Windows adapter order on the relevant stations.

Should the terminal-bus adapter be first in the Windows list? Siemens' WinCC Diagnostics guide says it must be at the top of the Connections list when multiple adapters are used. Confirm this against the installed version and approved topology.

Does a server appearing in SIMATIC Shell prove runtime is healthy? No. Shell is a maintenance and diagnostics view; verify WinCC client-server communication and process data separately.

Should every WinCC station use a static address? No. Siemens discusses static IP configuration when DHCP assignment is too slow in the described WinCC configuration context. Network administrators must decide addressing based on the site's network plan.

Could the problem be a restart delay? It is possible as a diagnostic branch: WinCC V7.4 SP1 documentation describes restart-related delays in distributed systems. The case supplies no timing observations, so this is not a confirmed explanation.

Technical References

Siemens, WinCC Diagnostics, Article ID 109757865, V2.0 (10/2019), Section 5.4 “SIMATIC Shell,” pp. 41–42: https://cache.industry.siemens.com/dl/files/865/109757865/att_963121/v5/109757865_WinCC_Diagnostics_en.pdf
Siemens, SIMATIC HMI WinCC V7.4 SP1 – General information and installation, System Manual A5E40840020-AA (02/2017), Section 2.2 “Notes on operation,” pp. 63–64, and Section 1.6.6 “Operation with multiple network adapters”: https://cache.industry.siemens.com/dl/files/335/109746335/att_915480/v1/WinCC_GeneralInfo_Installation_Readme_en-US_en-US.pdf

How to Troubleshoot a PCS 7 V8.2 Server Missing from SIMATIC Shell