Dear All,
I was doing a test of server fail-over with one of our project and I have noticed that every time the server switch from node A to node B if you change page in Desktop UI, the client crash. If I wait a couple of minute the UI desktop doesn't crash. My hypothesis is that Desktop UI, when the system move from Node A to Node B, updates the own cache and it takes some minutes, if you try to change page during this phase the Client crash.
Is there any way to fix the problem ? Is something that can be sorted out installing a new release of Desktop UI ? I am using the release 3.15.0.0. The WinCC OA release is 3.15 patch 16.
Waiting for your kind reply.
Best Regards,
Michele.
Desktop UI and Redundancy Crash
- michele.casella@vanderlande.com
- Posts:6
- Joined: Tue Apr 30, 2019 10:46 am
Desktop UI and Redundancy Crash
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Desktop UI and Redundancy Crash
During a redundancy switch the Desktop UI does not do anything with its cache.
If a UI gets the information that a redundant server is active it makes refresh of dpConnects/dpQueryConnects.
Meanwhile P021 for 3.15 is available.
Can you please do the upgrade and check afterwards if the problem still occurs.
Best Regards
Leopold Knipp
Senior Support Specialist
If a UI gets the information that a redundant server is active it makes refresh of dpConnects/dpQueryConnects.
Meanwhile P021 for 3.15 is available.
Can you please do the upgrade and check afterwards if the problem still occurs.
Best Regards
Leopold Knipp
Senior Support Specialist
- michele.casella@vanderlande.com
- Posts:6
- Joined: Tue Apr 30, 2019 10:46 am
Re: Desktop UI and Redundancy Crash
Hi Leopold,
Thanks for your advise I will try it today, and I will let you know.
Best Regards,
Michele.
Thanks for your advise I will try it today, and I will let you know.
Best Regards,
Michele.
- michele.casella@vanderlande.com
- Posts:6
- Joined: Tue Apr 30, 2019 10:46 am
Re: Desktop UI and Redundancy Crash
Hi Leopold,
I can confirm the patch 21 solve the issue. However, I would like to ask you if there is a way to make the initial connection of the Desktop UI, server independent. Indeed, Desktop UI needs an IP address or hostname to work. If I configure my connection with node A and node A, for some reason, is down the client cannot establish the connection with the server. Do you know a way to by-pass the problem?
Waiting for your kind reply.
Best Regards,
Michele.
I can confirm the patch 21 solve the issue. However, I would like to ask you if there is a way to make the initial connection of the Desktop UI, server independent. Indeed, Desktop UI needs an IP address or hostname to work. If I configure my connection with node A and node A, for some reason, is down the client cannot establish the connection with the server. Do you know a way to by-pass the problem?
Waiting for your kind reply.
Best Regards,
Michele.
- gschijndel
- Posts:376
- Joined: Tue Jan 15, 2019 3:12 pm
Re: Desktop UI and Redundancy Crash
For a redundant server you can pass the '-server' option twice. In case the first server cannot be reached, it should use the second server.
- michele.casella@vanderlande.com
- Posts:6
- Joined: Tue Apr 30, 2019 10:46 am
Re: Desktop UI and Redundancy Crash
HI Gschijndel,
I finally have time to check what you suggested and it works. I made a shortcut of the desktop ui connection on my Desktop and I added the parameter -server with redundant server ip address.
Thanks again for the help.
Best Regards,
Michele.
I finally have time to check what you suggested and it works. I made a shortcut of the desktop ui connection on my Desktop and I added the parameter -server with redundant server ip address.
Thanks again for the help.
Best Regards,
Michele.