Problems, such as Unwired Server or RSOE failing to start, are encountered without any obvious error messages.
Explanation 1: This may occur if the Unwired Server host machine is running intrusion detection software, such as the McAfee Host Intrusion Prevention service. This may cause a connection from the consolidated database (CDB) to the Unwired Server node to be flagged as an attack, and the CDB host to be added to the list of blocked hosts, preventing communication between Unwired Server and the CDB. The Unwired Server log reports connectivity problems with the CDB, and start-up failure problems similar to:
YYYY-MM-DD HH:MM:SS.SSS ERROR MMS Thread-55 [com.sybase.djc.log.SystemExceptionLog] com.sybase.djc.DataStoreException was thrown by method com.sybase.djc.server.PartitionLock.updateLock(boolean)\ncom.sybase.djc.DataStoreException: Connection Failed: java.sql.SQLException: JZ006: Caught IOException: java.net.SocketException: Software caused connection abort: connect ...
Workaround 1: You may want to set up some exclusion rules to allow the required communication between the CDB and Unwired Server nodes. Use the following information to formulate exclusion rules; rules may vary depending on the intrusion detection software used.
Explanation 2: If .NET is present when Unwired Platform is installed, and the .NET installation is corrupt, the Unwired Platform installer does not detect the problem, leaves the corrupt .NET in place and Unwired Server does not start.
Workaround 2: Uninstall both Unwired Platform and .NET, then reinstall Unwired Platform, letting the Unwired Platform installer install .NET.