Understanding Common Errors
This table lists common errors (and suggested solutions) that you might encounter when you use Microsoft® SQL Server™ 2000 Windows® CE Edition (SQL Server CE).
|Native error||Error numbers||Solution|
|28037||80072EFD||The user's device must have network connectivity. For example, the device might not have a working modem, network card, or universal serial bus (USB) connection.
Ensure that the computer running Microsoft Internet Information Services (IIS) is available, and that the ISP or network is functioning properly.
|28017||80004005||Ensure that the virtual directory is specified correctly. |
For example, the URL might be incorrectly listed as http://server/ssqlce/sscesa20.dll instead of http://server/sqlce/sscesa20.dll.
The string "sscesa20.dll" must be included in the URL.
|0||80045017||The SQL Server CE Replication Provider must have read permissions to the snapshot folder. Read permission is needed so the SQL Server CE Replication Provider can download the initial subscription to the Windows CE-based device.
The identity under which the SQL Server CE Replication Provider runs depends upon how IIS authentication is configured.
|0||80045020||Ensure that the data type length of the column supplied by the client is supported.
SQL Server CE supports only Unicode data types. It converts all ANSI character data types to their Unicode equivalent.
For example, if you subscribe to a table with a char column of 256 characters, SQL Server CE maps that table to a SQL Server CE ntext column. Then, if a user inserts into the ntext column a record that has a value larger than 256 characters, the user gets an error because the data cannot fit into the char column at the Publisher.
To correct this error, if you cannot change the schema of the Publisher to avoid this type of data type mapping, add application-level logic to limit the number of characters that users can enter on their devices.
|28560||80040E14||The snapshot format must be set to character mode for the publication.|
|25016||Ensure that no duplicate key violations have occurred.
Such violations may occur when users insert records into a table with an identity column. SQL Server CE remote data access (RDA) does not manage identity columns when a table is pulled.
Ensure that a replication publication is configured to manage identity columns for a table(s) in the publication.
|4060||80004005||Ensure that the user ID, password, and Initial Catalog to the OLEDBConnectionString parameter of your RDA Pull method are correct.|