ACTSYNC_NO_PORT

ActiveSync synchronization can only be initiated by ActiveSync itself, either by placing the device in its cradle or by selecting "Synchronize" from the ActiveSync Manager. To initiate a synchronization from an application, use the TCP/IP socket synchronization stream.

ACTSYNC_NOT_INSTALLED

The ActiveSync provider has not been installed. Run dbasinst to install it (see documentation for details).

CONNECT_TIMEOUT

The connection attempt timed out. Either the server is not running on the indicated host and port or the timeout value needs to increased to allow more time to connect.

COULD_NOT_OPEN_FILE_FOR_WRITE

The specified file could not be opened for write. Make sure that this is the correct file and that no other application is using it.

CREATE_RANDOM_OBJECT

The secure network layer could not create a random-number-generating object. Free up system resources, reconnect and retry the operation.

DEQUEUING_CONNECTION

The MobiLink server encountered an error while attempting to get a queued connection (synchronization) request. Free up system resources. If the problem persists, restart the MobiLink server.

DUN_DIAL_FAILED

Automatic dialup failed to establish connection to the specified dial up network.

DUN_NOT_SUPPORTED

An attempt to dialup has failed due to insufficient system support. On PocketPC you must use cellcore.dll and on Windows you must use wininet.dll from IE 4.0 or above. Dialup is not supported on other platforms.

END_READ

Unable to finish a sequence of reads from the network. See also: READ

END_WRITE

Unable to finish a sequence of writes to the network. See also: WRITE

GENERATE_RANDOM

The secure network layer requires a random number but was unable to generate one. Free up system resources, reconnect and retry the operation.

HTTP_AUTHENTICATION_FAILED

The supplied userid and password were rejected. Check that they were entered correctly. If so, contact your systems administrator to ensure you have proper access.

HTTP_AUTHENTICATION_REQUIRED

An HTTP server or gateway requested HTTP authentication. Please supply a userid and password using the HTTP synchronization parameters http_userid and http_password.

HTTP_BAD_STATUS_CODE

Examine the status line to determine the cause of the failure.

HTTP_BUFFER_SIZE_OUT_OF_RANGE

Fix the HTTP buffer size. A valid buffer size is positive and not overly large for the host platform.

HTTP_CHUNK_LEN_BAD_CHARACTER

Try using a fixed length HTTP body.

HTTP_CHUNK_LEN_ENCODED_MISSING

Try using a fixed length HTTP body.

HTTP_CLIENT_ID_NOT_SET

The client id was not passed into the HTTP client code. Contact technical support for a fix.

HTTP_CONTENT_TYPE_NOT_SPECIFIED

An unknown content type was specified. Refer to the documentation and change the content type to one of the supported types.

HTTP_CRLF_ENCODED_MISSING

The proxy you are using may not be compatible with MobiLink. Please check your configuration.

HTTP_CRLF_MISSING

The proxy you are using may not be compatible with MobiLink. Please check your configuration.

HTTP_EXPECTED_POST

The proxy you are using may not be compatible with MobiLink. Please check your configuration.

HTTP_EXTRA_DATA_END_READ

Extra data has been introduced into the HTTP body. This may have been added by a proxy agent. Try eliminating the proxy.

HTTP_HEADER_PARSE_ERROR

An error occurred while trying to parse an HTTP header. The header may be malformed.

HTTP_INTERNAL_HEADER_STATE

There was a problem decoding the HTTP header. This is an internal error that should never occur. Please contact technical support.

HTTP_INTERNAL_REQUEST_TYPE

There was a problem determining the HTTP request type. This is an internal error that should never occur. Please contact technical support.

HTTP_INVALID_CHARACTER

An unexpected character was read in an HTTP header. The header may be malformed or the other side may not be sending HTTP at all.

HTTP_INVALID_SESSION_KEY

An unknown session key type was specified. Refer to the documentation and change the session key type to one of the supported types.

HTTP_MALFORMED_SESSION_COOKIE

