Dear all,
this could be related to different actions - and most likely the Spectrum Control Panel runs in context of a "root" account - which should be not - please use the CA Spectrum install owner account ( see $SPECROOT/UI-CONFIG.<hostname> --> owner).
Next is, which can also potentailly cause sub-sequent issues - that the SpectroSERVER was started directly and most likely per "root" account from a shell. This can cause file-permission problems when by next action try to start the SpectroSERVER via SCP with Spectrum-install owner as "some files" are now owned by "root" (and depending on the umask default settings that could cause a conflict).
Finally - if you "tar"/copy/restore the "SpectroSERVER" executable this could case the "s-bit" is lost then. (SUID functionality used by SpectroSERVER). So please check the SpectroSERVER file/executable settings.
There should be only 1 file in the $SPECROOT/SS directory owned by "root" (maybe a second debug file .. but none else):
[specadmin@labspec03 SS]$ ls -la | grep "root"
-rw-rw----. 1 root specadmin 0 Dec 21 16:44 .moot.trace
-rwsr-x---. 1 root specadmin 14040 Dec 21 16:18 SpectroSERVER
Please ensure to check this first - and then make use of a Spectrum-Install owner logon to start the SCP - or starting the SpectroSERVER via cmd-line per $SPECROOT/bin/startSS.pl
hth, Joerg