OneSite Patch uses multiple sensors to detect the state of products and patches on a target device. There is a known issue in build 9.2.###.# that affects the Services sensor in new installations. This issue does not occur if the Adaptiva Client was upgraded from version 9.1 or 9.0.
For more information about sensors generally, see Adaptiva Support Portal – Sensors and Sensor Factories.
The Services sensor is used in patches listed in the spreadsheet attached at the bottom of this article. These patches include mostly drivers and some application patches, such as TeamViewer and TeamViewer Host.
When you try to apply an affected patch, the following error will appear in the PatchingAdmin, SoftwareDeploymentManager, and Adaptiva.err logs:
INFO - Completion status for patch [##########], request [zpvzWCccTZKDdTfMrwrQsw] is [PatchDeploymentResult : patchID=[##########],, operation=1, softwareDeploymentOperationStatus=2, reasonCode=1, reasonMessage='com.adaptiva.expressionevaluator.EvaluatorException: Error Message = Failed to fully execute sensor with id[249000018], Error Code = 1 (0x1), Source Object = null
…
Caused by: java.lang.UnsatisfiedLinkError: 'boolean com.adaptiva.inventory.inventoryagent.WinNTServiceInventoryAgent.getServices(java.util.Vector'
…
', wuaRebootRequired=false]. - PatchingAdmin - TID=91, AdaptivaTimer - SoftwareDeploymentManager. ExecutingTask-SoftwareDeploymentManager$InstallationTimerTask
In Patching Analytics > Devices, the patch appears as Failed in the Device Activity pane.
In many cases, the Services sensor runs after installation to check or restart a service. Although the patch installs successfully, the Post Install Action fails, marking the installation as failed. If the patch uses Windows Installer, check the installation log in the msiLogs folder under AdaptivaClient\Logs.
Because the system marks the installation as failed, it retries up to five times. This may impact users depending on the patch and its behavior.
New installations of the 9.2 client do not include a required DLL for the Services sensor. Upgraded clients from version 9.1 or 9.0 do include this DLL and will not experience the issue.
Important
This is a temporary workaround intended for a small number of devices until a resolution is available.
-
Download the DLL from: https://adaptiva-releases.adaptivacdn.cloud/InventoryAgentNativeCode_9.2.967-x64.zip.
-
Unzip the contents, and copy the
InventoryAgentNativeCode.dllto:C:\Program Files\Adaptiva\AdaptivaClient\binNote
This file does not exist in new 9.2 installations. If the client was upgraded from 9.1 or 9.0, the file is already present. Do not overwrite it if it exists.
-
Restart the Adaptiva Client service.
You can complete these steps even without the DLL if the patch installed successfully. The DLL is only required to prevent future post-install failures.
Reset Deployment Failures
-
Navigate to Patching Analytics > Devices, and then find the affected device.
-
From the Actions menu, select Reset Deployment Failures for Device.
-
In the Failure Reset Request dialog, you can add any additional devices or select a Business Unit to target multiple devices.
-
Next to Reset Products, select + Browse.
-
In the Select Software Product dialog, select the product associated with the patch, and then select OK.
-
Select OK to start the reset.
Note
The reset will complete in about about 5 minutes.
Rescan the Device
-
From the Actions menu of the affected device, select Scan Device.
-
In the Scan Request dialog, add additional devices as needed.
-
Next to Software, select + Browse.
-
In the Select Object dialog, select the product associated with the patch, and then select OK.
-
Select OK to start the scan.
The device should now show Compliant for the patch, assuming the installation was successful.
If you have any questions, please open a ticket with Adaptiva Support at https://support.adaptiva.com.