The HTTP cookie used to manage the synchronization session is corrupt. Determine where the cookie is being corrupted. The most likely cause is a client error, or perhaps an HTTP intermediary misbehaving,

HTTP_NO_CONTD_CONNECTION

The server timed out while waiting for the next HTTP request from the remote site. Determine why this request failed to reach the server or try a persistent connection.

HTTP_NO_PASSWORD

A userid was supplied for HTTP authentication but no password. Both are required for authentication.

HTTP_NO_USERID

A password was supplied for HTTP authentication but no userid. Both are required for authentication.

HTTP_PROXY_AUTHENTICATION_FAILED

The supplied userid and password were rejected by the proxy server. Check that they were entered correctly. If so, contact your systems administrator to ensure you have proper access.

HTTP_PROXY_AUTHENTICATION_REQUIRED

An HTTP proxy requested HTTP authentication. Please supply a userid and password using the HTTP synchronization parameters http_proxy_userid and http_proxy_password.

HTTP_SERVER_AUTH_FAILED

The Authentication-Info header sent from the server contained an incorrect value, causing authentication to fail. Make sure that you are connecting to a legitimate HTTP server.

HTTP_UNABLE_TO_PARSE_COOKIE

Determine where the set cookie header is being corrupted.

HTTP_UNKNOWN_TRANSFER_ENCODING

Determine how the unknown transfer encoding is getting generated.

HTTP_UNSUPPORTED_AUTH_ALGORITHM

The HTTP Digest authentication algorithm requested by the server is unsupported. Only "MD5" and "MD5-sess" are supported.

HTTP_VERSION

The requested HTTP version is unsupported. Consult the documentation and specify a supported HTTP version. At the time of publication the supported HTTP versions are 1.0 and 1.1.

INCONSISTENT_FIPS

Use of the -fips switch on the MobiLink server command line requires that all secure streams be FIPS-compliant. If a secure stream is not configured with the fips option, it will automatically be FIPS-complient (for example, fips=y). Either remove the fips option from the secure stream, or enable it with fips=y.

INIT_RANDOM

The secure network layer could not initialize its random number generator. Free up system resources, reconnect and retry the operation.

INTERNAL

An internal error has occurred in the network layer. Please contact technical support.

INTERNAL_API

An internal error has occurred in the network layer. Please contact technical support.

INTERNAL_PROTOCOL_NOT_LOADED

A synchronization protocol could not be loaded. If you are using UltraLite, make sure you have called the proper ULEnable method.

INTERRUPTED

The current operation was interrupted by the caller.

INVALID_COMPRESSION_TYPE

The specified compression type was not recognized.

INVALID_LOCAL_PATH

The local path for the downloaded file is invalid. Consult the documentation for details.

INVALID_NETWORK_LIBRARY

The given network interface DLL or shared object could not be loaded, possibly because it is invalid or corrupt.

INVALID_SYNC_PROTOCOL

The specified protocol is not a valid synchronization protocol.

LIBRARY_ENTRY_POINT_NOT_FOUND

The indicated library entry point could not be found.

LOAD_LIBRARY_FAILURE

The indicated library could not be found in the path. If you are trying to use TLS encryption for synchronization, make sure you have acquired the proper license.

LOAD_NETWORK_LIBRARY

The network interface library could not be found and/or loaded. Please check the following:

1) The sockets layer is properly installed. The correct network interface library (or DLL or shared object) must be present and accessible.

2) There are enough system resources available. Free up system resources if they are running low.

MEMORY_ALLOCATION

The network layer was unable to allocate enough bytes of storage. Free up system memory and retry the operation. The technique used to free up system memory depends on the operating system and how it is configured. The simplest technique is to reduce the number of active processes. Consult your operating system documentation for details.

MISSING_PARAMETER

The specified parameter was expected but not supplied.

NETWORK_LIBRARY_VERSION_MISMATCH

A network interface DLL or shared object could not be loaded because it is the wrong version.

NO_ECC_FIPS

There was a problem performing the given compression operation. Please contact technical support.

NONE

This code indicates there was either no network error, or an unknown network error occurred.

NOT_IMPLEMENTED

An unimplemented internal feature was requested. Please contact technical support.

PARAMETER

Network parameters are of the form "name=value;[name2=value2[;...]]". This code indicates an invalid parameter value. Consult the documentation for the corresponding parameter name, and correct the parameter value.

PARAMETER_NOT_BOOLEAN

Network parameters are of the form "name=value;[name2=value2[;...]]". The parameter value is not a boolean value. Locate the offending parameter specification and change the value of the parameter to either 0 (for off or false) or 1 (for on or true).

PARAMETER_NOT_HEX

Network parameters are of the form "name=value;[name2=value2[;...]]". The parameter value is not a hexadecimal (base 16) value. Locate the offending parameter specification and change the value of the parameter to a hexadecimal value.

PARAMETER_NOT_UINT32

Network parameters are of the form "name=value;[name2=value2[;...]]". The parameter value is not an unsigned integer. Locate the offending parameter specification and change the value of the parameter to an unsigned integer.

PARAMETER_NOT_UINT32_RANGE

Network parameters are of the form "name=value;[name2=value2[;...]]". The parameter value is not an unsigned integer value or range. Locate the offending parameter specification and change the value of the parameter to an unsigned integer or an unsigned range. An unsigned range has the form: NNN-NNN.

PARSE

Network parameters are of the form "name=value;[name2=value2[;...]]". Optionally, the entire list of parameters may be enclosed in parentheses. The given string does not follow this convention. Inspect the string, fix any formatting problems, and retry the operation.

PROTOCOL_ERROR

An unexpected value or token was read.

READ

Unable to read the given number of bytes from the network layer. Note that reads may occur as part of any larger network operation. For example, some network layers have sub-layers that perform several reads and writes as part of a basic operation in the upper layer. The cause of a read error is usually one of the following:

1) The network had a problem that caused the read to fail. Reconnect and retry the operation.

2) The connection timed out. Reconnect and retry the operation.

3) The other side of the connection cleanly terminated the connection. Consult the client and/or server logs for errors that indicate why the connection has been dropped. Consult the output-log errors and fix the cause, then retry the operation.

4) The process at the other side of the connection was aborted. Consult the client and/or server output logs for errors that indicate why the process was aborted. If the process was shut down by other than normal means, there may not be any errors in its output log. Reconnect and retry the operation.

5) The system is low on resources, and cannot perform the read. Free up system resources, reconnect and retry the operation. If subsequent retry attempts fail, consult your network administrator.

READ_TIMEOUT

Unable to read the given number of bytes from the network layer in the given time. Check that the network is functioning correctly, and that the sending application is still running.

SACI_ERROR_CLIENT

An error has been reported by the SACI implementation.

SACI_ERROR_SERVER

The SACI network library is reporting an error. Refer to the provider of the SACI network library to resolve the problem.

SECURE_ADD_CERTIFICATE

The secure network layer was unable to add a certificate to a certificate chain. Free up system resources and retry the operation.

SECURE_ADD_TRUSTED_CERTIFICATE

The secure network layer was unable to add a trusted certificate to a certificate chain. The most likely cause is a shortage of system resources. Free up system resources and retry the operation.

SECURE_CERTIFICATE_COMMON_NAME

The given common name is not in the certificate chain. Check the following:

1) The common name was properly entered.

2) The correct certificate file was specified.

3) The common name is in the certificate chain. You can verify this with the readcert utility.

SECURE_CERTIFICATE_COMPANY_NAME

The given organization name is not in the certificate chain. Check the following:

1) The organization name was properly entered.

2) The correct certificate file was specified.

3) The organization name is in the certificate chain. You can verify this with the readcert utility.

SECURE_CERTIFICATE_COMPANY_UNIT

The given organization unit is not in the certificate chain. Check the following:

1) The in company name was properly entered.

2) The correct certificate file was specified.

3) The company name is in the certificate chain. You can verify this with the readcert utility.

SECURE_CERTIFICATE_COUNT

