I'm having an issue with the soft render of a simple report in both SSDT and Report Builder environments in 2016. I'm sure there is a sample solution but I'm unable to find a solution on the web/forum.
I'm actually just using a simple tablix from AdventureworksDW2016CTP3 with a couple of fields inserted. The data might initially display but disappears after modifying the field length or switching between design and preview. More interestingly, the report views perfectly when utilising print preview and it exports to .pdf correctly... and also views correctly when deployed to the report server.
All is installed locally on my laptop with Windows 10 and Administrator privileges. I have repaired and upgraded Visual Studio and SSDT to the latest version but without any luck.
I've added images of the simple design, soft render and print preview as well as Visual Studio System Info at the bottom.
Thanks
Visual Studio Info
Microsoft Visual Studio 2015 Shell (Integrated) Version 14.0.25420.01 Update 3
Microsoft .NET Framework Version 4.6.01586
SQL Server Analysis Services 13.0.1701.8
Microsoft SQL Server Analysis Services Designer Version 13.0.1701.8
SQL Server Data Tools 14.0.61021.0
Microsoft SQL Server Data Tools
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer Version 13.0.1601.5
SQL Server Reporting Services 13.0.1701.8
Microsoft SQL Server Reporting Services Designers Version 13.0.1701.8
Images
Design Images
Soft Render / HTML
Print Render
After much testing it appears that the problem came down to my graphics driver - Intel HD Graphics 5500.
The problem still occurred after I updated the driver so I then disabled it... which solved the problem. I then reinstalled the driver and all is now working as expected.
This link gave me the initial indication of the issue:
https://support.microsoft.com/en-us/help/2894215/you-experience-performance-issues,-product-crashes,-or-rendering-issues-in-visual-studio-2015-and-visual-studio-2013
Related
For many versions I have a reporting services project in Visual Studio. The latest is Visual Studio 2013. I have installed Visual Studio 2017 community edition and it has the Microsoft Reporting Services Projects extension. It also says that it has Data Tools installed as part of VS (at least that's what it looks like). Yet my rptproj file will not be recognized by Visual studio 2017. Every document that I'm sent to says I need SqlServer Data Tools but is that now a separate program I have to use to deal with reports outside of Visual Studio? It makes no sense to me given that there is a reporting Services projects in VS. But that isn't working at all. I've tried creating a new project and copying the RDL over to it. It opens it and I can see designer but when I try to preview I get the dreeded " Unknown report version 9". Any help would be very very much appreciated.
Just download and install
https://learn.microsoft.com/en-gb/sql/ssdt/download-sql-server-data-tools-ssdt
SSDT will provide all the missing bits for VS2017. You will then be able to edit your reports in VS2017 but you will need to upgrade the solutions. You will be promoted to do this upgrade when you attempt to open the project/solution.
I am using SQL server 2008 express.
I have created one RDL file and i have used zen barcode to display barcode in my Report.
But when i deploys it to server then it is not displaying on browser.
I have also tried with sql server 2008 full version but still its not working.
But, I have another system in that system sql server 2008 full version is installed. And in that machine it is working fine.
I am attaching both system snap.
Please give me solution.
Thanks a lot in advance.
Hi that happen because your server need that font to working so you have to add this in Control Panel - Fonts.
I have a problem. This co-worker, whenever they open a BIDS project it gives her an error message:
...cannot be opened because its project type (.rptproj) is not
supported by this version of the application.
However, if I remote onto the computer using my login, it opens stuff just fine. The thing is, it was working for them for about 8-9 months. It just 'randomly' started doing this today. It also gives a similar error when creating new report projects.
Do you have an idea what the issue might be? I'm thinking maybe it's a configuration in the user profile? I mean, the computer obviously can open it up- just not for them. Has anyone experienced this and resolved it?
We are using the BIDS suite that comes with SQL Server. It is VS2008, we are running SQL Server 2008 R2.
Thanks in advance.
From Solved: project type (.rptproj) is not supported by this version of the application:
Install "Business Intelligence Development Studio" from the SQL Server 2008 installer.
See Business Intelligence Development Studio 2008 installation for more information on the installation.
I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation.
I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server.
I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.
So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue
So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:
Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.
The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.
I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.
Any help would be appreciated
Thanks,
Doug
This might help: How to edit SSRS 2008R2 Reports in Visual Studio 2012?
I have been working for a client who run SQL Server 2008 in their live environment. I had been working onsite for a period but now work from home. However, due to security, I cannot connect to the live setup, I can only connect to a test server. This server runs SQL Server 2012. I script any code and send it to the office for someone to deploy. The problem I have is I am now doing some reporting services work. They are only pretty basic reports, tablix controls, nothing fancy. Is is possible to build on 2012 and deploy to 2008? Can I do something with the .rdl file to make this work or is it not going to be feasible?
Thanks in advance
In the Properties of the ReportServer Project in Visual Studio you can set the target server version.
Right click the Project in the Solution Explorer pane and set the TargetServerVersion Property to the required version. This works for reports SQL Server Reporting Services 2008 onwards. The designer will then manage what features are available to avoid using features from a later version of SSRS.
The .rdl files are nicely formated XML. You can use your favorite diff tool to compare reports generated in either version of the tool.
I'm pretty sure that Microsoft doesn't support moving a newer RDL to an older version server.
There were huge changes to the .rdl format between 2005 and 2008, moderate changes between 2008 and 2008R2, but I haven't really looked into 2008R2 versus 2012. From what I've seen these should be smaller changes yet.
If you do this you are off of the golden supported brick road. Since this server is production, and you don't have a good way to test this, I would find a 2008 server to develop with. I wouldn't want my name connected with the possible problems that could come up with a hack to move the rdl backwards.