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

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta