Dear colleagues,

We have a problem with server-client architecture of the PCS7 8.1 software.The batch clients tend to detach from the server time to time. The system is not redundant! Components of the system are the followings:

1. ES.
   Installed Windows: Windows 7 EnterpriseBuild 7601
2. OS+Batch Server:
   Installed Windows: Windows Server 2008 R2 Standard Build 7601
3. CL1 -> Wincc client, Batch client
   Installed Windows: Windows 7 EnterpriseBuild 7601
4. CL2 -> Wincc client, Batch client
   Installed Windows: Windows 7 EnterpriseBuild 7601
5. CL3 -> Wincc client, Batch client, Recipe Editor.
   Installed Windows: Windows 7 EnterpriseBuild 7601
6. PH -> ProcessHistorianbeírni a verzióját

The system runs in a fully virtualized environment of the VMware ESXi 6.0.

The OS+Batch server communicates with the clients through the Terminal Bus in the VMware. There are no other network components included ( like switch, etc.).

In case we experience a detach, there is a black X mark in the Simatic Shell next to the OS+Batch server name, and if we try to run the BatchCC then there is a message indicating the OS+Batch server can not be reached.

It is strange that the WinCC client is not detached from the OS server during this phenomenon.

The solution to this problem does not require a reboot, only need a Simatic Shell update, then everything seems to be fine, the problem is gone. (attached picture)

Settings in the Simatic Shell (attached picture):

• Multicast Time to Live (TLL)-> Set to 4
• At Multicast Proxy: the OS+Batch server Terminal Bus IP address is added.

The settings of the Windows and the antivirus softwares are set step by step according to the manual of the Siemens

Anyone have met a similar problem before? Is there any solution to this problem?

Thank you for your answers in advance.

Best regards,

Szabolcs Kiss

We are seeing the same problem.

Did you ever find out the reason?

Or what was your solution?

Thanks in advance!

Good Morning.

We are experiencing the same problem on one of our systems.

The setup is similar.

One OS Server

One Batch Server

Two OS Clients.

About once a week when you try open the Batch client from a OS Client, it seems as if the Batch server Connection has been lost. The OS Client connection to the OS Server is still working as normal. This can occur on one, or both of the OS Client, not necessarily at the same time.

When we have a look at the Simatic Shell on the client it shows the Batch Server with a Red X.

However, if I right-click -> Update on the Simatic Shell. then the communication is restored.

Has this issue been resolved?

Or does anyone have a suggestion how to resolve this?

Regards

Johann Louw

AutoGen_4151552

Good Morning.

We are experiencing the same problem on one of our systems.

The setup is similar.

One OS Server

One Batch Server

Two OS Clients.

About once a week when you try open the Batch client from a OS Client, it seems as if the Batch server Connection has been lost. The OS Client connection to the OS Server is still working as normal. This can occur on one, or both of the OS Client, not necessarily at the same time.

When we have a look at the Simatic Shell on the client it shows the Batch Server with a Red X.

However, if I right-click -> Update on the Simatic Shell. then the communication is restored.

Has this issue been resolved?

Or does anyone have a suggestion how to resolve this?

Regards

Johann Louw

 Hi Johann, 

It seems like you are having network issues / IP conflicts / host name resolution issues. Can you troubleshoot suspicious errors from event viewer?

I suggest you create a new thread for this discussion.