• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1616
  • Last Modified:

I receive errors running report Via Report Manager or when I am connected to the Report Server. Reports run ok if I disconnect Report Builder from the Report Server.

Hi Experts,

I am using SSRS reports using an ODBC connection to the database.

SSRS reports run/authenticate fine using 32bit connection (ODBC32). But when I join the 64bit (ODBC)connection (Report Manager) then reports crash. It doesn't seem to authenticate the user.

I have set this up a few times but the problem seems to go away somehow? It could be a server setting? I would like to hear any possible fix's I should try as I have the same problem again and need it fixed ASAP.

The error I receive when I try to run the report when I have connected the Report builder to the Report Server is as follows:

Unsupported RPL stream version detected: 104.116.1344302189. Expected version: 10.6.
----------------------------
An error occurred during client rendering.

Many thanks in Advanced!
0
Papa1NZ
Asked:
Papa1NZ
  • 6
  • 5
1 Solution
 
Koen Van WielinkBusiness Intelligence SpecialistCommented:
If you google the error you'll find that it's a fairly general error description with a host of underlying problems for different people. But a few suggestions I found:

- Remove the page break indicator from the tablix properties and redeploy the report
- Restart the agent service
- If you're running the reports through SharePoint it might be that you have to update the SharePoint add-in.

I haven't seen the error myself before, this is just some stuff I found online. Hope it helps.
0
 
Papa1NZAuthor Commented:
Hi Kvwielink,

Thanks for those bits of information. I've actually already done lots of google searches including the above details you mentioned but none have helped so far. I am not using sharepoint.

Its a really strange issue. I am now moving the SSRS databases to be stored directly on the SSRS server rather than to the SQL Server. Hopefully this might change things? However if you have any other thoughts I would like to hear them.

Many thanks,
0
 
Papa1NZAuthor Commented:
I have just moved the SSRS database to be on the same server as the SSRS instance and no change :(
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Koen Van WielinkBusiness Intelligence SpecialistCommented:
What's the driver you're using in your ODBC connection?
0
 
Papa1NZAuthor Commented:
Its a modified ODBC driver for an application. Do you think that might be the issue? I have found that the Report Manager will connect directly to the database server and run a report fine. But if I connect up the report via the ODBC driver the report fails to authenticate to the database. It fails at the authentication going via the ODBC driver and does not produce any logs.
0
 
Koen Van WielinkBusiness Intelligence SpecialistCommented:
It might be. Any chance to test it using a standard ODBC driver like SQL Server Native Client 10.0? Or even the standard SQL Server driver?
0
 
Papa1NZAuthor Commented:
Hi Kvwielink,
Yes the native client connection to the database works fine. I can run a report ok. Only occurs when I connect via the ODBC driver.
0
 
Koen Van WielinkBusiness Intelligence SpecialistCommented:
But when you create another ODBC connection using a different driver, does it still work?
0
 
Papa1NZAuthor Commented:
Yes a native odbc connection going to the same database with the same user works fine. So this is pointing out that the issue is with the ODBC driver. I have raised the issue with the ODBC Driver developers.  Many Thank for your help Kvwielink.
0
 
Koen Van WielinkBusiness Intelligence SpecialistCommented:
Glad I could help, even though I wasn't able to solve the issue. Good luck with it. Would be nice if you could give us an update if you do get it fixed.
0
 
Papa1NZAuthor Commented:
Kvwielink helped point out where the problem is occurring. Which appears to be with an application ODBC driver.
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now