Re: Service Pack SI57907 for C/A: Any issues?

On 30-Nov-2015 08:21 -0600, Szepesi Frigyes wrote:

On 28-Nov-2015 03:41 -0600, Szepesi Frigyes wrote:

I just installed the 64 bit version of Service Pack SI57907 for
Client Access for Windows. After installing it, 5250 sessions and
System i Navigator do not start. Has anyone encountered similar
issues?

There is nothing I could find reported in the PSP, nor any APAR for the any symptoms ("CA400EXP" "OPNAV") AND ("UNPRED" OR "OTHER" OR "INCORROUT"), neither with nor irrespective "64 bit" being included.

That they "do not start" is a fairly nebulous description. Any specifics; e.g. error messages?

Is the Win7 system updated to the latest SP for that PC OS? And any recent updates have been applied also?

Was the image size identical to what was recorded on the FTP site? Perhaps download another copy, and then compare the binary streams, verifying there are no differences between the prior and the new download; if wrong size or differences found, then try applying with the newer download.

<<SNIP>> I am on Windows 7, I am an admin on this machine. I
installed the previous SP for C/A without any issues (actually, to
cure this problem <ed: see prior quoted message>, I uninstalled C/A
on my PC, re-installed it, and installed the previous SP, which is
SI56695. It works fine. As I saw in the readme.txt for the current
SP, there WERE some changes in 5250 emulation.

Given the prior ServicePack was installed without issue, presumably there would be no issue for the special\pre-requisite instructions at [http://www.ibm.com/systems/power/software/i/access/windows_sp.html] with link showing redirect within page to [www.ibm.com/systems/power/software/i/access/windows_sp.html#action], but may be worth reading [again].

Might be helpful [mostly] to others, though likely burdensome to you [per likely needing to install the fixpack again and record errors and collect some traces after experiencing the difficulty again], to report the problem to your service provider [which may be IBM]. That is to suggest, for both lack of anyone here responding, and no apparent APARs, seems the issue may be unique to you, or not yet reported [outside of this discussion[, and thus unknown to IBM.