CODEWITHSUNDEEP
sql-serverssis
SmokerJones
SmokerJones

Reputation: 333

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

Upvotes: 24

Views: 13269

Answers (5)

jim
jim

Reputation: 456

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!

Upvotes: 0

Ade
Ade

Reputation: 101

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

Upvotes: 7

Nick.Mc
Nick.Mc

Reputation: 19184

I had this issue. Turns out I had dropped some windows groups from the database I was loading data into (which was on a completely different server). When I added them back, the reports worked and didn't show #error

This makes absolutely no sense of course, but I thought I'd document it in case it helps or jogs someones memory

Upvotes: 0

Martin Thøgersen
Martin Thøgersen

Reputation: 1639

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

Upvotes: 29

James Bourne
James Bourne

Reputation: 123

I had this exact same problem and initially thought it was due to using the latest SSMS package - 17.1 on Windows 10 - but others with the same setup were not getting the errors.

I then ran the configuration for SSRS (which had been installed but not configured). This created the reporting server databases but made no difference. I don't think SSIS reporting uses SSRS anyway but not sure.

I then ran Windows update and it installed latest .NET 4.7 packages.

After a re-boot SSIS reporting was back to normal!

So one or combination of what I did above together with a re-boot made the difference but equally it may just have been a re-boot that was required.

This was on my development machine and I have been backing up and restoring the SSISDB from production to my development environment - this may have a bearing on attempting to re-producing this problem but I have not experienced it since and after fully deleting and restoring the SSISDB.

Hope that helps?

Upvotes: 1

Related Questions