| # | Error Code Name | Description |
| 557 | PS_PIM_BADCREDENTIALS |
Bad Username or Password on Edit User web page. If using Exchange,
also check the PIM Server Domain on the Edit PIM Server page. |
| 558 | PS_PIM_HTTPERROR |
HTTP connection error, try changing settings on Edit PIM Server or Edit
PIM Protocol web pages. Check NLPim Log for specific HTTP or System
Error code [Verbose Logging will show url being hit]. Error codes in
the log less than 1000 are usually HTTP and error code codes greater
than 1000 are usually System Error codes. |
| 559 | PS_PIM_NOFOLDERSELECTED | No Folder Selected on Choose Address Books or other Format web pages |
| 560 | PS_PIM_CEXCEPTION |
MFC CException Thrown, check Log for specifics. These are rather rare;
some examples include Memory or File Access errors. If they do not
clear up on the next PIM Cycle, send Maximum Logging to Technical
Support. |
| 561 | PS_PIM_XMLEXCEPTION |
XML Exception Thrown, check Log for specifics. Most XML errors will be
from parsing in #565, but some may still happen in other XML usages.
Send Maximum Logging to Technical Support. |
| 562 | PS_PIM_COMEXCEPTION |
COM Error Thrown, check Log for specifics. Only found in Scalix PIM.
Most often these are sporadic and may only happen on one PIM cycle and
clear up on the next. If happening during Login, check that the Scalix
Wireless Connector and Outlook were setup correctly. |
| 563 | PS_PIM_STDEXCEPTION |
std Exception Thrown, check Log for specifics. Most often a string was
not parsed properly or an array index was out of bounds. Send PIM
Error Log or Maximum Logging to Technical Support for either case, as a
fix can usually be made. A System Error code is also included that can
be looked up in a place that lists System Errors. |
| 564 | PS_PIM_UNKNOWNEXCEPTION |
Unknown Exception Thrown, check Log for specifics. A System Error code
is also included that can be looked up in a place that lists System
Errors. |
| 565 | PS_PIM_XMLPARSING | Could not parse XML returned from server. Send PIM Error Log or Maximum Logging to Technical Support. |
| 566 | PS_PIM_XMLEMPTY | Empty XML returned from server. It is possible that no items were processed. |
| 567 | PS_PIM_XMLROOT |
Wrong XML Root returned from server. No items processed. It is
possible the PIM Server or PIM Protocol settings are incorrect. Send
PIM Error Log or Maximum Logging to Technical Support. |
| 568 | PS_PIM_DATABASEERROR | SQL Error or other type of Database error |
| 569 | PS_PIM_SERVERSPECIFIC | An error was returned that is specific to that server backend. Check Log for error code. |
| 570 | PS_PIM_NOTFOUNDINDATABASE | Failed to process an item because it was not in the database |
| 571 | PS_PIM_NOTFOUNDONSERVER | Failed to process an item because it was not on the server |
| 572 | PS_PIM_SEQUENCENUMBER | Failed to process an item because the Sequence Number from the device was out of order |
| 573 | PS_PIM_ITEMFAILED | One item failed to process as opposed to all items failing to process. Check Log. |
| 574 | PS_PIM_INVALIDVALUE |
An invalid value was used somewhere in processing. Check Log for
specific error. Examples include Device meetings with start time
before end time, Recurrence rules missing necessary values, Empty value
returned from database for a required field, Device contact has no name
or UID, and Invalid email address in device meeting. |
