CA Spectrum Process Daemon (processd) service on Windows does not work correctly anymore which is then causing all Spectrum subservices managed the processd are not starting
Background here is the implementation that CA Spectrum Process Daemon will launch the sub-service per context of Install-owner (run process as user ) and not under the processd service account (which is per default Local System Account). This ensures the Spectrum services are all under effective user "Spectrum install owner".
The implementation for CA Spectrum Process Daemon to launch the sub-service per context of Install-owner (run process as user ) requires the saved "user context" is valid. This user-context, here for the Spectrum Install owner credentials (username and password) is saved at time of install. Subsequent user-credential change - here the account password - is not passed into CA Spectrum Process Daemon context. So the Spectrum logic to launch the sub-services will make use of out-dated credential set which then causes the sub-services not starting. (in practice the SID is saved at time of install - there is no option to find/edit the username and password within the Spectrum install files).
CA Spectrum Process Daemon logfile $SPECROOT/lib/SDPM/processd_log will cover runtime details (and exception messages).
In case the "Spectrum install owner" password expires, the CA Spectrum Process Daemon cannot start the Spectrum subservices anymore (under context of "run process as user") which is then reported to the processd_log file.