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?
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
Using SSMS Microsoft SQL Server Management Studio 14.0.17285.0. Solved this by closing SSMS and restarting it.
RE: "I restarted SSMS 13.0.16106.4, which solved the issue. This could be a SSMS memory issue." from @James Bourne
RE: "Using SSMS Microsoft SQL Server Management Studio 14.0.17285.0. Solved this by closing SSMS and restarting it." from @Ade
I had some very large nHibernate queries (captured from Extended Events) open in a couple of SSMS tabs. I closed each tab and restarted SSMS version 18.8.
Problem solved!
