This project has moved and is read-only. For the latest updates, please go here.


VS2015 crashes when displaying any report


Visual Studio crashes on me when I try to display any BIDS Helper report (such as the "Unused columns report" for a DSV in a SSAS project). The separate window with the report viewer opens, displays the Loading briefly, then I get the "Visual Studio 2015 has stopped working" box.

The only bit of troubleshooting information I managed to get was by clicking "Debug" in the "has stopped working" dialog:

'System.ExecutionEngineException' occurred in Microsoft.ReportViewer.Common.dll
Microsoft.ReportViewer.Common.dll!Microsoft.ReportingServices.ReportIntermediateFormat.TextBox.SetExprHost(Microsoft.ReportingServices.RdlExpressions.ExpressionHostObjectModel.ReportExprHost reportExprHost, Microsoft.ReportingServices.ReportProcessing.OnDemandReportObjectModel.ObjectModelImpl reportObjectModel)    Unknown
(see the attachment for the full stack trace)

I tried to create a simple ReportServices report in the VS itself and it displayed without errors.

I tried uninstalling older SSDT and Visual Studio versions and completely reinstalling the latest version, including switching from the "integrated shell" to VS 2015 Community and installing SSDT on top of that. I tried devenv.exe /resetuserdata too. This didn't help at all.

The Tools -> Options -> BIDS Helper -> Version says SSDTBI2016 (13.0.1701.8) for Visual Studio 2015 was detected and doesn't display any errors. Other features not relying on the report viewer (such as smart diff and dimension health check) appear to work fine.

I'm out of ideas at this point, other than reinstalling the system from scratch, and would greatly appreciate any pointers.

VS 2015 update 3 (Community; 14.0.25431.01), SSDT 16.5, BIDSHelper 2.0.1 (obtained from the VS Gallery), Windows 7 SP1

file attachments

Closed Jun 2 at 2:39 AM by furmangg


furmangg wrote Feb 3 at 12:03 AM

I actually have this same issue on my laptop (making it mighty hard to develop any feature with reports in BIDS Helper) however none of the rest of the BIDS Helper dev team has this issue and no other computers where we tested have it.

So please describe your laptop? What OS? What other versions of Visual Studio?

Let me debug some more on my laptop and I may send more questions.

nickolayp wrote Feb 3 at 12:47 AM

It's an old Lenovo laptop with Windows 7 "Enterprise N" SP1, with all updates installed.

Since it's old, the system accumulated a lot of cruft. I had VS 2010 Express installed (for the C++ compiler) and VS2012/2015 (integrated/isolated shells) for the corresponding versions of SSDT-BI and SSMS.

Before the recent version of BIDS Helper for VS2015 was available I had tried installing the previous version (and then uninstalled it).

There are also a number of SQL Server components left over over time (2008/2012/2014/2016; Compact 3.5/4.0). I uninstalled some of them, but I feel it doesn't make the situation better.

wrote Mar 9 at 10:44 PM

nickolayp wrote Apr 26 at 10:00 AM

FWIW, this reproduces on a new Windows 10 machine. I mistakenly installed VS 2017 Community first, and the most recent versions of SSMS and SSDT-BI (which as far as I understand installed the 2015 "shell"), then installed BIDS Helper from the marketplace - and it crashes on any report again.

I feel I'm missing something very simple - perhaps there's another component everyone else has installed (like maybe the database itself? something related to reporting services?)

furmangg wrote May 15 at 6:07 AM

Good news! I believe I have this fixed. I would love everyone on this thread to beta test. I'll try to send you all an email, but feel free to click furmangg and send me an email instead.

I will update this thread again once the fix is included in a public release.

nickolayp wrote May 15 at 12:42 PM

Great news indeed! I would love to test the beta version, I received the above comment and the additional private message, but I don't see the email I should use for further communication. I'm fine with both using the comments here and e-mail. If you prefer e-mail, mine is

wrote Jun 2 at 2:39 AM

wrote Jun 2 at 2:39 AM