Reset Search
 

 

Article

KB45237 - ESAP Upgrade/downgrade fails in certain upgrade/downgrade paths on Windows Endpoints.

« Go Back

Information

 
Last Modified Date6/16/2022 1:47 PM
Synopsis
This article describes an issue where ESAP Upgrade/downgrade fails in certain upgrade/downgrade paths on Windows Endpoints.
Problem or Goal
On Windows Endpoints if an ESAP upgrade/downgrade occurs in the following paths, sometimes the upgrade/downgrade
may fail without the end user being aware of it as the connection still succeeds using the currently installed ESAP version.
However, if the user is expecting some functionalities or fixes in the target ESAP version, it will not be available as the
ESAP upgrade/downgrade has failed.

ESAP Upgrade/Downgrade paths impacted:

a.    Upgrade from ESAP 3.9.9 to ESAP 4.0.0 & above. 
b.    Upgrade from ESAP 4.0.0 to ESAP 4.0.1 & above.
c.    Downgrade from ESAP 3.9.9 to ESAP 3.9.8 & below.
d.    Downgrade from ESAP 4.0.0 to ESAP 3.9.9 & below.

Note: The affected ESAP versions are 3.9.9. & 4.0.0.

This applies to both browser and Pulse Desktop client connections.

This issue can be confirmed by checking the following Pulse Desktop Client log snippet on the endpoint.
 
00262,09 2022/04/19 20:50:27.831 1 SYSTEM PulseSecureService.exe hcUtils p6528  
tACC hcWinFileUtils.cpp:363 - 'safeReplaceFiles' Failed to delete all files from directory  
C:\Program Files (x86)\Common Files\Pulse Secure\TNC Client Plugin\OPSWAT, restoring 
the files back

00359,09 2022/04/19 20:50:28.238 1 SYSTEM PulseSecureService.exe hcUtils p6528 
tACC hcWinFileUtils.cpp:134 - 'copyFile' Failed to copy file from C:\Program Files 
(x86)\Common Files\Pulse Secure\TNC Client 
Plugin\OPSWAT.1650381627\wa_3rd_party_host_32.exe to C:\Program Files 
(x86)\Common Files\Pulse Secure\TNC Client 
Plugin\OPSWAT\wa_3rd_party_host_32.exe, error:32

00348,09 2022/04/19 20:50:28.238 1 SYSTEM PulseSecureService.exe hcUtils p6528 
tACC hcWinFileUtils.cpp:223 - 'copyAllFiles' Unable to copy file C:\Program Files 
(x86)\Common Files\Pulse Secure\TNC Client  
Plugin\OPSWAT.1650381627\wa_3rd_party_host_32.exe to C:\Program Files 
(x86)\Common Files\Pulse Secure\TNC Client Plugin\OPSWAT\wa_3rd_party_host_32.exe

 
Cause
This is due to the handle not being released on the wa_3rd_party_host_32.exe process in ESAP 3.9.9. & 4.0.0. on time during Upgrade/downgrade.
Solution
This issue is resolved in ESAP 4.0.1 onwards.

In the meantime, if any user experiences this issue, the following solutions can be adopted:
  1. Pulse Desktop Client - Restart Pulse Service.
  • Go to Services.msc (From the search option) -> Right Click on “Pulse Secure Service” and select “Restart”.
       2. Browser/Pulse Desktop Client - Reboot the device. 

Note: This will be a one-time activity only.
 
Related Links
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255