How to Install Microsoft SQL Server 2017: SSRS 2017 Not Supported on a Domain Controller

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

I often create two types of demo or test environment; one will have multiple virtual machiens createdin order to replicate a typical live environment, and the second has only a single virtual machine.

While prepping a test environment of the latter type in readiness for the launch of Microsoft Dynamics GP 2018 RTM, I encountered a problem with SSRS:

Microsoft SQL Server 2017 Reporting Services installation issue

Microsoft SQL Server 2017 Reporting Services

Setup blocked

The following issues blocked Setup

Installing Reporting Services on a domain controller is not supported

This is a major departure from SQL Server 2016 and previous, all of which allowed SSRS to be installed on a Domain Controller; for most systems this will be absolutely fine, but I’ll no longer be able to use single virtual machine demo or test environments.

Click to show/hide the How to Install Microsoft SQL Server 2017 Series Index

How to Install Microsoft SQL Server 2017: Avoiding Max Request Length Error in SSRS

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

In the last post I configured SSRS, which is fine for most uses. However, Microsoft Dynamics GP requires an additional configuration step. This is not done through the Report Server Configuration Manager, but by editing a config file.

The reason this is required is because of an error produced when deploying the SSRS reports. If you do not change the setting, the error you will receive is the following:

GP – The deployment has exceeded the maximum request length allowed by the target server. Set maxRequestLength="20690" in the web.config file and try deploying again.

Microsoft Dynamics GP

The deployment has exceeded the maximum request length allowed by the target server. Set maxRequestLength="20690" in the web.config file and try deploying again.

To avoid this error, requires the SSRS web.config file to be amended. The file, for SQL Server Reporting Services 2017, is located in C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer.

Below is a snippet of code from the web.config file with the added node highlighted:

<httpRuntime executionTimeout="9000" requestValidationMode="2.0" maxRequestLength="20690" />

Add the above, save the file, and SSRS is now ready for the Microsoft Dynamics GP reporting services reports to be deployed.

Click to show/hide the How to Install Microsoft SQL Server 2017 Series Index

Hands On With MDGP 2018 RTM: Confirmed – SQL Server 2017 Is Supported

Microsoft Dynamics GPMicrosoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

Just a quick post to confirm that Microsoft SQL Server 2017 is supported by Microsoft Dynamics GP 2018 RTM; I currently have Dynamics GP 2018 installing onto SQL Server 2017.

This was the word on the grapevine, but it’s good to see it is the case. I have a couple of implementation projects about to start, where the client is holding off awaiting confirmation. Fortunately, I can now give this on Monday.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

How to Install Microsoft SQL Server 2017: Configure SQL Server Reporting Services

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

In the last post I covered the installation of SQL Server Reporting Services (SSRS); in this post I am going to cover the basic configuration of SSRS.

To complete the configuration, launch the Report Server Configuration Manager; ensure the Server Name is set to the correct name and click the Connect button:

The Report Server Configuration Connection

Continue reading “How to Install Microsoft SQL Server 2017: Configure SQL Server Reporting Services”

How to Install Microsoft SQL Server 2017: Install SQL Server Reporting Services

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

Microsoft Dynamics GP ships with some Reporting Services Reports by default, so this componenbt of SQL Server also needs to be installed. As with SSMS, SQL Server Reporting Services (SSRS) is not installed by the main installer, but, again like SSMS, it is available via a download accessible tyhrough the setup utility.

To install SSRS, laucnh the main setup utility of SQL Server, click Installation and then select Install SQL Server Reporting Services:

SQL Server Installation Center - Installation

Continue reading “How to Install Microsoft SQL Server 2017: Install SQL Server Reporting Services”

How To Install Microsoft SQL Server 2017: Install SQL Server Management Studio

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

The next component to be installed, is SQL Server Management Studio (SSMS). This was the first of the components which Microsoft removed from the main installer. However, to install it, we can launch the download page from the Setup utility.

Once launched, click Installation and then select Install SQL Server Management Tools:

SQL Server Installation Center - Installation

Continue reading “How To Install Microsoft SQL Server 2017: Install SQL Server Management Studio”

How to Install Microsoft SQL Server 2017: Install the Database Engine Services

Microsoft Dynamics GPIn this short series of posts, I am going to be covering the installation of Microsoft SQL Server 2017; the installation process for this version is somewhat different to previous ones, in that SQL Server Management Studio and SQL Server Reporting Services have been separated out from the main installer.