The given file does not contain a certificate. Check the following:

1) The certificate file name was properly specified.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

SECURE_CERTIFICATE_EXPIRED

A certificate in the certificate chain has expired. Obtain a new certificate with a later expiry date and retry the operation.

SECURE_CERTIFICATE_EXPIRY_DATE

A certificate's expiry date could not be read. Check the following:

1) The password was entered correctly.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

4) The certificate file is undamaged.

SECURE_CERTIFICATE_FILE_NOT_FOUND

The certificate file could not be opened. Check the following:

1) The certificate file name was properly specified.

2) The certificate file exists.

3) The certificate file contains one or more certificates.

4) The certificate file contains the correct certificate(s).

5) The program attempting to open the certificate file has sufficient privileges to read the file. This only applies to operating systems having user and/or file permissions.

SECURE_CERTIFICATE_NOT_TRUSTED

The server's certificate was not signed by a trusted authority. Check the following:

1) The certificate file name was properly specified.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

4) The client's list of trusted root certificates includes the server's root certificate.

SECURE_CERTIFICATE_ROOT

The root certificate in the chain is invalid. At the time of publication, this error was defined but not used.

SECURE_CREATE_CERTIFICATE

The secure network layer was unable to allocate storage for a certificate. Free up system resources and retry the operation.

SECURE_CREATE_PRIVATE_KEY_OBJECT

The secure network layer was unable to create a private key object, prior to loading the private key. The most likely cause is a shortage of system resources. Free up system resources and retry the operation.

SECURE_DUPLICATE_CONTEXT

The secure network layer was unable to duplicate a security context. Free up system resources and retry the operation.

SECURE_EXPORT_CERTIFICATE

The secure network layer was unable to copy a certificate. Free up system resources and retry the operation.

SECURE_HANDSHAKE

The secure handshake failed. Check the following:

1) On the client, the correct host machine and port number were specified.

2) On the server, the correct port number was specified.

3) The correct certificate file was specified, both on the client and on the server.

SECURE_IMPORT_CERT_FROM_SYSTEM_STORE

Failed to import a certificate from the system certificate store.

SECURE_IMPORT_CERTIFICATE

The secure network layer was unable to import a certificate. Check the following:

1) The certificate file name was properly specified.

2) The certificate file exists.

3) The certificate file contains one or more certificates.

4) The certificate file contains the correct certificate(s).

SECURE_NO_CERTS_IN_SYS_STORE

No certificates were found in the system's certificate store.

SECURE_NO_SERVER_CERTIFICATE

No server certificate was provided. A server certificate is required for secure communications. The file provided must contain the full chain of certificates for the server as well as its private key.

SECURE_NO_SERVER_CERTIFICATE_PASSWORD

No server certificate password was provided. This password is required to decrypt the server's encrypted private key.

SECURE_NO_TRUSTED_ROOTS

No trusted root certificates were provided. At least one trusted root certificate is required for secure communications.

SECURE_OPEN_SYSTEM_CERT_STORE

An attempt to open a system certificate store failed.

SECURE_READ_CERTIFICATE

The certificate file could not be read. Check the following:

1) The password was entered correctly.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

4) The certificate file is undamaged.

SECURE_READ_PRIVATE_KEY

The private key could not be read from the certificate file. Check the following:

1) The password was entered correctly.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

4) The certificate file is undamaged.

SECURE_REDUNDANT_SERVER_CERTIFICATE_PASSWORD

A password was specified when the server's private key wasn't encrypted by any password.

SECURE_SET_IO

The secure network layer was unable to attach to the network layer. Free up system resources and retry the operation.

SECURE_SET_PRIVATE_KEY

The private key could not be used. Check the following:

1) The password was entered correctly.

2) The certificate file contains one or more certificates.

3) The certificate file contains the correct certificate(s).

4) The certificate file is undamaged.

SECURE_TRUSTED_CERTIFICATE_FILE_NOT_FOUND

The certificate file could not be found. Check the following:

1) The certificate file name was properly specified.

2) The certificate file exists.

