web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Crystal Report - error...
Microsoft Dynamics SL (Archived)

Crystal Report - error opening report - database vendor code: 208

(0) ShareShare
ReportReport
Posted on by RedStorm 1,364

We upgraded to SL2011 FP1 from SL7 FP1.  Now when we print/print preview certain crystal reports they come up with an ERROR message:

Crystal Report Windows Forms Viewer - Failed to retrieve data from the database.  Details:  [Database Vendor Code: 208] ...

Any suggestions?  Thank you, Dave

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at
    RE: Crystal Report - error opening report - database vendor code: 208

    I had a similar error and it took me a while to REALLY read the error message: DATABASE VENDOR CODE: ####.  Hmmmmm ... my database is SQL Server and I have an error number. I went to a page that defined the SQL Server error codes and found my code: Syntax error converting datetime from character string. I went to my stored procedure and I had params that were defined as varchar() but used to compare to a date data type. While that did in fact work if I executed the code in a query window something happens when the resultset is returned to Crystal reports. I simply change the params to datetime and my report worked. What really threw me off was the report would PREVIEW the data but when viewed through the viewer it failed so I spent hours scouring the reports. The sad thing is I made this very same mistake a couple of years ago and forgot the lesson. So the moral is it might not be the report that has the problem. Go to >> www.sql-server-helper.com/.../msg-1-500.aspx - 208 = Invalid object name '%.*ls'. Hmmmm .. not as helpful as mine but there you go.

  • Suggested answer
    RedStorm Profile Picture
    RedStorm 1,364 on at
    Re: Crystal Report - error opening report - database vendor code: 208

    All:  1.  I found that when I went to VERIFY DATABASE in this particular crystal report I was getting tables that it didn't like (wanted me to remove the tables and I said No!!).

    2.  That led me to this little trick that I found online that fixed my issue.  Thanks Jeff Trotman and Rick Kerns!! :-)

    wisdomofsolomon.wordpress.com/.../crystal-reports-tables-not-found-during-verify-database

    3.  It shows you how you can use the "Overridden Qualified Table Name" property for the table(s) in the Crystal Report designer to get around the issue.  Alternatively (as mentioned in the link above) you can Update EACH table.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Dynamics 365 Community Calls Return
Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft
Responsible AI policies for the Community

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans