cancel
Showing results for 
Search instead for 
Did you mean: 
ssiops
Level 7
Report Inappropriate Content
Message 1 of 7

SCOM agents can't communicate after weekly patch

After we installed our weekly McAfee VirusScan patch last week the SCOM agents were no longer to communicate with the Operations Manager.  The error we keep getting is:

The OpsMgrConnector cound not connect to (SERVERNAME):5723.  The error code is 10061L(No connection could be made because the target machine actively refused it.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.

We have verified the connectivity and the server is running but the agents are still not able to communicate with the Ops Manager.

6 Replies
ssiops
Level 7
Report Inappropriate Content
Message 2 of 7

Re: SCOM agents can't communicate after weekly patch

No one has any thoughts on this?  We are running Windows Server 2008 R2 Enterprise x64 Edition SP1 on our servers and System Center Operations Manager 2007 R2. 

ssiops
Level 7
Report Inappropriate Content
Message 3 of 7

Re: SCOM agents can't communicate after weekly patch

We've tried a couple different work arounds but neither succeeded:

Workaround 1

Enable ScriptScan in the VirusScan Console:
  1. Click Start, Programs, McAfee, VirusScan Console.
  2. Right-click On-Access Scanner and select Properties.
  3. Under General Settings, click the ScriptScan tab.
  4. Select Enable ScriptScan.
  5. Click Apply and OK.

Workaround 2

Un-register SCRIPTSN.dll:

  1. Select Start, Run, type cmd, and press ENTER.
  2. Type the appropriate command and press ENTER:

    32 bit computers:
    cd c:\Program Files\Common Files\McAfee\SystemCore

    64 bit computers:
    cd c:\Program Files (x86)\Common Files\McAfee\SystemCore
    cd c:\Program Files\Common Files\McAfee\SystemCore

  3. To completely disable the SCRIPTSN.dll, type the following command and press ENTER:

    regsvr32.exe /u SCRIPTSN.dll

k3tg
Level 14
Report Inappropriate Content
Message 4 of 7

Re: SCOM agents can't communicate after weekly patch

I certainly do not imply any disrespect with your issue but I think you need to be posting in the Business Community for assistance.

This community here is for the Home Office Products

ssiops
Level 7
Report Inappropriate Content
Message 5 of 7

Re: SCOM agents can't communicate after weekly patch

OK moved to Business.  Thanks.

ssiops
Level 7
Report Inappropriate Content
Message 6 of 7

Re: SCOM agents can't communicate after weekly patch

So I've read on other sites there might be a sDAT that can fix this issue?  Anybody?  It's so lonely in here...

wwarren
Level 15
Report Inappropriate Content
Message 7 of 7

Re: SCOM agents can't communicate after weekly patch

Not an issue I'm familiar with sorry.

Network communication issues, at least with regard to VirusScan Enterprise if that is observed to be the catalyst or cause, bring focus immediately to our mini-firewall filter driver (mfewfpk.sys and mfetdik2.sys).

If you have a reproducible test case, you can confirm the involvement of our code by renaming the driver(s) and rebooting - then test.

However, as a test it offers no help toward finding root cause, it's simply a litmus test to verify our code is part of the equation.

William W. Warren | S.I.R.R. | Customer Success Group | McAfee