The first step in debugging a Chilkat method that returns a failed status is to examine the contents of the LastErrorText property. The LastErrorText property will contain information about the last method call on the object.

For example:

success = mailman.SendEmail(email);
textBox1.Text = mailman.LastErrorText;

The LastErrorText property is standard on all Chilkat classes/objects.  The error information may also
be accessed in XML or HTML format via the LastErrorXml and LastErrorHtml properties.
It may also be saved to a file by calling SaveLastError.

The LastErrorText will contain information about what transpired within a method call
even when the method succeeds.  Therefore, if a method returns a value indicating success,
but something did not go as expected, examine the contents of LastErrorText.

Note: The purpose of the LastErrorText is to help programmers determine the cause of a problem. It contains detailed information and is not something you would normally display to non-technical end-users.

It is designed to provide most (if not all) of the information that should be sent to when requesting support.  Please be sure to cut-and-paste the contents of the LastErrorText into your support email request.  (Please: Simply cut-and-paste the text.  This is much preferable to screen captures, MS-Word docs, or image files (JPG, GIF,  BMP) etc.)

When examining the LastErrorText, look for the “DllDate” that is contained within it.
If it is more than a few months old, Chilkat will most likely ask you to try the latest
pre-release from   This is to ensure that you
are not reporting a problem that is already fixed, and it also makes sure the LastErrorText
has the best information.  The contents of LastErrorText is continually being improved
and refined.

C++ Notes:

The LastErrorText “property” is actually accessed as one of two methods:
void LastErrorText(CkString &str),
const char *lastErrorText(void)