Thanks for all the suggestions.

For those that are interested and for those poor souls who may encounter this in the future - I thought I'd come back and report that...

We are getting the same stack dump with an access violation error on multiple instances on different machines and on different SQL versions. The thread at http://msdn.developer-works.com/article/12736742/alter+database+set+partner++ also...

"If the endpoints already exist then users do not need the CREATE ENDPOINT permission,"

I didn't give them CREATE ENDPOINT, I gave them CONNECT ON ENDPOINT and I know it is...

Hi Perry,

Yes, I know that the SQL Service account is the one that needs CONNECT ON ENDPOINT as detailed at https://msdn.microsoft.com/en-us/library/ms179306.aspx, however as to why - if you...

I have tested today with exactly the same results on SQL Server 2014, 2008 R2 and 2008 instances.

I have now granted connect on the endpoint to the Windows NT...

Thanks for the response, however please correct me if I'm wrong but the CREATE ENDPOINT permission is in relation to creating the mirroring endpoint that mirroring sessions will use, not...

Many thanks for your help Erland, it seems it was a database trigger that one of the developers has been adding. I am very relieved to have found the cause...

Yes, principal ID 6 is the Windows group I assigned to the database. I already know this and what the group is though, so this doesn't help me understand why...

Thanks for your suggestion Erland. The first query on sys.database_permissions confirms that Backup database and log are denied:

classclass_descmajor_idminor_idgrantee_principal_idgrantor_principal_idtypepermission_namestatestate_desc

0DATABASE0061BADBBACKUP DATABASEDDENY

0DATABASE0061BALOBACKUP LOGDDENY

The second query on sys.server_permissions yields no results and so doesn't...

PHYData DBA (8/8/2013)

---

stobe (8/8/2013)

---

PHYData DBA (8/8/2013)

---

stobe (8/8/2013)

---

Joie Andrew (8/8/2013)

---

Nice article. One thing though. You list this:

This is a misnomer. A full...

PHYData DBA (8/8/2013)

---

stobe (8/8/2013)

---

Joie Andrew (8/8/2013)

---

Nice article. One thing though. You list this:

This is a misnomer. A full backup restarts the...

Joie Andrew (8/8/2013)

---

Nice article. One thing though. You list this:

This is a misnomer. A full backup restarts the log chain. So...

It is strange, I have plenty of other 2005, 2008, 2008 R2 boxes where the cleanup tasks are working fine also.

Obviously I was only running the stored proc to try...

Yes, they are native/local backups. I am using the following syntax:

EXECUTE master.dbo.xp_delete_file 0,N'F:\<Path>',N'bak',N'2011-12-31T00:00:00',1

EXECUTE master.dbo.xp_delete_file 0,N'F:\<Path>\<Filename>.bak'

Thanks for the reply Perry,

As I said up top, I have also verified the backups using restore headeronly. This returned the details as expected and didn't complain of any issues...