Troubleshoot the Postinstallation Configuration

Provides troubleshooting information for postinstallation configuration problems in Sybase Unwired 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.
• Listeners or Services Could Not be Started Errors
  Problem: After installation, Listener could not be started, or Service could not be started messages appear.
• Sybase Unwired Server Service Fails to Restart After Credential Change
  Problem: The Sybase Unwired Server Service fails to restart after the person who installed Sybase Unwired Platform changes their login credentials.
• Handling Intrusion Detection/Prevention Software
  A personal firewall, or intrusion detection/prevention software (IPS or IDPS), can cause Unwired Platform components to malfunction or not function at all. Unwired 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 Sybase Control Center, and the Unwired Server log shows an ADMIN_WEBSERVICE_INVOCATION_ERROR.
• Cannot Access sampledb
  Problem: After installation, you cannot access the sample database (sampledb).
• System Environment Path is Too Long
  Problem: When upgrading Sybase Unwired Platform, you cannot start Unwired Server using the start-unwired-server.bat batch file provided with an ESD.
• [Deprecated in 2.3]Client Application Hangs Waiting for Authentication
  Problem: The client application hangs on the login screen, while waiting for authentication from Unwired Server. The application eventually times out and returns an authentication error: Failed to obtain ${licenseNumber}license(s) for SUP_BASECLIENT feature from License Server ${server_id}.
• Performance Issues if Unwired Server Not Installed on a 64-bit Machine
  Problem: You observe performance issues when a high volume of client activity (synchronizations or logins) occurs on an Unwired Server running on a 32-bit Windows machine.
• Unwired Server or RSOE Startup Problems
  Problem: Problems, such as Unwired Server or RSOE failing to start, are encountered without any obvious error messages.
• .NET Environment Problems Affect Unwired Server
  Problem: When installing or upgrading Unwired Server, certain .NET applications which are required by Unwired Server, such as OBMO.exe, do not run.
• Messaging Installer Completed With Errors
  Problem: When upgrading to a newer software level, you are informed of errors.