If your broker won't start, or the bkrd process is there but no hserver processes, there could be several reasons for the problem. To gather more information you can start these two processes from the command line. Here's how:
1. If you're on Unix or Linux assure that you're logged in with the userid that owns CA SCM
2. Navigate to the %CA_SCM_HOME% ($CA_SCM_HOME) folder
3. Check your list of active processes (Task Manager for Windows, or ps -ef on Linux or Unix). Any processes named 'rtserver', 'bkrd' or 'hserver' should be shut down.
4. From a command prompt enter the following command
bkrd -minserver=0 -maxserver=0 -verbose
What this will do is start just the broker (no hservers) and route all messages to the console. If the bkrd process encounters an error, this is where you'll see it.
5. If the broker was able to start normally in the previous step, let it continue to run, open a second command prompt window, navigate to the %CA_SCM_HOME% ($CA_SCM_HOME) folder and enter the following command:
hserver -logging=5 -verbose
What this will do is start an hserver process and route all messages to the console. If the hserver process encounters an error, this is where you'll see it.
In the majority of cases, the hserver component is the one experiencing a problem.
If you need help from Support to solve the issue, make sure to capture any error messages you find and attach them to the issue.