Hi @mian,
from this message I think this is a Brainstorm issue.
I couldn't reproduce it on my machine so it might be dataset specific.
Maybe @Francois can help you with it if you send him your dataset.
Hopefully it's not going to be too big.
The fact that one spike sorter detects spikes doesn't necessarily mean that the others will do as well.
There is a config file with a very big list of parameters to play with on each spike-sorter. The threshold for the spike-detection is a very important one, you should probably make sure that it is set properly.
More information regarding the spike-sorters can be found on their GitHub repository.
Just to make sure, since we encountered this in the past:
are your recordings from invasive, highly sampled electrodes (>=20kHz)?