Phantom75

bilgehan

. . . So I was thinking that problem is related to redundancy concept between servers and standby's. But then it happened on an Engineering Station which has no activated WinCC application running on. . . .

It is definitely connected with redundancy. When you activate the server for the first time and the master cannot find the standby. It can also happen if you are trying to activate a project configured as a multi-station system (redundant servers) on local station (ES). The remedy in this instance is to disable redundancy.

 Hello experts,

This method solved my case, well the first one... 

Now I can runtime Server A (that's generating error before when activating runtime) after deactivating redundancy (while Server B is normally running with activated redundancy).

So, afterward, we downloaded entire the WinCC project from ES to both the redundant Server A and B (to eliminate "conflict", preparing for the re-activation of Server A redundancy). After we downloaded successfully and all clients are up, we tried to re-activate Server A redundancy and viola, the dreaded reboot pop-up reappears! 

So basically our problem now is how to re-activate redundancy without the reboot error? 

Need urgent help, thanks!

------------------------------------------------------------------------------------------
Split from PCS7 reboot error popup.

So we've tried to stop run time Server B before reactivating run time and redundancy of Server A (where the error appears), so it basically mimic the setup of the normally running Server B with activated redundancy, we think if there's no problem with Server A internally, then it must run time with redundancy as Server B. Also we think it might be because the other server is running with activated redundancy during this time would cause some discrepancy. But to our surprise, the reboot error still appears! 

Any help? Thanks much!

Just wanna report that my problem is finally solved.

We just changed the redundancy setting "Synchronize failures of last 2 days only" to "Synchronize all data of the outage period" on WinCC of both servers and both servers are now running with activated
redundancy (clients are also automatically switching when 1 server is down).

Though we're not sure if that setting should really cause that error, it kinda make sense since the server was previously down for more than 2 days, so maybe it's having a problem syncing due to the settings of "2 days".

Well, in any case, I hope it could help anyone. Good day!