The series index can be found here. I am not a SQL expert and this series of posts is intended only for use on demo or test environment and not production ones.

In this, the first post of the series, I am going to install the core part of Microsoft SQL Server 2017, which is the Database Engine Services. To do this double click the Setup.exe on the installation media.

Click Installation and then select New SQL Server stand-alone installation or add features to an existing installation:

SQL Server Installation Center - Installation

Continue reading “How to Install Microsoft SQL Server 2017: Install the Database Engine Services”

How To Install Microsoft SQL Server 2017: Series Index

Microsoft Dynamics GPWith a new version of Microsoft Dynamics GP about to be released, it’s time to refresh my test environment; as well as the upcoming release of Microsoft Dynamics GP 2018, Microsoft SQL Server 2017 is also now available.

In this short series of posts, I am going to cover the installation of the SQL Server components needed for an installation of a demo/test Microsoft Dynamics GP 2018 (not including SSAS or SSIS).

I am not a SQL expert and this series of posts is intended only for use on demo or test environments and not production ones.

How to Install Microsoft SQL Server 2017
Install the Database Engine Services
How To Install Microsoft SQL Server 2017: Install SQL Server Management Studio
Install SQL Server Reporting Services
Configure SQL Server Reporting Services
Avoiding Max Request Length Error in SSRS
SSRS 2017 Not Supported on a Domain Controller

Find Column In SQL Using INFORMATION_SCHEMA

Microsoft Dynamics GPLast year I posted a script to find tables containing a particular column using sys objects. Steve Endow of Dynamics GP Land suggested using the INFORMATION_SCHEMA instead as he found it easier to use.

I’ve recently had reason to search for tables with a particular column in them, so I took a look at using a script using INFORMATION_SCHEMA.COLUMNS. However, when taking a detailed look at the results I found a few anomalies; the issue was that INFORMATION_SCHEMA.COLUMNS returns results for columns in not only tables, but also views. Which does make sense as both tables and views have columns. For what I was working on I needed a list of only tables.

I did a little exploring of the INFORMATION_SCHEMA and determined that I could join to INFORMATION_SCHEMA.TABLES and filter on TABLE_TYPE <> ‘VIEW’ to get a result set of only tables:

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
DECLARE @ColumnToFind VARCHAR(20) = 'PAYRCORD'
SELECT
	['Tables'].TABLE_SCHEMA AS 'Schema'
	,['Tables'].TABLE_NAME AS 'Table'
FROM
	INFORMATION_SCHEMA.COLUMNS AS ['Columms']
INNER JOIN
	INFORMATION_SCHEMA.TABLES AS ['Tables']
		ON
			['Tables'].TABLE_CATALOG = ['Columms'].TABLE_CATALOG
		AND
			['Tables'].TABLE_SCHEMA = ['Columms'].TABLE_SCHEMA
		AND
			['Tables'].TABLE_NAME = ['Columms'].TABLE_NAME
		AND
			['Tables'].TABLE_TYPE <> 'VIEW'
WHERE
	COLUMN_NAME = @ColumnToFind
ORDER BY
	'Schema'
	,'Table'

In the original posts script I was using the sys objects directly, but was filtering out the views by joining to sys.tables which contains only tables. Both the original script and the above one return exactly the same result set.

So, what’s the difference?

INFORMATION_SCHEMA, or System Information Schema Views to give the full name, is one of several methods SQL Server provides to get an internal, system table-independent view of the SQL Server metadata. Information schema views enable applications to work correctly although significant changes may have been made to the underlying system tables. The information schema views included in SQL Server originally complied with the ISO standard definition for the INFORMATION_SCHEMA, but appear to have diverged from the standard as new standards have been introduced.

The metadata returned by INFORMATION_SCHEMA, comes from the sys objects. So by using the former you are getting information from the latter, but in a way which should be future proofed against database changes.

Workflow Error Sending Email: “Execution Of User Code In The dotNET Framework Is Disabled”

Microsoft Dynamics GPThis has come up twice fairly recently. In the first case it was following an upgrade to Microsoft Dynamics GP 2016 and workflow was being introduced for the first time, and in the second it was when a client had created a new test system:

Execution Of User Code In The dotNET Framework Is Disabled

Microsoft Dynamics GP

[Microsoft][SQL Server Native Client 11.0][SQL Server]Execution of user code in the .NET Framework is disabled. Enable "clr enabled" configuration option.

Continue reading “Workflow Error Sending Email: “Execution Of User Code In The dotNET Framework Is Disabled””