Solved

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.

Posted on 2014-04-01
11
1,421 Views
Last Modified: 2014-04-09
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
Comment
Question by:Papa1NZ
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 13

Expert Comment

by:Koen Van Wielink
ID: 39971870
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
 

Author Comment

by:Papa1NZ
ID: 39973728
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
 

Author Comment

by:Papa1NZ
ID: 39973998
I have just moved the SSRS database to be on the same server as the SSRS instance and no change :(
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 13

Expert Comment

by:Koen Van Wielink
ID: 39974002
What's the driver you're using in your ODBC connection?
0
 

Author Comment

by:Papa1NZ
ID: 39974104
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
 
LVL 13

Expert Comment

by:Koen Van Wielink
ID: 39974165
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
 

Author Comment

by:Papa1NZ
ID: 39976927
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
 
LVL 13

Expert Comment

by:Koen Van Wielink
ID: 39977088
But when you create another ODBC connection using a different driver, does it still work?
0
 

Accepted Solution

by:
Papa1NZ earned 0 total points
ID: 39979679
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
 
LVL 13

Expert Comment

by:Koen Van Wielink
ID: 39980003
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
 

Author Closing Comment

by:Papa1NZ
ID: 39988240
Kvwielink helped point out where the problem is occurring. Which appears to be with an application ODBC driver.
0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question