Craig Knighton | I just resolved a similar issue - it turned out that the problem was that the phone was not able to reliably download the MIDlet over the URL that was provided. I assume that you are seeing the MIDlet listed on your SERVICES screen but that this error happens when you try to launch it. I suspect that if you look at your web server logs for the web server that is hosting the URL where the JAD/JAR are located you will see that the phone is never reaching the server or that if it is the connection is failing before the entire JAD or JAR is downloaded. I had both problems happening and needed to relocate closer to the access point to get a reliable connection. You can get more information about what is happening by connecting to the web server on the phone from a browser and elevating the trace settings on that phone to record full debug for all Java messages. If you do this you should be able to see the messages around the attempt to retrieve the JAD and JAR and if that process is failing. The steps for allowing access to the admin console on the phone are in the Admin guide for the phone. |
| Please sign in to flag this as inappropriate. |