We have a number of mac OS/X Lion 10.7.4 user complaining that when asked to upgrade Netconnect by IVE 7.1R9 they gets an error: "An error occurred while extracting one of the Network Connect Components".
Is this a known issue, does anyone know of a fix?
Solved! Go to Solution.
This issue in 7.1r9 with the error "An error occurred while extracting one of the Network Connect components." will not occur on 7.2R2 ( is available for download on support site) and will also be fixed in 7.1R10 that is being scheduled. (please contact JTAC for the dates)
I have not heard of any cases about this specific issue yet. Please open a case with JTAC for further review.
Would also like to know if there is a fix, exactly the same issue here on 10.7.3 and 10.7.4 after the upgrade to R9.
I have a case open with JTAC about this. The case number is 2012-0514-0826.
Could you please let us know the outcome of this and or if they provide you with updated firmware/a fix. Thanks!
I'm still winding through the Support technician's typical Network Connect diagnostic script, unfortunately. Probably no answers today. He asked for the Juniper logs under ~/Library/Logs/Juniper Networks/, which are not created (at least not in a fresh install) because we're not getting that far into invoking Network Connect.
Since the manual NetworkConnect.dmg installer works fine on everyone I have given it to so far, it seems it is just the automatic installation mechanism that is corrupted or broken.
I have been doing exactly the same with the DMG, works just fine.
I can also confirm that a installation of the DMG works fine although it is not possible to launch NC session from the client itself, still have to launch it from portal..
I also noted a strange GUI-error with the client installed from DMG, the input fields in NC client was "see-through".. I could see whatever what was behind the client..
JTAC is still working on it. I hope to hear soon.
The transparent username and password fields has been reported to Apple. JTAC was able to narrow down that after upgrading Safari to 5.1.6 and above is the cause of this issue. We are hoping to have any update for this specific issue soon.
As far as the installation error message with DMG, I have not heard any cases related to this issue.