Skip to main content

"E8535 Failed to receive data from the client agent. (ADDRESS= (DNS (IP Address)), EC=code, COMMAND=0"


Title:  Backup fails in the middle of the job with the error below "E8535 Failed to receive data from the client agent. (ADDRESS= (DNS (IP Address)), EC=code, COMMAND=0"



Description:

The universal client agent is a component which can be called by various clients such as client agent for windows, exchange agent and so on and its services are shared. Now this can be accomplished in 2 approaches.

  • In process component.




  • Out process component.


An in-process component is implemented as a DLL, and runs in the same process as its client application, enabling the most efficient communication between client and component. Each client application that uses the component starts a new instance of it.

An out-of-process component is implemented as an EXE, and unlike a DLL, runs in its own process space making the communication between client and component marshaled across the process boundaries. A single instance of an out of process component can service many clients.

The calling approach is environmental specific and can specify the approach to be used in the application.

In Arcserve application, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA Arcserve Backup\UniversalClientAgent\Options specifies the various clients that can call Universal client agent component.

For example:
\Options\1000 --- Client Agent for windows
\Options\2000\1070 --- Oracle Agent
\Options\2000\1400 --- SQL Agent
\Options\1060 --- Exchange Agent for Document level.

You can get this information from registry.

Go to \options sub key, highlight any folder within the sub key (For example 1000), you would see an registry value product name, which gives the name of client agent. Now the registry value "Executable" within sub key 1000 specifies the way universal client component is being called by the clients. With the value set to '0' it will run the component in 'in process mode'. The value set to '1' will run the component process in 'out of process mode'.

The above error may be resolved by changing the approach the universal client component is being called by various clients due to environmental specifications.

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to create a backup of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to backup, restore, edit the registry, please review the relevant Microsoft Knowledge Base articles on support.microsoft.com.

Solution:

This error is not specific to client agent for windows only; you can see this error for exchange agent, SQL agent and so on.

If the client agent for windows is failing with the above error, go to the registry key

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA Arcserve Backup\UniversalClientAgent\Options\1000

change the value of 'Executable' from 0 to 1 or vice versa.

The sub keys for other agents are:

\Options\2000\1070 --- Oracle Agent
\Options\2000\1400 --- SQL Agent
\Options\1060 --- Exchange Agent for Document level

If the issue is not resolved, you may revert the changes.

Comments

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932

This article outlines the protection against the publicly disclosed Secure Boot security feature bypass involving the BlackLotus UEFI bootkit (CVE-2023-24932). It includes steps to enable the necessary mitigations and provides guidance on creating bootable media. I will provide: - An overview of the CVE issue. - Pre-requisite actions within ADK. - Detection and remediation scripts for CVE-2023-24932. - Instructions for creating a WinPE Boot.wim file to support systems that have undergone remediation. - A breakdown of the files changed and how to boot WinPE to support systems before remediation. 1. Secure Boot Security Feature Bypass Vulnerability CVE-2023-24932 see MSRC CVE-2023-24932 is a security vulnerability involving the BlackLotus UEFI bootkit, which allows attackers to bypass Secure Boot protections. This vulnerability enables the execution of malicious code at the UEFI level, potentially leading to persistent and evasive threats. Mitigations for this issue include updates to th...

Blackberry How to factory reset your device.

Here's how to FACTORY RESET the device. Install Blackberry Desktop Manager on a PC.  Connect the Blackberry to the PC with a USB cable. From a DOS prompt (command) window on the users PC (from Start - Run  type cmd <OK>  then change directory path to: C:\Program Files\Common Files\Research In Motion\Apploader     by typing cd\ (enter)  followed by cd Program Files (enter) then cd Common Files (enter)  etc etc Run the command:   Loader.exe /resettofactory That will bring the Blackberry back to the state it should be in when you get a brand new one out of the box.