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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Crystal report returni...
Microsoft Dynamics SL (Archived)

Crystal report returning Database Vendor code 102 error

(0) ShareShare
ReportReport
Posted on by Community Member

A custom crystal report using a view and a table. Getting error

Failed to retrieve data from database.

Details: [Database Vendor Code: 102]

We get this error only on one workstation. If the user logs on to a different workstation they can run the report. Have reloaded client on workstation, rebooted workstation, deleted ODBC connection. Different user logs on (administrator rights) and doesn't work.  Something wrong with workstation.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Peter, what version of SL and what version of Crystal Reports are you running?

    You might try one ODBC change to see if it makes any difference.  Configure the ODBC definition for your application database using the SQL administrator credentials.  On the DSN configuration page, look at the Use ANSI option settings.  If they are checked, uncheck them and try the report.  If the are not checked, check them and try the report.  I know that sounds strange but I have found that the ANSI settings affect various reports built under prior versions of Windows talking to different versions of SQL.

    The other common issue with some user developed reports is that they are built with a particular printer type and then the workstation running the report cannot resolve the printer optimization codes in that report.  If you open the report in Crystal and go to the printer setup, check the No Printer option.  This causes the report to be more generic and lets it work with any printer.

    Not sure if either of these will help but they are things I try when I get an error similar to this and one of them usually fixes the issue.

  • harshshah Profile Picture
    harshshah 30 on at

    are the sql odbc drivers for both workstation same.  on SL2011 it uses sql 2012 native client odbc.

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

Quick Links

Responsible AI policies

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

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November 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