Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SSIS Catalog - All Executions report only shows #Error in all headings and hyperlinks

I'm running an SSIS package on a recent install of SQL Server 2016. Recently the All Axecutions report of the Integrations Services Catalogs SSISDB started looking like the screenshot below. The package that is executed on a 5 minute basis runs fine. No errors. I can see the data being transferred as expected. Something is wrong with this report. I did some searching around and can't seem to find anything.

Anybody have any ideas as to what is wrong? Why is it showing #Error everywhere?

enter image description here

like image 738
SmokerJones Avatar asked Jul 21 '17 06:07

SmokerJones


People also ask

What details does Integration Services dashboard report specify?

The Integration Services Dashboard report provides an overview of all the package executions on the SQL Server instance. For each package that has run on the server, the dashboard allows you to "zoom in" to find specific details on package execution errors that may have occurred.

How do I find SSIS execution report?

Several reports are built into SSMS and query the SSIS catalog. The easiest way to view the reports for a package is to right-click on the package and select Reports ⇒ Standard Reports ⇒ All Executions (see below screenshot). The All Executions report shows the package execution history.

How do I enable progress reporting in SSIS?

To enable or disable the display of messages on the Progress tab, toggle the Debug Progress Reporting option on the SSIS menu.


2 Answers

Solution: Restart SSMS.

I can reproduce this error with on SSMS 13.0.16106.4 / SQL Server 13.0.4206.0 (Although the reports was working for a period, the the issue came back).

With the SQL same user, but running SSMS 12.0.5000.0 (from a remote desktop) the reports were fine.

Another user with SSMS 14.0.17177.0 has never had the issue.

Restarting the server had no effect.

I restarted SSMS 13.0.16106.4, which solved the issue. This could be a SSMS memory issue.

Also posted on: https://connect.microsoft.com/SQLServer/feedback/details/3103853/ssis-built-in-execution-reports-are-broken-in-ssms-2016-v13-0-15800-18

like image 160
Martin Thøgersen Avatar answered Sep 21 '22 21:09

Martin Thøgersen


Using SSMS Microsoft SQL Server Management Studio 14.0.17285.0. Solved this by closing SSMS and restarting it.

like image 34
Ade Avatar answered Sep 20 '22 21:09

Ade