Report Viewer Webpart IE9 issue -Reports not visible

Hi,
we have several installations using Sharepoint 2010 together with Reporting Services 2008 and 2008R2.
When displaying reports in Sharepoint through the report viewer webpart, the rendering in IE9 will sometimes not display the report. This means
the Sharepoint site including the report viewer headline is visible, but the report itself is not rendered. After pressing ctrl+F5 the report most of the time will show up. When viewing the logs of reporting services it is clear that the report has been executed,
but as stated it was not visible in IE9.
Even when forcing IE9 to render all Websites in compatibility mode there is no change. Out of 10 times the report is roughly 3 times not visible.
On systems still using IE8 there are no problems at all.
Any ideas?
Regards,
Andre

Hi,
I just want to know whether this problem occurs on all the computers which installed Internet Explorer 9? As a test, please try to reset IE then check the result again:
1.
Run Internet Explorer, use Alt + T to open Tools menu, choose Internet Options.
2.
Choose Advanced tag, click “Reset…” button, click OK in the pop-up box.
3.
Click OK to close Internet Options, then restart Internet Explorer.
In you have any progress, please let me know.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Similar Messages

Adding Report Viewer Webpart through console app Throws UpdatePanel Error

Hi,
    I had created a console application in Visual Studio 2012, to add Report Viewer Webpart into the team site page in sharepoint 2013. I wrote a code to add the Report Viewer webpart into the sharepoint site. I followed some links to successfully
execute the console application to add the Report Viewer webpart.
    After successful execution of the console application, if i navigate to the sharepoint site where i had added the webpart through console application, it throws the following error.
"Cannot unregister UpdatePanel with ID 'ViewerAreaUpdatePanel' since it was not registered with the ScriptManager. This might occur if the UpdatePanel was removed from the control tree and later added again, which is not supported".
    In my console application i didn't use any UpdatePanel. Just add the webpart into the default sitepage in sharepoint. Hope it was in the default page on the sharepoint site.
   I had googled the rootcause for the error, but i end up with all the answers pointing to ScriptManager into the aspx page. But i didn't find the SafeScriptManager .dll file. I followed the steps, in some other sites to create the ScriptManager
