Hi,

We have 1 ES, 2 OS, N Clients and a Historian Server. One of the OS is used for Redundancy.

WinCC version: 7.4. Process Historian version: 2014 SP2

Any update or modification of the WinCC project have to be done on ES and then copy project to OS to apply the change. In addition, all clients must remind connected all time. By that mean when transfer project from ES to OS, we can't deactivate both of the OS. There is no SIMATIC MANAGER on ES but WInCC.

This is what we did to apply change to OS:

1. Deactivated WinCC Master Server. Closed and backup the project.
2. Used Project Duplicator tool on ES to copy (Save As) modified project from ES to WinCC Master. This step is to overwrite the configuration of WinCC project on OS and keep runtime data attached.
3. Activated Project once copy process was finished. 
4. Deactivated stand by WinCC server and closed the project
5. Duplicate project to stand by server using Project Duplicator
6. Opened project. Project would be automatically activated

After done all those steps, everything seem OK except Process Historian. PH only received alarm data. Tag data is not stored into PH. In Data Sources of PH Management Console, tag recovery shows Needed.

I don't know what causing the problem. I appreciate any suggestion and thank you in advance.

Lifeng

whatisthat

Hi,

We have 1 ES, 2 OS, N Clients and a Historian Server. One of the OS is used for Redundancy.

WinCC version: 7.4. Process Historian version: 2014 SP2

Any update or modification of the WinCC project have to be done on ES and then copy project to OS to apply the change. In addition, all clients must remind connected all time. By that mean when transfer project from ES to OS, we can't deactivate both of the OS. There is no SIMATIC MANAGER on ES but WInCC.

This is what we did to apply change to OS:

1. Deactivated WinCC Master Server. Closed and backup the project.
2. Used Project Duplicator tool on ES to copy (Save As) modified project from ES to WinCC Master. This step is to overwrite the configuration of WinCC project on OS and keep runtime data attached.
3. Activated Project once copy process was finished. 
4. Deactivated stand by WinCC server and closed the project
5. Duplicate project to stand by server using Project Duplicator
6. Opened project. Project would be automatically activated

After done all those steps, everything seem OK except Process Historian. PH only received alarm data. Tag data is not stored into PH. In Data Sources of PH Management Console, tag recovery shows Needed.

I don't know what causing the problem. I appreciate any suggestion and thank you in advance.

Lifeng

 Hi! Do you solve a problem? I have a similar situation... And I don't have solution... 

have you need a solution?

i have the same problem

thanks

Hi,

Please make sure to have same version of PH ready component on all machines as installed on PH.

BR,

Jawad

Hi Guys

For this issue follow the steps to clear the ST Cache in the program data folder,

SFCache / PHCache Removal

To facilitate the sync between the PH and OS, go through the steps below

1. Deactivate the runtime on the standby OS.
2. Rename the “Processhistorian.cfg” in the standby OS to “Processhistorian.cfg.old” (In WinCC project folder of the OS server)
3. Restart the standby OS.
4. Activate the runtime (on the standby OS).
5. Wait for the redundancy check to be completed. (explore process alarms/redundancy diag. control Tool)
6. Deactivate the runtime on the master OS.
7. Rename the “Processhistorian.cfg” in the master OS to “Processhistorian.cfg.old” (In WinCC project folder of the OS server)
8. Restart the master OS.
9. Activate the Runtime (on the master OS).
10. Copy SFCache folder to D drive before delete as a backup
11. Location of PHready Cache and SFCache are same “C:\ProgramData\Siemens\SFCache”. PHReady Cache means like a folder name that end with Queue. For instance, AlgCSDataQueue. Delete all from this folder
12. Delete the PH Ready Cache on both OS Servers. Delete the S&F Cache on both OS Servers.
13. Rename the “Processhistorian.cfg.old” on the standby OS back to “Processhistorian.cfg”.
14. Rename the “Processhistorian.cfg.old” on the master OS back to “Processhistorian.cfg”.
15. Deactivate the runtime on the standby OS.
16. Activate the runtime on the standby OS.
17. Wait for the redundancy check to be completed. (explore process alarms/redundancy diag. control Tool)
18. Deactivate the runtime on the master OS.
19. Activate the Runtime on the master OS.
20. Wait for the S&F recovery to be completed.
21. Open the Redundancy Diagnostics Tool and check for tick boxes on “WinCC is Sync” for both servers
22. Open the Process Historian Dashboard and check for Tag data and Alarm Data Transfer