Has anyone else had problems with the SIA (Server Intelligence Agent) not automatically starting after a system reboot? Everytime we reboot the servers the SIA does not auto-start and I have to go start it manually. It’s a pain.
Haven’t faced this issue - but have seen that SIA is not able to start up the CMS and other services.
Monitored the serverpids directory - and saw that the CMS pid was not created. No errors in logs either.
Restarting the SIA solved it.
This is a start - I have a bigger issue with modifying CMS properties which end up changed in the “port” of the CMS! - I’ll have a new post on that - not sure if this is fixed in SP1 or SP2. Mine is a XI 3.1 installation without any patches applied.
Also, check (if installed on Windows) if the SIA services has any dependencies. Then could it be that those dependencies have not properly strated, causing the SIA to not start either. Maybe removing the dependency (but use that with caution) could fix the issue.
To Zach’s question, yes the SIA service is set to start automatically. Good suggestion on checking dependencies. The SIA is dependent on the following services:
Event Log
Remote Procedure Call
TCP/IP protocol driver
I’ll check my logs and see if one of these is causing a problem.