Bootstrapping can fail if Symantec Antivirus is installed on Enterprise or Site Coordinator (Named Pipe Error)
Originally Published: 2008-06-12
Last Modified: 2023-10-06
Article Number
000045940
Applies To
RSA DLP Enterprise Coordinator
RSA DLP Site Coordinator
Symantec Antivirus

Issue
Workaround for bootstrapping Site Coordinator agent from an Enterprise Coordinator machine?or an agent from a Site Coordinator Machine if Symantec Antivirus is installed on Enterprise Coordinator or Site Coordinator machine
Bootstrapping of agents from Site Coordinator machine will fail for all scan groups belonging to that Site Coordinator having Symantec antivirus. Boostrapping of all Site Coordinator agent from Enterprise Coordinator(having Symantec antivirus) will fail. Error in log will show "Error: Failed to connect Failed to Establish Named Pipe to [hostname]"  or "Win32 Error: (231). All pipe instances are busy"
Resolution
If bootstrapping a Site Coordinator from an Enterprise Coordinator machine?or an agent from a Site Coordinator Machine?on which Symantec Antivirus is installed, the bootstrapping operation may fail.

In this case, the log output will display an error similar to:
"Error: Failed to connect Failed to Establish Named Pipe to [hostname]"

Workaround: Follow the steps below on the machine(s) hosting the Enterprise Coordinator and Site Coordinator(s) from which the bootstrapping occurs. No action needs to be taken on the target machine.

a. Open Symantec Client Security.
b. Select Configure > File System Autoprotect > Disable Networking scanning options.
c. Click OK to save the changes.

Example of log below that is also a name pipe issue "Symantec 10.0.2.2002" This version will not have the check box to disable networking scanning options. Would need to disable the Symantec on the EC/SC to scan

Win32 Error: (231). All pipe instances are busy

Related Articles

Trending Articles

Don't see what you're looking for?