dll file, but that .cs project was not in compatible mode with VS 2012/2010.
I had attached the full executing code of the console application.
using System;
using System.Collections.Generic;
using System.Globalization;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls.WebParts;
using System.Xml;
using Microsoft.ReportingServices.SharePoint.UI.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Client.WebParts;
using Microsoft.SharePoint.WebPartPages;
using PersonalizationScope = System.Web.UI.WebControls.WebParts.PersonalizationScope;
using WebPart = Microsoft.SharePoint.WebPartPages.WebPart;
namespace SampleSite.Accessor
public class WebPartGalleryAccessor
private readonly string _rootSiteUrl = "http://<server>/sites/testsite";
private readonly string _pageUrl = "http://<server>/sites/testsite/test1/SitePages/Home.aspx";
private const string PageName = "home.aspx";
private const string SubSiteUrl = "test1";
private void AddReportViewer()
const int zoneIndex = 0;
var reportViewerWebPart = new ReportViewerWebPart();
AddReportViewerWebPartToSitePage(_rootSiteUrl, SubSiteUrl, _pageUrl, reportViewerWebPart, zoneIndex);
public void AddReportViewerWebPartToSitePage(string rootSiteUrl, string subSiteUrl, string pageUrl, ReportViewerWebPart webPart, int zoneIndex)
try
SPSecurity.RunWithElevatedPrivileges(delegate()
using (var pageLoadSite = new SPSite(rootSiteUrl))
pageLoadSite.AllowUnsafeUpdates = true;
using (var pageLoadWeb = pageLoadSite.OpenWeb(subSiteUrl))
pageLoadWeb.AllowUnsafeUpdates = true;
AddReportViewerWebPartToPage(pageLoadWeb, pageUrl, webPart, zoneIndex);
pageLoadWeb.AllowUnsafeUpdates = false;
pageLoadSite.AllowUnsafeUpdates = false;
catch (Exception exception)
throw new Exception("Unable to Add WebPart To Site Page: " + pageUrl + " Webpart title: " + webPart.Title + "Error: " + exception.Message);
private string AddReportViewerWebPartToPage(SPWeb web, string pageUrl, ReportViewerWebPart webPart, int zoneIndex)
try
HttpRequest request = new HttpRequest("", web.Url, "");
HttpResponse response = new HttpResponse(null);
HttpContext.Current = new HttpContext(request, response);
HttpContext.Current.Request.Browser = new HttpBrowserCapabilities();
HttpContext.Current.Request.Browser.Capabilities = new System.Collections.Generic.Dictionary<string, string>();
HttpContext.Current.Request.Browser.Capabilities["type"] = "IE7";
HttpContext.Current.Request.Browser.Capabilities["majorversion"] = "7";
HttpContext.Current.Request.Browser.Capabilities["minrversion"] = "0";
HttpContext.Current.Items["HttpHandlerSPWeb"] = web;
webPart.Title = "My Report Viewer";
webPart.ZoneID = "Top";
webPart.ReportPath = "/sites/testsite/Shared Documents/RemoteSalesRepor.rdl";
webPart.AsyncRendering = false;
webPart.DockToolBar = DockToolBarLocation.Top;
SPFile file = web.GetFile(pageUrl);
if (file.CheckOutType == SPFile.SPCheckOutType.None)
file.CheckOut();
using (SPLimitedWebPartManager manager = file.GetLimitedWebPartManager((PersonalizationScope)Microsoft.SharePoint.Client.WebParts.PersonalizationScope.Shared))
manager.AddWebPart(webPart, webPart.ZoneID, zoneIndex);
file.CheckIn("Webpart Added.");
return webPart.ID;
catch (Exception exception)
throw new Exception("Unable to Add WebPart To Page: " + pageUrl + " Webpart title: " + webPart.Title + "Error: " + exception.Message);
   Could anyone have the solution to overcome the above issue. I was knocking my head to resolve this error.
Note:
   I am using,
   1. sharepoint 2013
   2. SQLServer 2012R2
   3. Windows2008R2 server
I can able to create the ReportViewer webpart in the site manually.
Thanks
Jaibabu

Hi Jai,
Did you find a workaround to this issue. I have the exact same issue with SharePoint foundation 2010. I am adding report viewer webpart through HTML5 web page hosted in SharePoint site.
Regards,
Ojas Maru ( My blog )

Getting 'an unexpected error has occurred' while editing report viewer webpart in Sharepoint webpart

Hi All,
I have added report viewer webpart in a page. On click of edit webpart link I am getting webpart edit toolbox. But after clicking on apply or save button, getting the following error.
'an unexpected error has occurred'
If I refresh the page then report is working fine, but webpart edit settings are not getting saved.
Please suggest.
Thanks in advance !
Soumya Das

Hi ,
For troubleshooting your issue, please take steps as below:
1. Open web.config file of current web application
2. Find the node that begins
<trust level=
3. Change the trust level from WSS_Minimal to
WSS_Medium
4. Save the file
5. Drop to command prompt and execute :
iisreset
If your issue persists, please provide detail error message of ULS log to determine the exact cause of the error?
For SharePoint 2010, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Best Regards,
Eric
Eric Tao
TechNet Community Support

Report Viewer WebPart in SPD - Missing required page header

Hi,
I seem to be getting the following error when adding the Report Viewer webpart to a minimal masterpage in SPD:
Error Rendering Control - Unnamed 1 Missing Required Page Header
If I create a page through the IE browser on the SharePoint then I can add the Report Viewer webpart. However when I then go to view that page in SPD - again I get the above message.
This is truely irritating ....
Thanks - Steve

Looks like a bug in sharepoint or some other design-time quirk in SPD. The code in the report viewer webpart (v11.0) that throws the exception is:
public static void RegisterCss(Page page)
if (page.Header == null)
throw new Exception("Missing required page header");
HtmlLink child = new HtmlLink {
Href = StyleSheetLink
child.Attributes.Add("rel", "stylesheet");
child.Attributes.Add("type", "text/css");
page.Header.Controls.Add(child);
...so it appears that SPD is not fully instantiating the master page, or otherwise partially executing it. The Header property on Page should be populated with a HtmlHead instance, which is a reference to the head tag in the master page (which must have
runat=server on it.) For me, the master page is fine -- this is why it still works when adding it via the web ui directly in the browser. When it's put through the design-time grinder in SPD, this property is null. I would presume that this is either a bug
in the webpart, or a failing in SPD.
I'm running sharepoint server 2010/sp2 and SPD 2010/sp2/x86, for what it's worth.

Select Row as Data filter between Report viewer webpart

Hi All,
i have a requirement in SharePoint 2013 which has 2 SSRS Report Viewer webpart.
i need to pass data which i select in First webpart to second webpart.
is this possible how can i achieve this.
Thanks for your time.
Regards
Bhasker
hi

Hi Bhasker,
In my opinion, you can refer to the steps as below:
1.Get the parameters from one SSRS Report Viewer Web Part:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/454ae44f-0d29-485a-8830-d2fb0e03f250/how-to-pass-parameters-from-report-viewer-to-report-server?forum=sqlreportingservices
http://msdn.microsoft.com/en-us/library/ff487390.aspx
2.Pass parameters to another SSRS Report Viewer Web Part:
http://sharepoint.infoyen.com/2012/08/25/pass-multiple-filter-parameters-to-custom-report-viewer-web-part/
http://stackoverflow.com/questions/2564178/passing-multiple-parameters-from-custome-webpart-to-reporting-services-report-vi
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Eric Tao
TechNet Community Support

SSRS report viewer webpart issues in SharePoint 2013

Even though SSRS Add in has been installed on both the frontends which are in the same SharePoint 2013 farm, SSRS report viewer web part does not render any reports from one of the servers and on that server it just asks to configure the webpart by giving
an option to open the tool pane...
I am really not sure why it is not picking up the report RDL configuration, which is working fine from the other server.
Any help on this would be really appreciated.
Thanks in advance.

Run the SharePoint Products and Technologies Wizard on this server. If simply running it does not fix it, remove the server from the farm and then re-join it, using the wizard.
Stacy Anothersharepointblog.blogspot.com

Unable to insert sql server reporting services report viewer webpart

Hello,
We are trying to add a SQL Server Reporting Services Report Viewer and when we click add we get the following error message
The file you imported is not valid. Verify that the file is a Web Part description file (*.webpart or *.dwp) and that it contains well-formed XML.
Does anyone know what the fix to this is?

Hi，
The Report Viewer Web Part is a custom Web Part that is installed by the Reporting Services Add-in for SharePoint Products and associated with report definition (.rdl) files that are processed by a Microsoft SQL Server Reporting Services report
server.
To install the Web Part, you must run Setup for the Reporting Services Add-in. You should not install or uninstall the Web Part independently. It is part of the add-in and can only be installed through the add-in setup package. The Report Viewer Web Part
file name is ReportViewer.dwp. It is located in the Program Files\Common Files\Microsoft Shared\web server extensions\15\template\features\reportserver folder and should not be moved to other folders.
To use the Web Part, you must have installed and configured the Reporting Services Add-in and configured the report server for SharePoint integration.
For more information,you can have a look at the blog:
http://msdn.microsoft.com/en-us/library/jj219068.aspx
http://msdn.microsoft.com/en-us/library/aa905871.aspx
http://msdn.microsoft.com/en-us/library/bb522800.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Crystal Report viewing and Printing Issue

Hi Experts
I use crystal Reports for PO,AR Invoice,Delivery and many other documents.It takes more than 5 mins to view layout from crystal report and print sequence printing takes more than 10mins.Please Help me to rectify this issue..
Regards
Naresh Kumar

Hi Naresh,
What is your SAP version and Patch Level ?
I believe in new version this issue has been addressed by SAP. Also note SAP B1 8.81 PL 07 has some issues in crystal Report, it asks for SQL user id and password, SAP is aware of this issue. So if you plan upgrade to latest PL then ensure that Crystal report issue is resolved, otherwise you will be in trouble.
BR
Samir Gandhi

Report Viewer Webpart is Blank in Custom Master Page

Dear Experts ,
Recently my team created a new master page to replace seattle default page in Sharepoint 2013. Things were fine till the moment we accessed one of site page containing a Report Viewer Web Part to load SSRS rdl. The web part is blank
with just standard SSRS toolbar and parameter. To isolate the problem, I have confirmed that the same page works fine in seattle master. I notice that something could be missing in our site (though I am clueless on what those are). There is one post online
from someone with potentially similar issue, but it does not help in our case. Some pointers from will be appreciated. Cheers.
http://blogs.msdn.com/b/selvar/archive/2013/11/28/using-reporting-service-web-part-with-sharepoint-custom-master-pages.aspx

Hi,
Please try to add AsyncPostBackTimeout="0" inside the ScriptManager code in your master page.
<asp:scriptmanager id="ScriptManager" runat="server" enablepagemethods="false" enablepartialrendering="true" enablescriptglobalization="false" asyncpostbacktimeout="0" enablescriptlocalization="true" />
If the issue still exists, I suggest you provide some error messages or code for further research.
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

Report Viewer icon rendering issue with web controls

Hi,
I have a sample application in ASP.NET 2.0 in which if I have a report viewer control in an aspx page and when I try to browse the page the report renders properly with all icons image also. But in the same application I am having a web user control that is having the report viewer control and I have added this control on another page. Now if I try to browse this page the report is rendered properly but the icon images are not displayed rather as 'X' is displayed indicating images are missing.
Thanks
Kajal

It sounds like the CrystalReportViewer control does not "agree" with the .NET control you are embedding it in. Can you be more specific with the exact steps to duplicate this issue? It would be helpful to know what controls you are using.
Viewing the source code will be helpful in your troubleshooting. You'll also want to review your IIS logs to see what error are popping up there. It could be that the gifs are being searched for in another location. You may need to make a copy of the crystalreportviewerxx directory in a new location.
Regards,
David

SSRS web based report viewer control rendering issues - text getting clipped chopped off

Hi,
I am using web based SSRS report viewer control to display SSRS reports in browsers like Chrome, FF, IE, Safari etc. My issue is some text is getting chopped off (clipped) in all cells of some reports. I investigated on my end by analyzing generated HTML
and I could see a problem in the HTML that report viewer control is generating. But I am afraid to apply any HTML or Javascript hacks at the moment considering we have hundreds of reports.
You can see in above image how text got chopped off. The problem in HTML (given below) is the text has been wrapped in a div tag with a fixed height. If I remove the height and also padding on parent TD, the text appears properly.
<td class="A23dfe7c5f99245f2a0db522a22a6035597c" style="HEIGHT:5.00mm;background-color:#d3d3d3;"><div style="HEIGHT:3.24mm;overflow:hidden;"><table lang="en-US" cellspacing="0"
cellpadding="0" border="0" class="Pd9776e5f7eaf4df696265b8b49d1da39_1_r17"><tbody><tr><td class="A23dfe7c5f99245f2a0db522a22a6035597" style="word-wrap:break-word;white-space:pre-wrap;">MyType11</td></tr></tbody></table></div></td>
Please let me know if you have faced a similar scenario before.
Here is link to stackoverflow thread -
Stackoverflow thread
Regards
Murtaza

Hi Murtaza,
According to your description, when you display the report with Report Viewer control, the data within the text is cutoff.
Based on my research, the issue could cause by that Arial Unicode MS font hasn’t been installed on the server where Reporting Services run. Besides, when we use ReportViewer control to render report, we’d better set
AsyncRendering="true" in the Report Viewer control. Also please run the IE with compatibility mode. For more information, please refer to similar threads below:
Data in column getting cut-off in report viewer control
SSRS Rendering Issues
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Publishingpage report viewer webpart in sharepoint

in the publishing page, report is showing in report viewer web part

Hi bhanu,
What is your issue?
Please give more detailed information about your issue. It will make others easy to find a solution for you.
If you want to use Report View Web part to display your report in a publishing page, please have a look at the link below, it is for SharePoint Foundation 2010 and wiki pages, and also should work for SharePoint 2013 server and publishing pages.
Also, if your issue is about SSRS, you can also create a new thread on SQL server Reporting forum, more experts will assist you with reporting.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlreportingservices
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Report Viewer WebPart for Sharepoint - Printing (Unable to load client print control)

Hi there,
I am running a report via the report viewer web part on a SharePoint page. The report itself is working great. But when I attempt to print it, I get a prompt to install something....and then it is followed up with "Unable to load client
print control".
There are some posts out there about updating the a certain CU or to find the RSClientPrint cab and unloading the dlls into the system32 folder and registering it. I've tried that but no go.
Anyone else encounter this issue? If so, potential solutions?
SP 2010 - 14.0.7221.5000
SQL Server 2008 R2 (Reporting Server)- 10.50.1617 (have tried updating to 10.50.6000.34)
IE = 10.0.9200
And yes, I am running as local admin....so there shouldn't be any issue installing the active x component on IE.
Thanks in advance,
Eric

Hi Eric,
According to your description, you can't load the print button in your sharepoint site. Right?
In Reporting Services, Each user who wants to use the print feature must download and install the ActiveX control that provides client print functionality. The first time a user clicks the
Printer icon on the report toolbar, the Microsoft ActiveX control is downloaded to the computer. After the control is downloaded, the
Print dialog box displays whenever the user clicks the Printer icon.
So in this scenario, please enable the setting Download signed
ActiveX controls in Internet Explorer and download it. Please follow the steps below:
Click Tools -> Internet options.
Switch to the Security tab, select the Trusted sites zone, and then click
Sites.
Type the URL of the SQL reporting server, click Add, and then click Close.
Click the Custom level button, scroll to the ActiveX controls and plug-ins
node.
Click Enable for Download signed ActiveX controls, and then click OK.
Then we need to have the
EnableClientPrinting is set to true.
In SharePoint Central Administration, click Application Management.
Click Manage service applications.
Click the name of your Reporting Services service application, and then click
Manage in the SharePoint ribbon.
Click System Settings.
Select Enable Client Printing. The Enable Client Printing option is near the bottom of the page.
Click OK.
Reference:
Enable and Disable Client-Side Printing for Reporting Services
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Login error with report viewer when opening Crystal report with subreport

Hi
I have a problem with a login error (database vendor code 18456) when I try to open a crystal report to view it.
The report uses data from an external payroll database but I'm running it via our Accounts system (it's a convenient front end for users to run the report from). This works fine for another report that doesn't have any subreports. However when I run the Crystal report that has subreports, the report generation process works but when the crystal reports viewer tries to open the report I get the login error. It doesn't seem to be passing the login details for the payroll database down to the subreport.
I'm using Crystal Reports version 11.0.0.1282. The Accounts system is Technology One. Tech One have provided a report template that has several formulas designed to allow Tech One to play nicely with Crystal. One of these formulas allows me to enter the nickname of the external database that the report needs to use. The external database's connection details are fully specified in the Tech One configuration section (server console). So in this case the report says use database U1 & the server console identifies U1 as being the payroll database, specifies the connection path & has the username & password required to logon to the payroll database/server.
The report is running ok & retrieving data, but for some reason the viewer is erroring. If anyone has any ideas for how I can get the login details used to run the main report to flow through to the subreport it would be much appreciated.
Thanks
Sue

I understand your frustration. We can do a few things. But really, it should be Technology One contacting us. To use an analogy (which you are free to share with Technology One). They built a car and sealed the hood. You bought the car, but he engine does not quite run as it should. You bring the car to the mechanic and all he can do is look at the car as he can not even open the hood.
In any case, here is what I would do if I could open the hood (e.g.; if I was dealing with Technology One):
1) Look up database vendor code 18456. This is simply the error our print engine is receiving from the database client and it simply passes it through relatively unhandled. This you should be able to do your self or ask Technology One to tell you what that means.
2) Break out the subreport and see if it runs on it's own in the application (if this is a permissions issue - which I doubt - it should come up here too). Unfortunately, this is for Technology One to do...
3) Run the report (with the subreport) in the CR designer. Does it work there? If this is a win app and it works, we again eliminated permission issues. And we also confirmed that the report is good. Again, Technology One should do this for you.
BTW.; CR 11.0 is out of support - not sure if you or Technology One are aware of this...
4) Can the developer duplicate the issue on his development computer?
Now, there are couple of instances where you say something like; "the report works and gets data, but the viewer errors out":
+The report is running ok & retrieving data, but for some reason the viewer is erroring.
However when I run the Crystal report that has subreports, the report generation process works but when the crystal reports viewer tries to open the report I get the login error. +
How do you know the report is retrieving data? From the error I would say the report never connects, thus the error / request for a logon...
So, the short of all of this is; get Technology One to contact us. They can do it over the forums or obtain a phone case here;
http://store.businessobjects.com/store/bobjamer/en_US/pd/productID.98078100
Now, here is a warning. As CR 11.0 is out of support Technology One will have to upgrade to CR 11.5, before that can create a phone case, which for them and you brings up another bunch of issues...
If you do not get any joy from the support person at you are talking to at Technology One, get him to escalate the issue. They are the ones that should be talking to us...
Ludek

