Skip to main content

1E 8.1 (on-premises)

Known Issues

Lists of the current known issues with implementing, configuring, and using 1E Patch Success.

If you cannot find an issue and its workaround on this page:

If you need further help, please refer to the Troubleshooting page for how to contact 1E Support and the technical support process.




Patch Success instructions that are using SCCM as a patch source log remote connections to Microsoft WSUS server.

1E Client logs creating a remote connection to Microsoft WSUS Server with a CheckOnline property set to false to indicate that 1E Client is using Windows Update Agent local cache to retrieve data. This log can easily be interpreted as an attempt to connect to the internet to collect data, which is not what the 1E Client is doing. Instead, the instructions are collecting additional information from WUA local cache in order to supplement missing data collected by ConfigMgr client and will therefore be regularly logged during normal operation of Patch Success instructions. ConfigMgr client omits Patch IDs for all installed patches and therefore requires additional information to be collected from a different source to match missing Patch IDs.

The log message should be interpreted as 1E Client performing a query against a Windows Update Agent local cache.

Deploying a missing patch directly via the internet returns the following error "overallDownloadResult is Null"

If a missing patch is deployed onto a target device, but the Windows Update service is not running or stopped, the 1E Client will return error: "overallDownloadResult is Null"

In later versions of the 1E Client, the returned error will be: "End search for updates because: (0x8024001E). Operation did not complete because the service system was being shutdown"

Ensure the Windows Update service is running before attempting to re-deploy the patch.

Deploying a missing patch to 1E Client may result with it logging "WARN - No updates to install" and the patch gets updated as "Not applicable"

If a missing patch is deployed, but there is no associated deployment package in ConfigMgr then the response will be returned as "Not applicable".

Ensure the patch has been packaged and deployed through ConfigMgr so that it is available to the CM clients before attempting to re-deploy the patch.

Patch Success charts and tables have inconsistent data.

Tachyon sync schedule process leads to new patch data being replaced with stale patch data when BI ETL is run.

When syncs are scheduled in the recommended way then the nightly BI ETL will replace all device and patch data in the BI star schema and cube with potentially stale SLA inventory data.

Execute a new Tachyon sync, once the expected devices have reported in patch data (check Tachyon Explorer → Instructions → History → "Returns Patch status for...") then execute a new BI ETL. This will result in up to date device and patch data in both the BI star schema and the cube.

Deploying a patch directly via the internet may return failure "End search for updates failed because: Not enough storage is available to complete this operation"

and WindowsUpdate.log will show an associated error: "WARNING: WU client failed Searching for update with error 0x8007000e"

On Windows 7 / Server 2008 R2 there is a known issue with the Windows Update that causes it to return an "8007000E" error message.

This may be seen if in the Patch Success page, a patch is deployed with the check box enabled for "Enable patches to be downloaded onto devices directly from the internet instead of the default (SCCM)".

Please ensure the update that contains the improvements to Windows Update Client is applied in order to allow for further Patch Success deployments to function correctly.

History page should be hidden when user only has Patch success viewer permissions

The history page is displayed when a user has no access to Patch Success instructions.


Patch Success will show all devices irrespective of the permissions on management groups.

BI cube does not have the permissions model required to filter the management groups correctly. In addition, the permissions model only assigns management groups to instructions therefore will not cater for BI cube permissions.