Crystal Reports V10 SP6 error message 'Not supported' SQL 2008

Hi team,

I have a client installation using Crystal Reports v10 SP6 reporting sales and volume figures daily/weekly and monthly year on year comparisons for more than 100 stores.  

They have just upgraded the MSSQL 2000 database to MSSQL 2008 and the daily report fails with a 'Not supported' error message, on the larger brand of stores, but not on the much smaller brand of stores.

The error occurs during the 'reading record' process, where someway down this track Crystal will just come up 'Not supported', the record count resets to zero.

I'm trying to find out if is there a known condition in MSSQL Server 2008 Express Edition which trips up Crystal Reports Version 10 on large volumes of transactions.  (60 million or more rows)

All help is appreciated

Cheers
Bernard
BernardGBaileyAsked:
Who is Participating?
 
GJParkerConnect With a Mentor Commented:
Check the version Numbers of the SQL Native Client this is likelly to be SQL Server 2005 the 2008 driver should be called SQL Native Client 10.0.

I would load this onto the machine being used to run the report and try it out.

Like James this is just a shot in the dark, I'm not saying this will fix the issue but it's something I would try.
0
 
GJParkerCommented:
What connection method are you using ?

Have you upgraded the report connection to the SQL2008 Native Client ? You may want to try this to see if thsi fixes the issue.
0
 
James0628Commented:
Is the report reading tables directly (added and linked using the CR interface), or using a CR command, or using a stored procedure or view on the server?

 James
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
BernardGBaileyAuthor Commented:
GJParker,

I can only see SQL Native Client, not specifically SQL2008 Native Client. Do I load the SQL2008 Native Client onto the workstation?

James,
Using CR Command and direct to tables.

Thank you
0
 
James0628Connect With a Mentor Commented:
If you take the query from the report and try it on the server with one of the larger stores, does it run?  Do you notice anything unusual while it's running (like it takes an unusually long time)?

 Just taking shots in the dark here really, since I don't know exactly what might be causing the "not supported" error.

 James
0
 
BernardGBaileyAuthor Commented:
Trying CR 2008 with Native client duriong this week, I'll post the results then
Cheers
0
 
BernardGBaileyAuthor Commented:
Hi team,

I have resolved the issue by updating the links so the main retrieve is searching from a datetime parameter to a datetime field on the master table ; removed two redundant tables; added an index to one of the related tables.

This meant I could reduce the run time from 6 hours to 15 minutes and thereby no error.   The monthly report which is not required now, still fails with the same error; maybe the temp tables are too large or the OLE timeouts need increasing.

Anyway the current issue is solved, nothing to do with the drivers; however you both participated, so I'm awarding the points 50:50.
Thanks
Bernard
0
 
James0628Commented:
Glad you were able to resolve it.  The obvious guess would seem to be some kind of timeout issue or something like that.  I suppose the up side is that this problem forced you to make some changes which sped up the report immensely.

 James
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.