Problem: This message may indicate that an Unwired Server administrative component is not running.
If users report problems synchronizing from the client, check for this error message in the Sybase Control Center agent.log file:
2009-11-10 17:19:51,718 [ERROR] [btpool1-4] com.sybase.scc.jmx.ManagedObjectGateway.invoke(?) - Failed to invoke managed object '82061EE7A2D141E391B46D245EAF0B1E' mbean operation searchDeviceList2([java.lang.String]): com.sybase.uep.sysadmin.management.mo.exception.SUPArtifactMOException: com.sybase.uep.sysadmin.management.mbean.UEPAdminException: com.sybase.uep.admin.client.AdminException: ADMIN_WEBSERVICE_INVOCATION_ERROR:java.security.PrivilegedActionException: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed javax.management.MBeanException:
Explanation: There are two possible reasons – the service could not be started due to a service account credential issue, or there is a conflict on the currently configured port for the administration web service.
If you install Sybase Unwired Platform with a domain account with administrator rights, and subsequently change the password, or use a domain account that does not have administrator rights, the Sybase Messaging Service will not start. One way to verify this is by accessing the following URL from the host where Sybase Unwired Platform is installed: http://localhost:5100/MobileOffice/Admin.asmx. The default Messaging Service port is 5100, but this may vary depending on your configuration.
Solution 2: Make sure the administration Web service is up and running, and correctly configured. Review Troubleshooting > Troubleshoot the System > Troubleshoot the Installation > Cannot Access Devices Tab and Web Service Error topic on how to configure the port in case of conflict on existing port.