Provides troubleshooting information for postinstallation
configuration problems in SAP Mobile Platform.
Troubleshooting Host Name Problems
Problem: After installation, you determine that you need to change the host name (machine name); for example, the host name is too long, or includes reserved characters. Changing the host name is rarely done in a production system.
Handling Intrusion Detection/Prevention Software
A personal firewall, or intrusion detection/prevention software (IPS or IDPS), can cause SAP Mobile Platform components to malfunction or not function at all. SAP Mobile Platform uses regular IP communication between components on the primary network interface of a computer, even when all components are installed on the same host.
Cannot Access Device Tab and Web Service Error
Problem: After installation, you cannot access the Applications > Application Connections tab in SAP Control Center, and the SAP Mobile Server log shows an ADMIN_WEBSERVICE_INVOCATION_ERROR.
Cannot Access sampledb
After installation, you cannot access the sample database (sampledb).
System Environment Path is Too Long
Problem: When upgrading SAP Mobile Platform, you cannot start SAP Mobile Server using the start-unwired-server.bat batch file provided with an ESD.
.NET Environment Problems Affect SAP Mobile Server
Problem: When installing or upgrading SAP Mobile Server, certain .NET applications which are required by SAP Mobile Server, such as OBMO.exe, do not run.
Installer Hangs Starting Services after Upgrade
Problem: After upgrading a 2.2 SP04 cluster to 2.3 using the SAP Mobile Platform installer, then adding a new 2.3 server node into the upgraded cluster, the installer hangs while starting SAP Mobile Platform services.