Listeners or Services Could Not be Started Errors

Problem: After installation, Listener could not be started, or Service could not be started messages appear.

Explanation: This may indicate your SAP Mobile Platform configuration includes duplicate port numbers. This can happen for a variety of reasons; for example, if an application or service is offline during the installation process, the installer does not detect the reserved port number.

Solution: Change the SAP Mobile Platform component port numbers as needed post-installation, using information in Port Number Reference.

• SAP Control Center Could Not be Started
  Problem: After installation, SAP Control Center could not be started. The agent bootstrap thread logs error messages in agent.log such as the ones below. In case of a port conflict on the RMI agent port (default 9999) or the Repository DB port (default 3638), the SAP Control Center service startup fails.
• Port Number Reference
  Change SAP Mobile Platform component port numbers after installation, if necessary.