Bootstrapping can fail if Symantec Antivirus is installed on Enterprise or Site Coordinator (Named Pipe Error)
Originally Published: 2008-06-12
Article Number
Applies To
RSA DLP Site Coordinator
Symantec Antivirus
Issue
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
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
HTML Tags Embedded in Client Web Requests in cross site scripting Number of Views FIM 3.1.2 - CryptoJ jar causing signature verification errors with md2 signature algorithm Number of Views Potential cross-site request forgery (CSRF) attack thwarted found in pi_webserver.log - RSA enVision Number of Views Error: '%1 is not a valid win32 application' when starting RSA RADIUS Server 6.1 Number of Views Error while accessingthe IWA connector site http : error system.web/identity@impersonate is set to true. ADP turned off. Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?
