I have an issue on our SSRS 2016 printing from Dynamics CRM application. Reports render correctly, but every time I want to print by clicking the print icon, I am prompted to install the ActiveX print control.
Note
As a local admin user, I can install it and I can print, but I have to do it every single time. And normal users do not have that option. Also when I open manage add-ons I can see that it is installed.
Running:
Microsoft SQL Server 2016 (SP1-GDR) (KB4019089) - 13.0.4206.0 (X64) Jul 6 2017 07:55:03
Copyright (c) Microsoft Corporation Enterprise Edition:
Core-based Licensing (64-bit) on Windows Server 2016 Standard 6.3 <X64>
(Build 14393: ) (Hypervisor)
enter image description here
Related
I have an SSRS report project I'm working on in Visual Studio 2015, and I am unable to deploy my reports to the correct target server version.
The reports need to be able to deploy and run on SQL Server 2012, 2014 and 2016. Visual Studio 2015 allows for a Target Server Version option for the project of 2008R2, 2012, or 2014, which is what the target server version of the project is set to. The designer automatically upgraded the source RDL file schema to the 2016 version of the report once you open and do anything within it. I understand this part is by design.
The problem comes when you build the report. The build output files in the \bin\Debug or \bin\Release folders are not targeted to the correct server version. The following tag looks like it updates correctly in the output files:
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
However, the build fails to remove and leaves behind all of the other SSRS 2016 tags within the built RDL files, and as such cannot be deployed to SSRS 2012 or 2014.
I have Visual Studio 2015 v 14.0.25431.01 installed with SQL Server Data Tools v14.0.60812.0 with SQL Server Reporting Services 13.0.1700.68.
Is there something that I'm missing that needs to be done as well besides setting Target Server Version to "2008R2, 2012, or 2014" to get it to build to the correct Target Server Version?
I had this same problem. What I needed to do to resolve this was
Clean the project
Under Project > Properties > General set TargetServerVersion to "SQL Server 2008"
Set TargetServerVersion to "SQL Server 2008 R2, 2012 or 2014"
Rebuild the project
Your project should now deploy to the correct version
We are planning to upgrade from SQL Server 2014 and Visual Studio 2013 to SQL Server 2016 and Visual Studio 2015.
The error message:
[IBM][System i Access ODBC Driver]Communication link failure.
comm rc=25202 - CWBCO1034 - SSL error, function returned 25202
Background
We have an SSIS project which connects to an IBM DB2 server and retrieves data. This has been working for years.
The working setup looks like this:
Windows 10
Visual Studio 2013
SQL Server Data Tools for Visual Studio 2013
IBM i Access for Windows, version 7 Release 1
A DSN pointing to the IBM DB2 server
ADO.NET Connection Manager with ODBC Data Provider pointing to the DSN mentioned above.
SSL enabled on the DSN.
If we on the same machine use Visual Studio 2015 and subsequently SQL Server Data Tools 2015, it no longer works. Everything else is the same!
As soon as the package is opened and SSIS starts to validate the connection managers the error message arises.
I have SQL Server Replication running between a Publisher and 2 subscribers.
Publisher: Microsoft SQL Server 2008 (SP3) - 10.0.5538.0 (X64)
Apr 3 2015 14:50:02
Copyright (c) 1988-2008 Microsoft Corporation
Workgroup Edition (64-bit) on Windows NT 6.1 (Build 7600: ) (VM)
Subscriber: Microsoft SQL Server 2008 (SP3) - 10.0.5538.0 (X64)
Apr 3 2015 14:50:02
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (VM)
The server containing the subscriber database failed and had to be rebuilt. I restored the replication with the subscriber database and everything ran fine for about a day.
Now I am receiving the error: "Cannot perform alter on 'dbo.MyTableName' because it is an incompatible object type."
I ran SQL Profiler and found that immediately following a series of calls to sp_MSunmarkschemaobject. It is trying to run an ALTER VIEW dbo.MyTableName statement.
I've verified that dbo.MyTableName is a table not a view on both the Publisher and the Subscriber.
A little background, MyTableName was originally a view in the database, but was converted to a table, but this was over 3 years ago and replication had been working fine until the server went down.
Also of note is there is a second subscriber where everything is working fine.
Any help or insight would be appreciated.
Okay, this is strange.
I installed Windows 8 and SQL Server 2008. The database I am working with has FileStream enabled and so I need to enable FileStream. And so, I did:
EXEC sp_configure filestream_access_level, 2
RECONFIGURE
It didn't work.
So I tried using the UI in SQL Server Management Studio. Like this:
Notice under configured value it is displaying "full access"
And under "running values":
And notice under "running values" it is displaying "disabled".
So I did:
Ran RECONFIGURE, it returns Command(s) completed successfully. Didn't work.
Restart SQL Server 2008. Didn't work.
Restart machine. Didn't work as well.
Now I wonder if I RECONFIGURE is broken or my UI is broken. So I tried changing Default Language to UK - English and ran RECONFIGURE. It worked! The language changed to UK under "running values".
So I guess the problem is Filestream access changes didn't get applied. But why?
I am running Windows 8 64 bit and this version of SQL Server:
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64) Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit)
on Windows NT 6.2 <X64> (Build 9200: )
filestream access level Server Configuration Option:
Before this option has any effect, the Windows administration settings for FILESTREAM must be enabled. You can enable these settings when you install SQL Server or by using SQL Server Configuration Manager.
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?