> # Error Handling

> The following types of errors can occur when you are using the SequeLink Client for .NET:

> - .NET errors
> - SequeLink Client errors
> - SequeLink Server errors
> - Database errors

> ### .NET Errors

> The SequeLinkError object collects information relevant to errors and warnings generated by the database server. See "SequeLinkError Object" for more information.

> See "Retrieving Warning Information" for a code example of how to return warning information.

> The SequeLinkException object is created and thrown when the database server returns an error. Exceptions generated by the data provider are returned as standard run time exceptions. See "SequeLinkException Object" for more information.

> ### ADO.NET Data Provider Errors

> Errors generated by the .NET Client have different formats, depending on the cause and source of the problem. Formats include:

>     [SequeLink nnnn] Memory allocation error occurred.
>     Invalid parameter type.

> If a native error code is displayed, you can look up details about the possible cause of the error. For a list of all error codes and messages, refer to the SequeLink Troubleshooting Guide and Reference.

> ### SequeLink® Server Errors

> An error generated by SequeLink Server has the following format:

>     DDTek.SequeLink.SequeLinkException:[SequeLink Server]
>     message

> For example:

>     DDTek.SequeLink.SequeLinkException:[SequeLink Server]
>     Required user name is missing.

> Use the native error code to look up details about the possible cause of the error. For a list of all error codes and messages, refer to the SequeLink Troubleshooting Guide and Reference.

> ### Database Errors

> An error generated by the database has the following format:

>     DDTek.SequeLink.SequeLinkException:[...] message

> For example:

>     DDTek.SequeLink.SequeLinkException:[Oracle] ORA-00942:table
>     or view does not exist.

> Use the native error code to look up details about the possible cause of the error. For these details, refer to your database documentation.