Follow along for an enriching discussion with our CEO, Peter Herweck, and industry leaders for a captivating Global Keynote at #InnovationSummit Paris 2024. Watch recording and join the #ImpactMaker movement!️
Upgrading Main Standby pair to 2010 R2 from 2009 R2.2 or earlier
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Upgrading from a 2009 R2.2 release to 2010 R2 has some potential issues. R2 depends on secure connections to exchange data and this is where the issue can come up.
The upgrade strategy indicates that in a Main Standby pair the standby gets upgraded first. However, doing so can result in a permanent "Sync" state on the standby after it is restarted. DB log file entries on the Standby machine have messages such as the following where 192.168.2.208 is the MAIN:
23-JUN-2011 17:56:01.328 0140 SVR Accepted connection 5 from 192.168.4.208:4780 to 192.168.4.209:5481...
23-JUN-2011 17:56:01.328 0140 SVR ... Connection 5: Type 13, client version 0x6440D2B (6.68.3371), (Uncompressed,Floating Licence)
23-JUN-2011 17:56:01.328 0140 SVR ... Connection 5: insecure connection rejected
23-JUN-2011 17:56:01.328 0140 SVR ... Connection 5 rejected, shutting down socket. Status C014003F -> The client version is not supported by the server.
23-JUN-2011 17:56:01.328 0140 SVR ... Connection 5 closed
This issue is caused by older versions of CS not connecting over SSL connections.
Solution
The solution is to allow non secure connections, enabling one of these options fixes this issue (I enabled both on the customers system and now we cannot reproduce here in the office)