I have installed SQL Server 2016 Standard along with SSRS 2017. I am using rs.exe tool for SSRS reports deployment.
When I try to execute rs.exe from command line, I am prompted to install .Net framework 3.5. While tool works after .Net FW 3.5 is installed - this is not something I want to do.
I have searched for similar questions and found out only this: https://social.msdn.microsoft.com/Forums/en-US/334685df-8899-4a53-9513-0b443fc485fe/rsexe-depends-on-net-35-but-sql-server-reporting-services-2017-system-reqs-dont-mention-it?forum=sqlreportingservices.
Also, no .Net framework 3.5 is listed in system requirements for Sql Server 2016 or SSRS 2017 (https://learn.microsoft.com/bs-cyrl-ba/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2016#hwswr)
So I wanted to ask:
Has anyone experienced the same situation? Do you need to actually install old .Net framework(2.0+3.5) to use that tool?
Any workarounds?
Related
How do I change the .NET framework of MS SQL Server 2012?
I have a SSIS package that has a script that cannot target .NET 4.0 due to using WebUtility.UrlEncode().
Will upgrading to 4.5 on the Server interfere with other stored procedures that are currently running (and targeting 4.0)?
I tried setting the target of the Script Task to 4.0 but WebUtility.UrlEncode isnt available for 4.0.
Two things at play here.
The first is the target setting for the SSIS Script Task/Component. You can change that up/down as the item requires.
That's a development setting by the way. When you deploy to the server, would need to ensure that server itself has an equivalent runtime on it.
Now, things get "weird" because for the 4.0 runtime framework, which we both have, there are developer versions within that version, from a Command Prompt if you typed
C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe you'd see what version there. For example, I see
Microsoft (R) Visual C# Compiler version 4.8.4084.0 for C# 5
How do I find the .NET version?
I am attempting to build a SQL CLR project in Visual Studio 2015 and I am calling a wcf service which targets the System.Runtime.Serialization.dll. I am having problems identifying the correct version of .NET to target in order to overcome this.
The sql version is:
name value
directory C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
version v4.0.30319
state CLR is initialized
I attempted to build the CLR against .NET version 4.
SQL refuses to install System.Runtime.Serialization.dll If I build against .NET version 3.5, I get
Msg 6586, Level 16, State 1, Line 8
Assembly 'System.Runtime.Serialization' could not be installed because existing policy would keep it from being used.
What version should I build against to overcome this?
SQL Server 2012 and newer uses CLR 4.0, which in turn is tied to .NET Framework versions 4.0 and above. You cannot use any .NET 2.0, 3.0, or 3.5 libraries in SQL Server 2012 or newer.
System.Runtime.Serialization is not in the Supported .NET Framework Libraries list, so you need to load it manually, and as UNSAFE. However, if that DLL is mixed mode and not pure MSIL, then it won't load since SQL Server's CLR host only works with pure MSIL libraries. I have found it best to just use HttpWebRequest and build the request XML manually and parse the response XML manually.
In the past, the ServiceModel DLL, and all of its dependencies, were pure MSIL and worked in SQL Server 2008 R2 (SQL Server 2005, 2008, and 2008 R2 are tied to CLR 2.0). But then, in CLR version 4.0, Microsoft added some dependencies to ServiceModel. One of them was the new Microsoft.VisualBasic.Activities.Compiler library (not a direct dependency, but via another, most likely Microsoft.Transactions.Bridge), which happens to contain unmanaged code (which cannot be loaded into SQL Server). Hence, everyone who had working WebService SQLCLR stuff running in 2008 R2 had it stop working upon upgrading to SQL Server 2012 or newer. Using HttpWebRequest works with an "approved" library that is guaranteed to always works across upgrades of the .NET Framework.
There are numerous questions already on here regarding these issues. I will try to find some and update this with a few of them.
Also, just FYI, the output shown in the question, which appears to be the results of executing: SELECT * FROM sys.dm_clr_properties;. Please be aware that the "version" shown, while often referred to as the Framework version, is actually just the CLR version, and those two things are not the same thing.
This might be a trivial error in my setup but I cannot seem to find where I went wrong in stalling SSDT 2013 with SQl Server and having the open to create a new database template
please see image
what I expect to be in the list in a sql template with the option to create a new database project
could someone tell me what i'm missing ?
Thanks in advance
For database projects you'll need to install a version of Visual Studio that supports it - in your case it looks like you ran the standalone SSDT-BI installer which installs SSIS, SSAS and SSRS templates. This doesn't include database project templates. What you need is to install one of the VS versions with support - there are 2 Express versions (Express for Web and Express for Windows Desktop) and 3 paid versions (Premium, Pro, Ultimate). Here is a quote from the SSDT blog post explaining this:
Visual Studio 2013 - VS 2013 now has SQL Server tooling built in and shipped as part of the core product. Database Projects, SQL tools (such as schema compare & data compare), and the online experiences through SSOX are all included with the RTM version. We have full project and SSOX support in VS Express for Web and Express for Windows Desktop, so we have discontinued our stand-alone integrated shell offering. We have a component update feed that will use VS Update to push notification to users. To manually check for updates, go to the Tools > Extensions and Updates... menu to open the dialog. We will continue to post announcements on our blog and forum that a release is available and what is included in that update.
What version of Visual Studio 2013 are you using? You need to have either the Ultimate, Premium or Pro version for SSDT (Link).
If you do have the right version of Visual Studio then you may need to re-run the installer and opt in to SQL Server Data Tools during setup.
I had this issue and resolved it several years ago. I needed to reinstall SSMS with Data Tools. Unfortunately I am encountering the same issue now, but luckily I had documented the issue at the time. I am finding that because there are newer versions of both VS and SSMS, it is hard to find the proper downloads.
From my documentation (3 years ago) None of the attempts to correct the Visual Studio install directly (SSDTBI_x86_ENU download from Microsoft) were successful, but once we did a complete reinstall of SQL Server 2014 which included the Data Tools, the needed template was available in the Add New Project dialog, and the previously incompatible projects found in GitHub******Report.sln were now compatible.
I have completed a WPF application in Visual Studio 2010 and SQL Server 2008 Express. I have also used Crystal Reports in my project. Now I need to deploy the application on client's systems. I assume that I will have to install the following pre-requisites first.
.Net Framework 4.0
MS SQL Server 2008 express (which may require .Net 2.0)
CR Runtime for .Net 4.0
Report Viewer
IS there a way so that everything installs on its own? I have tried selecting all the above as ** prerequisites**, but that gives me an error that CR Runtime msi not found. Can I also include all the files within my software in the bin folder?
Please give me suggestions.
you can download CRRuntime_32bit_13_0_1.msi from SAP website (google it) and place it in this location:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\Crystal Reports
for .NET Framework 4.0\
Has anyone managed to use vs2010 db build & deployment with teamcity without VS 2010 installed on build server?
I've registered the missing DLL's but it doesn't work and seems msdn suggest that we need vs installed on the build server.
Install the Microsoft Windows SDK v7.1 and any other requirements (example being ASP MVC 3 framework), etc. Make sure you have the correct versions of .NET installed as well. I am able to build and run unit tests, no issue without Visual Studio 2010 on a windows 2008 r2 64-bit server.