Looks like this was caused by an invalid certificate. No idea what was wrong with it but applying a newly-created certificate worked without issue.

Hi Jo.

HTTP works fine and I've configured all my reports, subscriptions, etc. without issue. It's only when trying to enable HTTPS that I hit a problem.

I've also attached a screenshot...

Just to verify this, how can I check the membership of the MSSQL$INSTANCENAME group? Can't...

Not that I'm aware of. I performed the install and selected the AD account to run the SQL Agent service which is currently the one in use.

Tim - There's an OnError event handler at the package level but that just does an INSERT into a log table

Not yet, Phil. I'm gonna collate some data from the [operation_messages] and see if that points me in a direction.

It shows the "For Loop Container" task.

The variables in each stack are unique to that stack (they're all named for the stack in which they exist).

This is failing when the package runs from a SQL Agent job.

I forgot to mention that *most of the time*, it works. We just get this failure occassionally.

Yeah I've already implemented a workaround in this case but wanted to know for future implementations where this might not be possible.

Grrr... Such a simple answer! For some reason I'd set it to 0.

Many thanks.

Thanks for that. There was a slight issue in that the day portion being returned was 2nd of the month for a date duration of 1 day - because 0...

Thanks for the feedback. Yes, the initial restore was greatly slower as the files were initialised but the regular refresh is obviously using pre-existing files so there's no speed improvements...

Thanks Grant. Yeah, that's what I thought re: a restoring DB.

I'll see if there are any infrastructure-level options available to us.

Thanks again.

Note: I've managed to make this work by changing "pattern2" to:

pattern2 = "[\x22\x27\x2c\x3f\x5c\x5c\x60]"

but I don't know why I need to escape the backslash in the pattern2 value...