Starting the Configuration Manager

This topic contains advice for dealing with some common problems that can arise when you start resources:

A migrated Configuration Manager does not start

When the Configuration Manager has started successfully, the following event messages appear in the system's local error log with the source identifer WebSphere Broker v6000: 2001, 1223, 1224, 1228, 8255, 8280, and 1003.

If the error log still contains the original six event identifiers repeatedly (2001, 1223, 1224, 1228, 1205, and 1007), repeat steps 1 to 3, increasing the value that is assigned to the APP_CTL_HEAP_SZ parameter.

Error messages BIP1708 and BIP8283 are issued when you start a Configuration Manager on Windows

Related concepts
Brokers
Broker domains