Attempts to remediate or apply software updates to some computers result in errors in the GFI LanGuard Remediation details section:
- "Remote registry failed"
- "RPC not available"
- "The network path was not found"
The following messages may be show in the lanss_v102_patchdeployment.csv log:
"warning","RemediationEngine","Failed to open SC Manager: The RPC server is unavailable" "info ","RemediationEngine","<< TRemoteRegistryServiceManager.StartRemoteRegistryEx Result: False, dwLastError: 1722" "info ","RemediationEngine","<< StartRemoteRegistry Result: False" "warning","RemediationEngine","Registry connection failed Error 53: The network path was not found"
- GFI LanGuard
- All supported environments
- Ensure GFI LanGuard can resolve the client hostname to the corresponding IP address using IPv4 protocol. Verify the name resolution also over Windows command prompt. Verify the required settings https://www.gfi.com/support/products/gfi-languard/KBID001940
- Ensure the account specified in Remediation Center> Remediate button > Credentials is part of the target machine's "Administrators" group (directly or via another group)
- Ensure the following services are started on the target machine:
- Remote Registry Service
- Remote Procedure Call Service (RPC)
- Ensure the other requirements are met according to the following article What changes are required on a Windows Vista or later machine to allow GFI LanGuard to scan and deploy updates to it?
- These errors are normally caused when the account that is used to connect to the target machine (specified in the Remediation Center > Remediate button > Credentials) and copy over the requisite files for remediation (Patchagent.exe, deploypatches.bat, patch install files, etc.) does not have full administrative access to the machine
- The remote registry service, or Remote Procedure Call service is not enabled.
- GFI LanGuard is not resolving the client Hostname to the corresponding IP address