Reboot of the server resolved the issue.

The query: "SELECT 1" fails to export to PDF.  It's not data related. Also there's only 2 of us that would change these reports and the other person was on...

Tech guys said no Windows updates were installed.

Everything I've tested works fine for other formats, it's just PDF. Maybe there was an automated update.

The only thing I haven't tried yet...

Open the package open the script and resave it, should be OK unless it was written in VB. If so you'll need to re-write it in C#. This was our...

Ok so I've confirmed now the process of upgrading a ReportServer database to a new version of SSRS is handled by the SSRS service.

I backed up a 2017 set of...

I'm going to give this process a try.

https://www.mssqltips.com/sqlservertip/6323/move-sql-reporting-services-to-another-server/

Ok yeah I guess I'm not talking about upgrading SSRS I'm talking about moving the SSRS databases, reports, subscriptions, etc.... to a new server which is a higher version. So...

I'm not really sure what you're after but it seems like maybe you could just create a derived columns.

new column, name: dc_ImpressionsValue

Expression:  type == "Impressions" ? value : NULL (need...

This is "resolved". Our experience with Microsoft ended the same as the previous comment. Stager the job start times. We actually did this a few weeks ago and haven't seen the...

You can create a couple variables and set them with the expression parameter they will evaluate at run time.

Then have an Exec SQL Task preferably setup with an ADO.Net...

Makes me wonder why the occurrences dropped after patching.

I guess if it works. Easy non-impactful change so worth a shot... we'll start changing jobs today and see how it goes.

Thank...

SQL 2019 CU16 removes the Log4J files

https://support.microsoft.com/en-us/topic/kb5011644-cumulative-update-16-for-sql-server-2019-74377be1-4340-4445-93a7-ff843d346896#fixes

• This reply was modified 2 years, 7 months ago by  TangoVictor.

Update:

No resolution yet, but we are also working with MS support now. Their feeling on this seems to point at a Windows server issue. We've sent logs to them using...

Same for us, this error first appeared after we migrated from SQL 2016/Win 2016 to SQL2019/Win 2019

We just did a straight migration using dbatools migration cmdlets to move everything to...

Sounds great. Can I asked how you captured the log?