Report errors 'Database Vendor Code:'

When Crystal Reports experiences an error running a report, it may display the error message with Database Vendor Code:

Here is an interpretation of the different vendor codes:

Database Vendor Code:11 - This means 'General network error. Check your network documentation'. At the time the error occurred, the affected user's network connectivity wasn't working correctly, either because of their network adapter settings or because their network connectivity in general isn't entirely reliable. This article from Microsoft may help to address the issue: http://support.microsoft.com/kb/942861

Database Vendor Code:14 - This error means "Invalid Instance". It can occur if port 1433 is associated with a named instance rather than the default instance. Sqlsvr32.dll, which is used by the Crystal Reports components, does an "InstanceValidity" check and if port 1433 is associated with a named instance the check could fail. The workaround for this would be to specify the port number along with the SQL server\instance name (i.e. SQLServer1\SQL,1433) in the TrackIt.Core.DataAccess.xml (specifically in the 'Reports server' line of the file).

Database Vendor Code:207 - The report references a column that cannot be found in the database.

Database Vendor Code:208 - The report references a table or view that cannot be found in the database.

Database Vendor Code:229 - The report user in the database does not have the necessary permissions to view the data.  Try running usp_Jiwa_Grant_Application_Permissions 'JiwaUser' and usp_Jiwa_Grant_Reporting_Permissions 'JiwaReports'

Database Vendor Code:241 - This is a datatype conversion error. Specifically the error is "Conversion failed when converting datetime from character string". This can appear if the default design of the one of the built-in tables has been modified.

Database Vendor Code:245 - This is a datatype conversion error. This usually occurs when the database views being referenced by the report refer to an incorrect list of columns, which causes the view to generate a 'Conversion failed' error when it tries to query the underlying tables. Resolving the problem usually requires a deeper analysis of the database to trace the exact query that is being called by the report, and then dropping and recreating or altering the associated views with known good objects so that their column lists match up correctly with the underlying tables.

Database Vendor Code:4413 - This is a binding error that occurs when certain views reference other views that do not exist, usually because the view calls another view owned by a user that no longer exists in the database. The problem views must be re-created to resolve the issue.

Database Vendor Code:1205 - There is a deadlock on resources with another process and your report has been chosen as the deadlock victim. Rerun the report or modify the report to use a view with WITH (NO LOCK).

Database Vendor Code:8153 - The subquery in the stored procedure returned more than 1 value. This is not permitted when the subquery follows =, !=, = or when the subquery is used as an expression