|
String
|
Default Message
|
Cause/Solution
|
|---|
None
|
Access Control Error
|
The current card attempted to illegally link to a deck for which access control is enabled. A common cause for this error is trying to navigate to a deck in a different domain. By default, the domain of a specified URL must match the domain of the calling URL.
Note that the UP.Browser performs a literal string match between the domains of the requestingand target decks--it does not resolve names or aliases into canonical domain names. For example, if your deck has the domain 204.163.167.193, a deck in the domain devgate2.uplanet.com will not have access to your deck, even if devgate2.uplanet.com is an alias for 204.163.167.193.
You can change the access rules for a deck using the <ACCESS> element. For more information, see the UP.SDK Developer's Guide.
|
None
|
HTTP Reply failed
|
The HTTP request from the device failed. This error can result from failure to open a connection, or failure to read, write, or parse the request header information.
|
1002strings
|
Digest is too large
for device
|
The service sent a digest that was larger than 1460 bytes after the UP.Link server compiled it.
|
1010strings
|
Service read error
|
The customer is attempting to access a service that is returning bad data; the UP.Link server is rejecting the data that is being sent from the service. This message is caused by the inability of the UPLAgent to handle the returned WML data sent by the server. There are a large number of possible reasons for this, most of which are covered by the transaction log or system log.
|
1011strings
|
Service write error
|
The subscriber is attempting to access a service that is not providing an HTTP "write" connection. In other words, the UP.Link server cannot send data to the service.
|
1012strings
|
Cannot connect to
service
|
The service may no longer be available at the specified URL or it was too slow and timed out.
|
1013strings
|
Invalid URL
|
The specified URL is invalid (i.e. does not follow URL conventions).
|
1014strings
|
Bad HTTP status
|
The service returned an invalid HTTP status header
|
1015strings
|
Invalid content type
|
The service has provided a content type that the UP.Link server does not accept.
|
1018strings
|
Invalid notify type
from messenger
|
The service specified a notification type other than Alert or Prefetch.
|
1019strings
|
Compile Error
|
The WML returned by the service could not be compiled.
|
1020strings
|
Invalid HTTP
response
|
The service did not return a valid HTTP response.
|
1022strings
|
Invalid redirect
format
|
The Web server hosting a service replied with a redirect that was improperly constructed.
|
1023strings
|
Invalid auth
challenge type
|
The Web server hosting a service sent an invalid authentication challenge.
|
1025strings
|
Infinite redirect
loop
|
The Web server hosting a service is in an infinite redirect loop.
|
1026strings
|
Infinite
authentication loop
|
The Web server hosting a service is in an infinite redirect loop.
|
1027strings
|
URL is too large for
packet
|
The service has sent a URL larger than 1460 bytes.
|
1044strings
|
HTTP response limit
exceeded
|
The service has returned an HTTP response that exceeds the limit configured for the UP.Link server.
|
4000strings
|
Invalid fax content
|
The service has sent a fax with content that the Fax Manager did not understand.
|
4001strings
|
Invalid fax content
|
The service has sent fax content whose mime container was not a multipart message. The actual content must be preceded by a remote_printing element.
|
4002strings
|
Invalid fax content
|
The service has sent fax content whose mime container was a multipart message but had only 1 subpart. There must be a minimum of 2 subparts. The remote_printing subpart and the data subpart.
|
4003strings
|
Invalid fax number
|
The fax number supplied is less than 10 digits or is greater than 11 digits.
|
4004strings
|
Maximum fax size
exceeded
|
The fax that was sent was larger than the Fax Manager will allow. If this is an issue, the fax limit must be raised and the Fax Manager restarted.
|
4100strings
|
Unsupported content
type
|
The application returns something that the UP.Phone or UP.Link cannot accomodate (e.g. a JPEG image).
|
4101strings
|
Internal fax error
|
The FaxManager encountered a serious error.
|
4102strings
|
Internal fax error
|
4103strings
|
Internal fax error
|