Logs in smp.log look like this:

2009-02-23 09:41:02,744 [main] INFO  Authenticator Initialized
2009-02-23 09:41:02,761 [main] INFO  Exaprotect Advanced Server initiating startup sequence
2009-02-23 09:41:02,763 [main] INFO  Exaprotect version: 3.1.0 (build 17478-213-1161)
2009-02-23 09:41:02,766 [main] INFO  Proc: 4 Mem: xxxMB/981MB/981MB
2009-02-23 09:41:03,075 [main] INFO  EventManager Context - config : InstanceName = TEST
2009-02-23 09:41:03,075 [main] INFO  EventManager Context - config : useGenerator = false
2009-02-23 09:41:03,075 [main] INFO  EventManager Context - config : generatorRateEPM = 0
2009-02-23 09:41:03,075 [main] INFO  EventManager Context - config : simplestEES = false
2009-02-23 09:41:03,156 [main] INFO  Creating 8 data inserter with queue length = 350
2009-02-23 09:41:03,299 [main] INFO  Max number of alerts in an incident : 100000
2009-02-23 09:41:03,299 [main] INFO  use.script!=YES in /home/exaprotect/conf/TEST/exa_incident.properties => No script execution allowed during creation of incidents
2009-02-23 09:41:09,079 [Maintain Process] INFO  Begin Maintenance Process
2009-02-23 09:41:09,093 [Maintain Process] INFO  End Maintenance Process

To fix this problem you have to delete all the corrupted files with the command:

rm -rf /var/lib/exaprotect/spool/MY_INSTANCE_NAME/ExaReceiver/all/*

and restart the runtime:

/etc/init.d/exa_runtime_MY_INSTANCE_NAME restart

This is fixed in SEM 3.2.0.