Servicing Director LSCNFG FixRights Error: "Cannot drop schema 'LoanServicing' because ..."

Servicing Director LSCNFG FixRights Error: "Cannot drop schema 'LoanServicing' because ..."

Execute with results failed for Database 'Service'. An exception occurred while executing a Transact-SQL statement or batch.

Cannot drop schema 'LoanServicing' because it is being referenced by object '<object name>'

Root Cause:

The LSCNFG FixRights option will drop/remove the Servicing Director created SQL logins, users, and related security objects, and then rebuilt them back to the default configuration. 
This error indicates some non-default object in your database unexpectedly is owned by or referenced by the Servicing Director login named 'LoanServicing'.

Workaround:

This information is for your local IT or system administrator:

  1. The Servicing Director primary login is named LoanServicing, and normally the login LoanServicing has DBO access to the Service database by default.
  2. All the Servicing Director created objects in the database will be owned by DBO.
  3. This error usually means some other object is owned by the LoanServicing login rather than DBO. This can happen when a customer creates a custom object in the database and happens to set the product login LoanServicing as the owner, which would be the incorrect setting.
  4. Locate the object referenced in your database, and change the object so it is not owned by or referenced by the LoanServicing login.  For example, change the owner to DBO or some other security object.
  5. If necessary, save all the information about the object you can, and consider removing the object. If the object is a SQL security object, such as a Schema or User or Role, the LSCNFG with FixRights will rebuild all the required Servicing Director security objects.

ArticleNumber:

000043383