IT Management Suite

 View Only

Symantec Agent fails to register: Error: “HTTP Request Failed: No connection could be made because the target machine actively refused it” 

Oct 20, 2015 01:20 PM

Symantec Agent fails to register: Error: “HTTP Request Failed: No connection could be made because the target machine actively refused it”

Issue:

The agent installation is successful but the Symantec Management Agent doesn’t register to the server and show a GUID generated against the Computer ID: You won’t be able to see the client in the Server console since it never gets registered.

 

 Error message:

  HTTP Request Failed: No connection could be made because the target machine actively refused it. (-2147014835)]]>

Here is the screenshot of the agent when you have this issue:

1_0.png

 

In the client machine, check the Symantec Agent logs under C:\Program Data\Symantec\Symantec Agent\Logs. Open any log file and if you see an entry saying:” process='AeXNSAgent.exe' pid='1664' thread='1692' tickCount='143021' >

  <![CDATA[HTTP Request Failed: No connection could be made because the target machine actively refused it. (-2147014835)]]>

</event>”, here is the solution:

In the client machine, open a command prompt and go to the following path:

C:\Program Files\Altiris/Altiris Agent

Type ? And hit enter:

 

1_1.png

 

 

Type aexnsagent /diags to enable the agent diagnostics feature.

 

Usually with the diagnostics disabled, the Symantec Agent will appear like this when you right click the icon:

 

2_0.png

 

Enable the diagnostics as below:

 

3_0.png

 

Right clicking the agent, will give you the additional options now:

 

4_0.png

 

 

Launch NS Web Config as below:

 

5_0.png

 

 

You will notice that the check mark for”Use default NS URL Schema”  is not selected in the following window though you see the server information is displayed correctly:

 

6_0.png

 

If you look at the first tab ( Logs), you can see the error message ([HTTP Request Failed: No connection could be made because the target machine actively refused it)  in the logs there.

 

In the NS Web Config tab, put the check mark for”Use default NS URL Schema”  and hit ‘Update’.

 

Wait for a few minutes and go back to the Symantec Agent ‘Settings’ tab. Hit ‘Update’ and you will see a Computer GUID against Computer ID:

 

Once you are done, you may disable the Diagnostics by running the following command:

 

7_0.png

 

 

 

 

Statistics
0 Favorited
1 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
docx file
Symantec Agent fails to register.docx   112 KB   1 version
Uploaded - Feb 25, 2020

Tags and Keywords

Comments

Oct 27, 2015 11:49 AM

I have seen these on SMP 7.1 and 7.5 . I cannot see any errors or warnings in NS side as the client won't even register it to the server. The client machines were running Windows 7 32 bit and 64 bit Enterprise editions.

Oct 21, 2015 09:37 AM

Hello,

This particular error could appear for several reasons. Can you provide more information for more accurate troubleshooting. What SMA version are you installing and on what OS? Can you see errors/warnings in log on NS side.

Related Entries and Links

No Related Resource entered.