3) The certificate file contains one or more certificates.

4) The certificate file contains the correct certificate(s).

5) The program attempting to open the certificate file has sufficient privileges to see the file. This only applies to operating systems having user and/or file permissions.

SECURE_TRUSTED_CERTIFICATE_READ

The secure network layer was unable to read the trusted certificate file. Check the following:

1) The certificate file name was properly specified.

2) The certificate file exists.

3) The certificate file contains one or more certificates.

4) The certificate file contains the correct certificate(s).

5) The program attempting to open the certificate file has sufficient privileges to see the file. This only applies to operating systems having user and/or file permissions.

SEED_RANDOM

The secure network layer could not seed its random number generator. Free up system resources, reconnect and retry the operation.

SERVER_ERROR

The server reported an error. Contact the MobiLink administrator to learn more.

SHUTTING_DOWN

The MobiLink server encountered an error in the network layer during shutdown. It is possible that some network operations pending at the time of shutdown were affected.

SOCKET_BIND

The network layer was unable to bind a socket to the given port. Check the following.

1) (Server only) Verify that the port isn't already in use. If the port is in use, either shut down the application listening on that port, or specify a different port.

2) (Server only) Verify that there are no firewall restrictions on the use of the port.

3) (Client only) If the client_port option was used, verify that the given port isn't already in use. If only one client port was specified, consider using a range (for example, NNN-NNN). If a range was specified, consider making it a wider range, or a different range.

4) (Client only) If the client_port option was used, verify that there are no firewall restrictions on the use of the port.

SOCKET_CLEANUP

The network layer was unable to clean up the socket layer. This error should only occur after all connections are finished, so no current connections should be affected.

SOCKET_CLOSE

The network layer was unable to close a socket. The network session may or may not have terminated prematurely, due to pending writes that were not flushed. Check the following:

1) The other side of the network connection had any errors.

2) The other side of the connection is running normally.

3) The machine is still connected to the network, and the network is responsive.

SOCKET_CONNECT

The network layer was unable to connect a socket. Check the following:

1) The machine is connected to the network.

2) The socket layer is properly initialized.

3) The correct host machine and port were specified.

4) The host server is running normally and listening on the correct port.

5) The host machine is listening for the proper socket type (TCP/IP vs. UDP).

6) If the client_port option was used, verify that there are no firewall restrictions on the use of the port.

7) If the device has a limit on the number of open sockets, verify that the limit has not been reached.

8) There are enough system resources available. Free up system resources if they are running low.

SOCKET_CREATE_TCPIP

The network layer was unable to create a TCP/IP socket. Check the following:

1) The machine is connected to the network.

2) The socket layer is properly initialized.

5) If the device has a limit on the number of open sockets, verify that the limit has not been reached.

6) There are enough system resources available. Free up system resources if they are running low.

SOCKET_CREATE_UDP

The network layer was unable to create a UDP socket. Check the following:

1) The machine is connected to the network.

2) The socket layer is properly initialized.

3) If the client_port option was used, verify that the given port isn't already in use. If only one client port was specified, consider using a range (for example, NNN-NNN). If a range was specified, consider making it a wider range, or a different range.

4) If the client_port option was used, verify that there are no firewall restrictions on the use of the port.

5) If the device has a limit on the number of open sockets, verify that the limit has not been reached.

6) There are enough system resources available. Free up system resources if they are running low.

SOCKET_GET_HOST_BY_ADDR

The network layer was unable to get the name of a host using its IP address. At the time of publication, this error was defined but not used.

SOCKET_GET_NAME

The network layer was unable to determine a socket's local name. In a TCP/IP connection, each end of the connection has a socket exclusively attached to a port. A socket's local name includes this port number, which is assigned by the network at connection time. Check the following:

1) The machine is still connected to the network, and the network is responsive.

2) The other side of the connection is running normally.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_GET_OPTION

The network layer was unable to get a socket option. This error may be the first indication that a connection has been lost. Check the following:

1) The machine is still connected to the network, and the network is responsive.

