It is my understanding that you can keep the old workspace when upgrading to the new CICS Explorer v5.1. Is that correct? We have users on v184.108.40.206 who are upgrading to v5.1 and appear to then have issues with the connections. When keeping the existing connections file, we have experienced either an IZE0106E Connect failed with error "Unexpected end of file from server (SYSH)" or an IZE0106E Connect failed with Service unavailable (SYSH) error message.
We have found, so far, that by deleting the workspace, and starting with a new connections file, there are no issues. Does anyone have any direction regarding the workspace with the upgrade? Or any experience with these errors?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
4 replies Latest Post - 2013-02-20T17:12:02Z by HBruchey
Pinned topic Keep old workspace with v5.1?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-20T17:12:02Z at 2013-02-20T17:12:02Z by HBruchey
Colin_Stone 0600015GYN30 PostsACCEPTED ANSWER
Re: Keep old workspace with v5.1?2013-02-19T08:01:29Z in response to HBrucheyHi Heather.
Sorry you are experiencing these issues. It's related to updates we made in version 5.1 of the explorer which has tightened security up. The Unexpected end of file exception is symptomatic of accessing a port which is either not enabled or is an SSL port. If you access an SSL port without your client indicating that it is SSL, the server doesn't actually give you the clue that it is SSL and behaves like the port is not enabled. This is because you don't want to give clues back if someone is trying to hack into your system. The old Explorer used trial and error to work out if the port was SSL which is something we have now stopped. The net effect is that some of your old connections in your client workspace may now show themselves as being non-SSL when they should be SSL. Your users should be able to edit the connection information and change the SSL setting.
The other exception you describe. "Connect failed with Service unavailable" is one I am not familiar with but would recommend editing the connection details and swapping the SSL setting.
Hopefully with this in mind both keeping the old workspace and using a new workspace with new connections file will be options available to you and your users.
If you would like further details, we have published a technote (1619304) which describes this and also covers some other security areas we have upgraded.
Hope this helps
Colin_Stone 0600015GYN30 Posts