Why a Redundant PCS 7 Server Is Missing from Configure Server Data
An OS client may fail to list a redundant partner even when both servers are reachable. Check that the two OS stations are configured as a redundant pair, that the client is assigned to the intended OS server, that its server package is current, and that each server's SIMATIC Shell redundancy settings use the intended adapter. In the reported case, correcting the client assignment/package and adapter selections made both servers appear when Configure Server Data was opened from the client.
Table of Contents
- Identify where the partner is missing
- Check the redundant OS pair
- Check the client assignment and package
- Check SIMATIC Shell redundancy adapters
- Apply changes in a controlled order
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Identify where the partner is missing
First distinguish the engineering station, OS server and OS client. The reported symptom occurred when Configure Server Data was opened on the client; the operator had been checking the server and expected the client's view to be identical. A successful ping or visibility in SIMATIC Shell proves basic network reachability, but does not by itself prove that the OS client has the correct server assignment and project package.
Check the redundant OS pair
Confirm in the OS project that the partner is configured as the redundant OS server/standby and that the main server points to the correct partner. PCS 7's PC Configuration manual describes redundancy as a coordinated configuration of paired stations and says server-client installations also require assigning clients to servers. The exact dialog labels vary by PCS 7 release, so use the manual for the installed version.
Check the client assignment and package
In the engineering project, verify that the OS client is assigned to the intended OS server pair. Regenerate or update the client's server data package (.pck) after changing the assignment, then download the resulting package to the client using the project's supported procedure. The original report says the client had neither the intended server assignment nor a downloaded package; creating a new shared folder was also part of that site's resolution, but the available evidence does not establish that deleting and recreating a share is a general fix.
Check SIMATIC Shell redundancy adapters
On both redundant server PCs, inspect the SIMATIC Shell Redundancy Settings and select the interface intended for the redundancy connection. Confirm the two sides use the matching physical path and that the selected adapters are connected and correctly addressed. Siemens' PCS 7 V9.1 SP1 PC Configuration manual documents selecting the redundancy connection path for paired PC stations. Do not infer the selected path solely from a successful ping over another network.
Apply changes in a controlled order
- Record the existing OS project and PC-station configuration. 2. Confirm which station is main and which is standby. 3. Correct the pair definition and OS-client assignment in the engineering project. 4. Update and download the client server package. 5. Configure the intended redundancy adapter at each server. 6. Reopen Configure Server Data on the affected client and inspect whether both partner names are listed. Follow the installed release's manual for any required compile, download or restart sequence; this report does not establish a universal sequence.
Verification
Verify the partner list from the same OS client that showed the fault. Then check the OS runtime's displayed server/partner state and confirm client process data remains available during a planned, approved redundancy switchover. Visibility in a dialog, ping response, or a successful package download alone does not prove runtime redundancy. Conduct a switchover only under the site's change-control and availability procedures.
Limitations and Operational Precautions
The report does not specify the PCS 7 version, WinCC version, Windows configuration, or whether the two server projects were generated from the same engineering project. Its folder recreation step is a site-reported action, not a documented universal requirement. Siemens' V9.1 SP1 manual supports the general need to configure the redundant connection and client assignment, but the direct PDF could not be opened in the research browser; confirm release-specific menu paths and deployment steps in the installed documentation.
Engineer FAQ
The primary checks are whether the client is assigned to the correct redundant server pair, whether its generated server package is current, and whether the redundant servers have the intended redundancy interface configured. Test runtime failover only under approved site procedures.
Technical References
- Siemens, PCS 7 – PC Configuration (V9.1 SP1), section on configuring redundancy for high-availability PCs: https://support.industry.siemens.com/cs/attachments/109805407/ps7pck_b.pdf (search-indexed text reviewed; direct retrieval returned HTTP 403).