Article ID: 128447, created on Feb 24, 2016, last review on Feb 24, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

The task to drop database user fails with the following output:

Destination host 'mpf.hosting.local' (#19), IP '10.10.10.10' : Provisioning request failed. IDispatch error #3092 [<response><errorContext description="The database principal owns a database role and cannot be dropped." code="0x80040e14" executeSeqNo="2"><errorSource namespace="SQL Provider" procedure="ExecSQL"/></errorContext></response>]

Cause

Microsoft SQL server cannot drop user if it owns schema or role.

Resolution

In order to fix the issue you need to change the owner of database in question via CCP under Database > Security > Roles > Database Roles;

If user own database scheme, you may use the following query executed on target Microsoft SQL server:

ALTER AUTHORIZATION ON SCHEMA::%user_name% TO dbo;

Note: specify problematic user name in query above instead of %user_name%.

Search Words

The database principal owns a database role and cannot be dropped.

The database principal owns a database role and cannot be dropped." code="0x80040e14

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF