Look in the Windows Event Viewer application logs to see if any errors exist. Another option would be to enable the SIA trace from the CCM. If you double click on the SIA when its stopped, you can add a -trace to the command line to enable the trace. The logs may give you a better idea of why its not starting. One main cause can beIf the port is in use for the SIA, usually 6410. If its in use, then it won't be able to start.
↧