When Harvest broker fails to start Harvest server processes, then server log file needs to be examined for detailed information regarding why the server failed to start.
Harvest broker and server are two separated processes. By default, when broker starts, the broker daemon process will try to start a number of harvest server processes. If the Harvest server process can not be started for some reason, the broker will emit "ERROR: Starting server".
At this point, the Harvest administrator should check the Harvest server logs for the exact error that causes the server processes to fail. In order to gather more information in hserver log, we need to restart the broker with following recommended entries in HARVESTHOMEHOME\HServer.arg;
-trace -sqlout -logging=5
For Harvest 7.1, by default, the Harvest server logs are written to %HARVESTHOME%\log for all platform.
For CA SCM R12.0, the server logs on UNIX and Linux are under $CA_SCM_HOME/log. While in Windows, the server logs are written to %USERPROFILE%\.casm\log, except if broker is started as service logged on as system then log is created in %CA_SCM_HOME%\log.