After upgrading, software is failing to install or update for users.

[netdefilr_]

Recently we upgraded to 7.1R10.

A good amount of tickets have been coming in regarding this.

In some cases, if you install(or reinstall) some of or all of these applications:

- Java

- Network Connect

- WSAM

- Citrix Receiver

Then the user is fine. While it would be nice to get around this, I had a user that could install WSAM. But could not initiate WSAM from Internet Explorer or Firefox. I disabled the AVG firewall, reset Internet Explorer options, still nothing. If anyone has suggestions on fixing the reinstallation issues, it would be greatly appreciated. Although I'm not sure how to move further with this particular ticket, where the web browser just can't initiate WSAM, or Terminal Sessions.

Thanks.

[jayLaiz_]

Hi,

Do the users have admin rights?

which version of JIS are the client workstations running if clients have no admin rights?

Regards,

Jay

[netdefilr_]

Most of the users have admin rights. It just seems like a manual reinstall is necessary. Sometimes you're lucky with the specific app, but most times you have to reinstall java, wsam, ect.

[jayLaiz_]

From which version did you upgrade the SA to?

I think it is better to investigate this via a JTAC ticket

Regards,

Jay

[-red-_ · Accepted solution]

See if this is your issue. We ran into this upgrading from 6.5R5 to 7.1R10

 [KB22040] Show KB Properties

SUMMARY: Users are unable to launch UAC/IVE client software such as Junos Pulse, Host Checker, Network Connect, Windows Secure Application Manager (WSAM), Terminal Services, and so on. PROBLEM OR GOAL: When users attempt to connect, the application looks like it is trying to launch but fails. There is little or no external notification that there is a problem; other than failing to launch.
Users will see the Please Wait... screen for the application launch and may even see the executable attempting to launch; but nothing more is observed.
When looking at the client-side logs, the following sequence is observed (edited for clarity and emphasis added for the keywords to check against):
2011/10/04 11:03:43.819 1 dsVerifyHelper.cpp:184 - 'DSVerifyHelper::verify()' Enter: C:\DOCUME~1\tester\LOCALS~1\Temp\JuniperSetupClientInstaller.exe dsVerifyHelper.cpp:184 - 'DSVerifyHelper::verify()' WinVerifyTrust() failed, 800B010A
2011/10/04 14:58:04.833 1 dp59 - 'DSVerifyHelper::verify()'  Enter: C:\Documents and Settings\tester\ Application Data\Juniper Networks\Setup Client\JuniperSetupDLL.dll dsVerifyHelper.cpp:184 -'DSVerifyHelper::verify()' WinVerifyTrust() failed, 800B010A

CAUSE: The certificates, which are used to sign the Juniper binary files, are not installed on the client machine.

SOLUTION: The following certificate needs to be installed on the machine in the root CA store:
VeriSign Class 3 Public Primary Certification Authority - G5
Once the above certificate is downloaded and installed, the chain is allowed to be successfully created.

[netdefilr_]

I came across a computer that this did work on. Right after installing the cert, the apps installed and launched as normal.

Thanks!