Think I figured this one out on my own... the transaction logs were failing to make the report file; properties of the maintenance plan were pointing to the old backup...

That is strange... I know I've connected to SQL 2005 from a SQL 2016 SSMS version without any problems.  mind you that isn't for a data import/export.
I'd still recommend...

Possibly a dumb question, but are you sure you are putting it into the proper table on the destination side?  I think by default it dumps it into dbo.query.

That is a big chunk to bite off.
First, I would determine if you want to host the SQL yourself or cloud hosting.  Depending on the required uptime (which I...

I don't see anything in that trigger that should cause any failure unless, as you suggested,  somebody modified the trigger and rolled back their changes OR the application was updated...

If I understand correctly, you have a SQL job that calls multiple things, one of which is an SSIS package that sometimes fails and you want it to continue when...

Not to pick a fight, but what if his company doesn't follow ISO 11179 naming conventions?  Or the third party software he purchased doesn't follow those?  Heck, the ISO 11179...

Ok, so to confirm - there is only 1 logon trigger, correct?

If so, and that is the entire query, I would still create a logging table to watch...

I would create a logging table and modify the trigger to dump the user and program into the logging table table and any other useful infromation you want for logging...

If I am understanding the issue correctly, you have 2 reports that you want to merge into 1?

Why not just use multiple data sources in a single report?...