Look in the SISIPSService.log located in the scsplog folder for more info. This log deals with the service/engine of SCSP.
If it is not apparent, then run "sisipsconfig -trace" from a command line to enable verbose debugging and reproduce the issue. If then you still cannot see what caused the issue, pull a Collect Agent Info with the verbose debug option logs and open a support case.