Have a look in the work directory. Does the dispatcher even attempt to start the work processes? Files with naming convention dev_w* should exist if it does. Do these files contain any error messages? The error messages are normally very descriptive. Common startup problems are related to SAP being unable to connect to the database or being unable to allocate a sufficient amount of memory. Typos in the instance profiles are also often the reason of start-up failures.
Dig Deeper on SAP ABAP
Related Q&A from Bert Vanstechelman
An SAP user wants to know the risks of changing time zones in ECC 6.0. Continue Reading
An SAP user wants to know how to access an SAP IDES 4.7 system via the Internet through SAP GUI. Continue Reading
A SearchSAP.com reader wants to know how an increase of indexes and tables after upgrade to SAP ECC 6.0 will affect the memory requirements of a DB2 ... Continue Reading