Crystal Report Viewer Credential Prompt for Report with Dynamic Parameters

The .NET Crystal Report Viewer is prompting for database credentials when launching a report containing dynamic parameters. This only occurs for reports created with SAP Crystal Reports 2011 designer. Reports created with Crystal Reports XI designer (where dynamic parameters were first introduced) work correctly.
The credential prompt window contains the following fields:
- Server Name: <server name> (disabled)
- Database Name: <database name> (disabled)
- User Name: <empty> (enabled)
- Password: <empty> (enabled)
- Use Single Signon Key: false (disabled)
The values in the prompt window which are disabled are the database connection values used during the design of the report in the SAP Crystal Reports 2011 designer.
Expected Result:
- No prompt for database credentials.
- Values read from the database should be populated in a drop down for the dynamic parameters.
Environment:
- Visual Studio 2010 (C#)
- Windows 7 Enterprise
- SAP Crystal Reports runtime engine for .NET Framework 4
- SAP Crystal Reports, version for Visual Studio 2010
- SAP Crystal Reports 2011
The database connection is being set to use a DSN. It must be a DSN as the calling application is only aware of the DSN/Username/Password values. These values are being passed to the Crystal Report Viewer contained in a Windows form.
The database connection for the report is being set as follows:
foreach (InternalConnectionInfo internalConnectionInfo in this.report.DataSourceConnections)
    // Must set the UseDSNProperties flag to True before setting the database connection otherwise the connection does not work
    if (internalConnectionInfo.LogonProperties.ContainsKey("UseDSNProperties"))
        internalConnectionInfo.LogonProperties.Set("UseDSNProperties", true);
    // Supposed to set the database connection for all objects in the report (ie. main report, tables, sub reports)
    internalConnectionInfo.SetConnection(this.DSN, string.Empty, this.LoginName, this.Password);
The SetConnection method's signature is as follows:
   SetConnection(string server, string database, string name, string password)
As you can see from the code snippet above I am setting the DSN name as the server parameter, blank for the database parameter (a database connection using DSN should only require DSN name/Username/Password) and the database username and password respectively.
Is this a SAP bug?
Is this the correct way of setting the database connection to use a DSN?
Is there some other properties that need to be set somewhere else in the report through code?
Any help would be greatly appreciated.

Thanks for the pointer to the database connection code generator. After taking a look at the output from the tool I was able to finally get the dynamic parameters to load and populate properly without prompting for credentials. I needed to tweak the outputted code a bit to match my requirements of using a DSN only connection.
Instead of updating the database connection properties contained within the Report.Database.Tables collection from the CrystalReports.Engine namespace, I changed it to replace the database connection properties in the Report.ReportClientDocument.DatabaseController.Database.Tables collection from the CrystalDecisions.ReportAppServer.DataDefModel namespace. For one reason or another, using the RAS namespace solved the problem.
Below is the updated code with the change made:
using RAPTable = CrystalDecisions.ReportAppServer.DataDefModel.Table;
foreach (InternalConnectionInfo internalConnectionInfo in this.report.DataSourceConnections)
    // Must set the UseDSNProperties flag to True before setting the database connection
    if (internalConnectionInfo.LogonProperties.ContainsKey("UseDSNProperties"))
        internalConnectionInfo.LogonProperties.Set("UseDSNProperties", true);
    // Sets the database connection for all objects in the report (ie. main report, tables, sub reports)
    internalConnectionInfo.SetConnection(this.DSN, string.Empty, this.LoginName, this.Password);
// The attributes for the QE_LogonProperties which is part of the main property bag
PropertyBag innerPropertyBag = new PropertyBag();
innerPropertyBag.Add("DSN", this.DSN);
innerPropertyBag.Add("UserID", this.LoginName);
innerPropertyBag.Add("Password", this.Password);
innerPropertyBag.Add("UseDSNProperties", "true");
// The attributes collection of the tables ConnectionInfo object
PropertyBag mainPropertyBag = new PropertyBag();
mainPropertyBag.Add("Database DLL", "crdb_ado.dll");
mainPropertyBag.Add("QE_DatabaseType", "OLE DB (ADO)");
mainPropertyBag.Add("QE_LogonProperties", innerPropertyBag);
// Pass the database properties to a connection info object
ConnectionInfo connectionInfo = new ConnectionInfo();
connectionInfo.Attributes = mainPropertyBag;
connectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
connectionInfo.UserName = this.LoginName;
connectionInfo.Password = this.Password;
// Replace the database connection properties of each table in the report
foreach (RAPTable oldTable in this.report.ReportClientDocument.DatabaseController.Database.Tables)
    RAPTable table = new RAPTable();
    table.ConnectionInfo = connectionInfo;
    table.Name = oldTable.Name;
    table.QualifiedName = oldTable.QualifiedName;
    table.Alias = oldTable.Alias;
    this.report.ReportClientDocument.DatabaseController.SetTableLocation(oldTable, table);
this.report.VerifyDatabase();
Thanks again Ludek for the help.

Report Viewer Webpart IE9 issue -Reports not visible

Similar Messages

Maybe you are looking for