Hi.

Yes, that Q&A article is mine but wasn't seeing any traction.

Can you advise where "MaxCatalogConnectionPoolSizePerProcess" is configured?

Thanks again.

Hi Ken.

Thanks for this but I don't see how it includes the SUM([value]) in the SELECT statement.

Pete

Hi Brian; thanks for the response.

Unfortunately, the [rn] is a pseudo-column from the ROW_NUMBER() window function so I'd have to store the output into a temporary table in order to...

My "resolution" was to change the code to something of the form:

CREATE FUNCTION
    [dbo].[fnc_Rule1]()
RETURNS
    [int]
AS
BEGIN
    DECLARE @result [int]
...

Hi Jeffrey.

Thanks for the feedback. In my *real* use case, the index hint *is* needed or the query takes an age to run whereas with the index hint it's pretty...

Unfortunately, this server doesn't have SQL Server installed. It only has the SSAS instance.

Could I copy them to a different server and read them from there?

Thanks Jo. Unfortunately that didn't resolve the problem. The report server logs only detail what I included in the original post - aside from a stack trace that's no good...

All through HTTPS and, according to Edge, the certificate is valid.

Thanks frederico_fonseca. That was exactly what I needed. Annoying that this still isn't in the GUI, even though it adds the parameter (with true) to the command line when scripting...

Nope. Nothing in the package is doing that. The package doesn't even start running.

You've misread. Running the package (under a proxy) runs it synchronously - not what I want.

Running the stored procedures runs it asynchronously - but this errors. 

Thanks for the link. However T-SQL steps cannot be run under a proxy and using a proxy on the SSIS step won't make it run asynchronously.

May have found an answer.

I hadn't opened SQL Server Configuration Manager since the upgrade but when I tried, I got the error:

Cannot connect to WMI provider

Googling that, I found the...

Thanks for the response. That registry hive was missing from the server after the upgrade - maybe "HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds" got replaced by the upgrade?

However we tried recreating it previously but that...

I'd already found that and it doesn't work. If I run PowerShell, I get:

Scope          ExecutionPolicy
-----   ...