This might not be an complete 'answer' since you're still troubleshooting, and asking for help, but its too long for a comment. Of note, at this time SAP does not support VS 2017, and there is possibility that has something to do with this, but I've seen similar messages even back in VS 2010 so here goes. Megasoft ot dyadi sema vipusk 3. Short guess add this to your app.config file: or more specifically target.NET like: Longer troubleshooting thought process.

The error message usually would indicate that the DataSet (DataTable in this case) is not set at the time it is used in the report object. You could put a breakpoint there and see if this is true (where SetDataSource is used). It might be that I am wrong here and there is a properly set DataSet even at that point, and the issue happens a little later in the viewer. I ran into issues like this a long time ago and if memory serves this was the route I took to track down a solution. Basically my problem was the way the EXE was using ADO objects in the viewer. Without knowing everything about your project I would start down this path to debug. Other questions would be does it work in VS 2015?

Did it ever work in X64 and stop working? Does it work for other operations, like can you access the report object programatically, and it's only erring in viewer? I don't know if this is useful for you or not. But I came across following solution when I had issue with server 2012.

Download the Crystal Reports Runtime 32bit & 64 bit for all Editions of Visual Studio and learn how to install the Crystal Report Runtime. I have windows application with Dot net Framework 2.0 and Crystal Report 2008. Since this crystal report version not support in windows 2016, planning to move crystal report 2016 version. Free crystal reports redistributable 64-bit download software at UpdateStar. 02.01 SAPGUI_6.20. Redistributable package installs the.NET Framework runtime.

Framework 4.6 causes Crystal Reports for Visual Studio to create a unique folder path to the Crystalreportsviewer13 folder in IIS and IISExpress DEV. Environment Crystal Reports for Visual Studio Windows 7 Windows 8.x Windows 2012 Server Windows 2016 Windows 10 Reproducing the Issue We’re aware of such problem. Actually it’s related to.Net Framework 4.6, not only limited to Win10 or Windows Server 2016 preview(these OS by default installed.Net 4.6 ). If you install.Net 4.6 on Win7 there will be same issue. The root cause is MS provide the update to.Net Framework 4.6 via windows update, then the small version of.Net 4.6 will changed. For ASP.NET web site target to.Net 4.6 app pool, CR viewer will try to find the viewer resource file(js & icon) from.

Aspnet_client system_web 4_6_xx crystalreportviewers13 The highlight xx is the small version of.Net Framework 4.6. On Win10 RTM, it’s 4_6_79; on Win7+.Net 4.6 it’s 4_6_81, if user installed recent KB3098786 it will be 4_6_118 The version number will change again if next KB update for.Net Framework 4.6. So please create a BOSAP case for it. At least in SP16 we need add more symbol link to support different small version of.Net Framework 4.6. And a better solution is change the path of viewer resource file loaded, eg, point to a virtual folder under IIS.

Symantec ghost 32 free download version. Symantec helps consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored.

That required fix in Viewer side and need more time, we will try to implement it in SP16 Thanks, Soda Resolution Our Developers are aware of this issue and we should be able to provide a fix in Service Pack 16 The issue is related to.Net Framework 4.6. The root cause is MS provide the update to.Net Framework 4.6 via Windows Update ASP.NET web site will target the.Net 4.6 app pool, CR viewer will try to find the viewer resource file(js & icon) from.