Moving one application from windows 2003 server to windows 2008 R2. The application uses Microsoft Report Viewer. After publishing the application and when I browse the web application, I get an error with web.config stating the Microsoft reviewer is not available. Will it be okay to download Report Reviewer 2005 redisrtibutables for consistency with what was installed on the older server, or should I install the latest Report Reviewer which is the 2010 SP1 version. Please let me know. Thanks,
Either option should be okay but the 2010 report viewer is a huge improvement and works really well.
Related
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
Client :
- Windows 7 SP1 32bit
- With SQL Express - Advance series installed (with VS2008)
Server:
- Database: SQL Server 2008R2 Enterprise Ed., 64bit
- OS: Windows Server 2008
I always get the message "To design IS packages in BIDS, BIDS has to be installed"
What am I missing here?
Really need your help guys, first time using VS much more the BIDS.
Thanks,
Elmer
You need to install BIDS on your client machine. BIDS is not included as part of Visual Studio, it is part of SQL Server (but runs in the Visual Studio shell). So get your SQL 2008R2 media and run the installation a new instance or add features. You don't need any of the Instance Features, but you should include the following Shared Features:
Business Intelligence Development Studio
Client tools Connectivity
Client tools SDK
Management Tools - Complete
SQL Client Connectivty SDK
We will migrate from Windows Server 2003 to Windows Server 2012.
My question is if we can use Team Foundation Server 2010 on the new server, or if we need to update to TFS 2012?
It appears that Sharepoint Foundation 2010 doesn't support Windows Server 2012, and I believe SQL 2012 doesn't work with TFS 2010, but if you can live without Sharepoint and you can use SQL 2008 R2 (or prior), you should be fine.
Take a look at: http://msdn.microsoft.com/en-us/library/vstudio/dd578592.aspx
Notice where it says:
Because Team Foundation Server installs SharePoint Foundation 2010 with the standard configuration, you can’t use it on Windows Server 2012. If you want to install Team Foundation Server on Windows Server 2012, use the advanced configuration and skip the installation of SharePoint Foundation 2010.
Regarding SQL 2012, take a look at this: http://blogs.msdn.com/b/bharry/archive/2013/01/11/tfs-2010-will-not-support-sql-2012.aspx
I am unable to get TFS 2010 running on Windows Server 2012 because TFS doesn't seem to recognize the IIS 6.0 compatibility mode. See:
Error installing TFS 2010 in Windows Server 2012
and
Application Tier Configuration Failed For TFS 2010 on Windows Server 2012 R2
Magol and Adam (or anyone else), have you got it running successfully?
I have multiple reports that have been created over the years and anytime a RDLC file is opened in the VS2010, it is asking for an upgrade. I have seen many posts about changing the .config file, but these files are not using config files since they are application based. I have Microsoft.ReportViewer.Winforms, .Common, .ProcessingObjectModel and, .WebForms 9.0 and 8.0 installed on the lab machine.
After upgrading a report and trying to run it on the lab machine ( ms server 2008) I am returned an error of: "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded.
Does Report Viewer 2010 Redistributable Package fix this issue? I cannot find a distinct answer. If not, is there another workaround without changing server modes from local to server?
You should really be opening those using the SQL Server Business Intelligence Development Studio (BIDS), which can be found under the Microsoft SQL Server 2008R2 folder on the Programs menu.
I have a computer (windows 7) which already has SSRS 2008 installed. We also need to install SSRS 2005 on it. When I run installer for 2005 I see "reporting service" option greyed out. What could be the reason? How can install ssrs 2005 on this machine?
They can certainly coexist, I have had servers with 3 versions on them whilst migrating reports.
It's possible that you've installed it with the same instance name which would then make reporting services think that it is already installed and not let you. There could also be an issue with IIS ports.
When I've needed to do this I've installed them the other way around (2005 first then 2008 then 2008 R2) which might be an issue as well due to shared components.
Is there a particular reason you would want to use 2005? Any existing reports that you may have that are 2005 should work fine on 2008.
As Davos indicates they will coexist but you would have to uninstall 2008, then install 2005, and then reinstall 2008.