Error: "Named pipe could not be opened" in the Symantec Mail Security for Microsoft Exchange console.

Products

• Mail Security for Microsoft Exchange

Issue/Introduction

The error "Named pipe could not be opened" is received when attempting to save configuration changes to scheduled or manual scans or "Named pipe could not be found" when deploying changes in the Symantec Mail Security for Microsoft Exchange (SMSMSE) management console.

Cause

SMSMSE uses named pipes to communicate scanning requests from VSAPI, manual scans, and schedule scans.  A lack of permissions or hung services can prevent SMSMSE from opening named pipes.

Resolution

This problem can have multiple causes, please check the following in this order:

1. Restart following services:
Symantec Mail Security for Microsoft Exchange
Symantec Mail Security Utility Service

Test to see if a simple service restart fixes the problem by reproducing the conditions that failed previously.  If it still fails, continue to step 2
 

2. Verify read/write permissions have been set for the SMSMSE Admins Group for the following directories/registry keys:

Directory
On 32-bit Systems:
C:\Program Files\Symantec\SMSMSE\<version>\Server
C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

On 64-bit Systems:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

or

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files 

C:\Program Files(x86)\Symantec\SMSMSE\<version>\Server

Making the Directory changes:
1. Right click each of the above folders and select Properties
2. Select the Security tab.
3. Add “SMSMSE Admins” group and grant read/write access to the directories listed above (if not already present)

Registry
On 32-bit Systems:
[HKLM]\SOFTWARE\Symantec\SMSMSE\<version>\Server
[HKLM]\System\CurrentControlSet\Services\MSExchangeIS\VirusScan

On 64-bit Systems:
[HKLM]\SOFTWARE\Wow6432Node\Symantec\SMSMSE\<version>\Server
[HKLM]\System\CurrentControlSet\Services\MSExchangeIS\VirusScan


Making the Registry changes:
1.Open the registry editor by go to Start > Run and type regedit, then click Ok
2. Locate and select the registry keys mentioned above.
3. Select the Edit menu, then select Permissions
4. Add SMSMSE Admins group and grant read/write access to the Registry keys listed above (if not already present).

Test to see if changing user account permissions fixes the problem, if not, continue with step 3.


3. The Symantec Mail Security for Microsoft Exchange service needs to have rights to perform it's duties as well. To eliminate possible problems with service permissions complete the following steps:

1. Go to Start > Run and type services.msc
2. Select the Symantec Mail Security for Microsoft Exchange service, right-click and select Properties.
3. In the Properties dialog box click the Log On tab
4. Change the Log On from Local System Account to "This account" and choose a domain administrator.
5. Restart the service.
6. Repeat steps 2-5 for the Symantec Mail Security Utility Service.

If this resolves the named pipe error, you now know that the permissions for the Local System account are limited in way that prevents the SMSMSE service from opening named pipes.

4. If you continue to experience this error after completing steps 1-3, please follow the steps in this document to create an SMSMSEUITraceOutput.log for Symantec Technical Support to analyze: How To Debug Common Management Framework (CMaF)