2) The other side of the connection is running normally.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_HOST_NAME_NOT_FOUND

The given host name could not be found. Check the following:

1) The host name was correctly specified.

2) The host is accessible. Many systems include a "ping" utility that can be used to verify access to a named host.

3) The Domain Name Server (DNS), or its equivalent, is available. If the DNS is not available, try specifying the host's IP number (for example, NNN.NNN.NNN.NNN) instead of the host name.

4) The HOSTS file contains an entry that maps the host name to an IP number.

SOCKET_LISTEN

The server is unable to listen on a socket. The backlog refers to the maximum number of queued connection requests that may be pending at any given time. Check the following:

1) The machine is still connected to the network, and the network is responsive.

2) There are no firewall or other restrictions preventing a socket listener from running on the current machine.

3) The backlog setting is within the limit, if any, on the machine.

4) There are enough system resources available. Free up system resources if they are running low.

SOCKET_LIVENESS_OUT_OF_RANGE

An invalid liveness timeout value was specified. The liveness timeout value must be an integer between zero and 65535.

SOCKET_LOCALHOST_NAME_NOT_FOUND

The network layer was unable to determine the IP address of "localhost". Check the following:

1) The Domain Name Server (DNS), or its equivalent, is available. If the DNS is not available, try explicitly specifying the localhost IP number (usually 127.0.0.1) instead.

2) The HOSTS file contains an entry that maps the "localhost" name to an IP number.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_PORT_OUT_OF_RANGE

An invalid port number was specified. The port number must be an integer between zero and 65535.

SOCKET_SELECT

The network layer encountered an error attempting to wait for a socket to be ready for reading or writing. Check the following:

1) The machine is connected to the network, and the network is responsive.

2) The other side of the connection is running normally.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_SET_OPTION

The network layer was unable to set a socket option. This error may be the first indication that a connection has been lost. Check the following:

1) The machine is still connected to the network, and the network is responsive.

2) The other side of the connection is running normally.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_SHUTDOWN

The network layer was unable to shut down a socket. Check the following:

1) The machine is connected to the network, and the network is responsive.

2) The other side of the connection is running normally.

3) There are enough system resources available. Free up system resources if they are running low.

SOCKET_STARTUP

The network layer was unable to initialize the socket layer. Check the following:

1) The sockets layer is properly installed. The correct network interface library must be present and accessible.

2) The machine is connected to the network, and the network is responsive.

3) There are enough system resources available. Free up system resources if they are running low.

UNEXPECTED_HTTP_REQUEST_TYPE

The given HTTP request type was unexpected at this time. The most likely cause is an HTTP client that is not a MobiLink client.

UNRECOGNIZED_TLS_TYPE

The TLS type is invalid. Consult the documentation for valid types.

VALUE_OUT_OF_RANGE

The specified value was not in the range of acceptable values for that parameter. Check the documentation for the parameter to learn the acceptable range of values.

WOULD_BLOCK

A requested operation would block where blocking is undesirable or unexpected.

WRITE

Unable to write the given number of bytes to the network layer. Note that writes may occur as part of any larger network operation. For example, some network layers have sub-layers that perform several reads and writes as part of a basic operation in the upper layer. The cause of a write error is usually one of the following:

1) The network had a problem that caused the write to fail. Reconnect and retry the operation.

2) The connection timed out. Reconnect and retry the operation.

3) The other side of the connection cleanly terminated the connection. Consult the client and/or server logs for errors that indicate why the connection has been dropped. Consult the output-log errors and fix the cause, then retry the operation.

4) The process at the other side of the connection was aborted. Consult the client and/or server output logs for errors that indicate why the process was aborted. If the process was shut down by other than normal means, there may not be any errors in its output log. Reconnect and retry the operation.

5) The system is low on resources, and cannot perform the write. Free up system resources, reconnect and retry the operation. If subsequent retry attempts fail, consult your network administrator.

WRITE_TIMEOUT

Unable to write the given number of bytes to the network layer in the given time. Check that the network is functioning correctly, and that the receiving application is still running.