Found the answer. On the secondary server run:

SELECT [secondary_id] FROM [msdb].[dbo].[log_shipping_monitor_secondary] WHERE [secondary_server] = N'SECONDARY' AND [secondary_database] = N'DBNAME'

Turns out that the timeout setting for the data driven subscription is 30 seconds (default) and this is where the issue was occurring. Didn't realise that this is what was...

Alex. I had that thought but wasn’t sure if that would differentiate between the database being encrypted and the backup of the database being encrypted. Peter

RESOLVED:

It turned out that the availability group was the issue. Looking at sys.databases I saw that the log_reuse_desc was AVAILABILITY GROUP so it was replication that was preventing...

Hmm... Changing this through the normal services interface worked. When I set the account to use I got a message stating that the "log on as a service" right was...

Hi Sue. Yes I am.

Sorry for the delay; forgot to update this.
This turned out to be a strange issue. The publication database had a number of duplicated foreign keys on...

Hi Phil. No, we're not using that setting and we do have schema changes enabled for replication.

Thanks. I've also been looking at the log files for this (SQLFT*.LOG) and notice in a previous rebuild that there were messages of the form:

Error '0x80043630: The filter...

Your article led me to https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-fts-population-ranges-transact-sql.
Do you know whether the "processed_row_count" value in this view is accurate? If so then it's only 26% complete and has 6 more...

So was I 🙂

There is a database role called "admin", for example, which has:

ALTER on schemas a, b and c

CREATE TABLE

CREATE PROCEDURE

What I'd like to do is restrict the "CREATE...

Unfortunately I don't have flexibility on the roles - they're pre-defined within the application. Probably should have mentioned that.

<engage embarrassment mode>
This turned out to be (mostly) unrelated to replication and entirely unrelated to identity range inserts.
As I was refreshing the entire table, my first step was...

Thanks for this information, especially the referenced article.

I've been advised that it might be because the quantity of information being written has exceeded the configured ranges (this is...

Many thanks; this worked perfectly!