locked
ACS forwarder connection problem RRS feed

  • Question

  • Hello.

    I recently install ACS on SCOM 2012 R2 and enable forwarders on domain controllers.2 DCs has connection problem to ACS:

    Forwarder unsuccessfully tried to connect to the following collector(s):
     SCOMServer:51909, status: 0x7A (unknown), source: registry
      addresses tried:
        10.1.95.10:51909
    
     
     If the list of collectors is blank, then AdtAgent was unable to locate a collector.
     
     Common reasons for this message are:
     	The machine(s) listed is not online
     	AdtServer is not running on the machine(s) listed
     	AdtServer on the machine(s) listed is not listening on the specified port
     	TCP connectivity to the AdtServer machine is blocked by firewall, IPSec, or other filtering mechanism
     	AdtServer on the machine(s) listed actively refused the connection (due to policy or current activity load)


    After enabling tracing on Server and agent i receive next:

    Agent:

    [20160510 085108,880][Info ]LookupServersReg(): Found SCOMServer:51909.

    [20160510 085108,958][Error ]QueryEventlogConfig(): Log name Microsoft-Windows-TerminalServices-LocalSessionManager/Operational too long.

    [20160510 085108,958][Warning]ConnectToServer(): Calling Disconnect() with error 0x0000007A.

    [20160510 085108,958][Error ]IoContext(0x3E5B20)::OnRecvComplete(): Disconnecting: dwIo = 0, dwError = 0x000004D4.

    Serer:

    [20160510 085108,935][Error  ]IoContext(0x6E16FA0)::OnRecvComplete(): Disconnecting: dwIo = 0, dwError = 0x00000040.
    [20160510 085108,935][Warning]IoContext(0x6E16FA0)::OnRecvComplete(): Disconnecting.
    [20160510 085108,935][Info   ]AgentClient(0x6E16FA0)::OnDisconnectComplete(): Disconnecting , AgentIP. 

    Please help me to understand and resolve connection issue

    All agents installed from SCOM console and located in same domain


    Tuesday, May 10, 2016 6:56 AM

Answers

  • Hello.

    Problem was with TerminalServices-LocalSessionManager log. Other administrator clone this log into the root of Applications and Services Logs.

    After removing Log via PowerShell and agent restarting all problem Computers successfully connected to ACS Server

    Thanks for the tip. I didn't think that the log file can cause such problems
    • Edited by Sidorenko Andrey Wednesday, May 11, 2016 11:49 AM
    • Marked as answer by Elton_Ji Wednesday, May 18, 2016 7:38 AM
    Wednesday, May 11, 2016 11:47 AM

All replies

  • Hi Sir,

    According to that error on agent , it mentioned "Microsoft-windows-terminalservices-localsessionManager.." .

    "

    Unfortunately, this does not work for events under the ‘Forwarded Events’ or events buried in logs deeper under the ‘Applications and Services Logs’ header.

    "

    http://sc.scomurr.com/scom-2012-using-acs-to-capture-events-from-other-event-logs/

    Best Regards,

    Elton


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    Wednesday, May 11, 2016 9:30 AM
  • Hello.

    Problem was with TerminalServices-LocalSessionManager log. Other administrator clone this log into the root of Applications and Services Logs.

    After removing Log via PowerShell and agent restarting all problem Computers successfully connected to ACS Server

    Thanks for the tip. I didn't think that the log file can cause such problems
    • Edited by Sidorenko Andrey Wednesday, May 11, 2016 11:49 AM
    • Marked as answer by Elton_Ji Wednesday, May 18, 2016 7:38 AM
    Wednesday, May 11, 2016 11:47 AM