Symantec is aware and is investigating this issue.

Alternately, the following manual process is recommended to be performed as needed:

1) Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services.
2) Rename or delete the current sem5.log
3) Click Start > Run and type CMD then click OK
4) In the Command Prompt type:
For 32-bit: CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
For 64-bit: CD C:\Program Files(x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
5) Press Enter. This will change directories to the folder containing dbsrv11.exe.
6) To force the recreation of sem5.log, type:
For 32-bit: dbsrv11 -f “C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db”
For 64-bit: dbsrv11 -f “C:\Program Files(x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db”
7) Press Enter
8) Click Start > Run and type services.msc then click OK
9) Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services.

Crédito : http://www.symantec.com/business/support/index?page=content&id=TECH178718