UP.Phone/UP.Simulator-related errors

Message	Cause/Solution
`Access Control Error`	See the entry for Access Control Error under Service-related errors.
`Bad WML: check Phone Information window`	The UP.Simulator has loaded a deck containing WML errors. To see the line numbers and descriptions of the WML errors, look in the Phone Information window. For more information on the Phone Information Window, see Phone Information messages.
`HTTP Error 404: Not found`	This error commonly occurs when you run the UP.Simulator in HTTP direct mode and attempt to use services available in UP.Link mode only (for example, bookmarks). When you run the UP.Simulator in HTTP direct mode, it communicates directly with your HTTP Web server and bypasses the UP.Link server completely. When you try to bookmark a card, the UP.Browser attempts to fetch a URL that resides on the UP.Link server. Since the server is not available when you run the UP.Simulator in HTTP direct mode, the URL request returns a `Not Found` error. To use functionality such as bookmarks, notifications, and faxing, you must register your UP.Simulator and run it in UP.Link mode (see UP.Link mode).
`Network not responding`	This error occurs if the UP.Simulator is unable to reach the UP.Link server. To resolve this error, see Network/Server not responding errors.
`Server not responding`	The network is working, but the UP.Link server is down. This might also occur if you have specified an invalid or nonexistent UP.Link server domain in the UP.Link Settings dialog box. Make sure the domain is correct. To resolve this error, see Network/Server not responding errors.
`Security is not enabled`	You need to enable secure communication between your UP.Phone and the UP.Link server. To enable security, press the `ACCEPT` key.
`Key exchange is disabled`	You attempted to enable security (do a key exchange), but the key exchange process was disabled on the UP.Link server or the UP.Simulator. This can occur if you have updated the UP.Simulator to a new version or attempted to use the same registered subscriber ID on different machines. To correct this problem, delete and then re-register the subscriber. For more information on deleting and registering subscribers, see Registering on an UP.Link server and Deleting a subscriber. If the error still occurs, try again later or contact the UP.Link server administrator.
`Bad key was generated, try again`	Try executing a key exchange again. For information on executing key exchanges, see the UP.Browser User Handbook.
`You must perform key exchange`	Do a key exchange (enable security).
`You must verify your key`	Call the UP.Link server administrator to verify your security key.
`UP.Link address is not set up`	The UP.Browser doesn't know the IP address of the UP.Link server you are using. Contact your wireless carrier.
`Cannot mark this location`	You attempted to bookmark a site or WML service that cannot be bookmarked.
`No help available here`	You attempted to get help (for example, by pressing the Help button) on a service for which no help is available.
`Unregistered device`	Your UP.Phone or UP.Simulator is not registered with the UP.Link server. To register the UP.Simulator, see UP.Link mode. To register a real UP.Phone, contact your wireless carrier.
`This device is disabled`	The UP.Phone has been disabled. Contact your wireless carrier.

Network/Server not responding errors

If the UP.Simulator displays a "Network not responding" or "Server not responding" message instead of the WML deck you requested, the UP.Phone was unable to connect to the Web server that provides the deck. This could be because you are not connected to the Internet, your site's firewall is preventing you from connecting, or the server is temporarily offline. Make sure you are properly connected to the Internet; for example, use the ping command to verify that you can access remote hosts on the Internet.

For example, to verify that the Unwired Planet Developer server is accessible and responding, type the following in an MS-DOS window:

The MS-DOS window should display the server's response--several lines starting with: "Reply from 204.163.167.193...". If you have verified that you can access other remote hosts, but updev.uplanet.com does not respond, the server may be temporarily offline. Try again later--if the problem persists, contact the server administrator (note that pinging the domain uplanet.com by itself does not work).

If you are able to ping the Unwired Planet Developer server but the UP.Simulator does not connect successfully, it could be because your network's firewall is preventing it from communicating with the UP.Link server or Web server. For UP.Simulator port requirements, see System requirements.