You see the error: No Symantec Scan Engine registered. There is no VirusScanning possible

Article:TECH97580

Created: 2009-01-19

Updated: 2009-01-03

Article URL http://www.symantec.com/docs/TECH97580

Article Type
Technical Solution

Environment

Show all

Languages

Show all

Problem

Symptoms
After a reboot, the Symantec Protection 5.1 for SharePoint Servers status shows that there is no Scan Engine registered. Also, when you look at the ScanEngine log, you see that the Scan Engine was unable to be reached at 127.0.0.1. At this point no documents are accessible and no documents can be uploaded.

You may see the following when clicking on your farm overview:

Cause

The Symantec Protection 5.1 for SharePoint Servers service started before the Scan Engine service. When it could not connect to the Scan Engine, it reported the error and did not retry.

Solution

To change Windows settings to prevent startup conflicts with Symantec Scan Engine and Protection for SharePoint Service:

On the Windows taskbar, click Start > Run.
In the Open box, type the following command: regedt32.exe
Press Enter.
In the Registry Editor, in the left pane, go to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SymantecSharePointScan
In the right pane, right-click DependOnService, and then click Modify.
If the DependOnService value does not exist, create a new REG_MULTI_SZ (Multi-String Value) named DependOnService.
In the Value Data box, type: symcscan
Click OK.
Exit the Registry Editor.
Restart the computer

Attachments

noscanengine.jpg (31 kBytes)

Legacy ID

2009111912101954