Fix for ‘The database principal owns a schema in the database, and cannot be dropped’ Error

Shiva Manjunath — Wed, 28 Mar 2007 01:30:27 +0000

In SQL Server 2005, if you try to drop a database user by right-clicking the user name and clicking Delete, you may encounter an error as follows.

“The database principal owns a schema in the database, and cannot be dropped. (Microsoft SQL Server, Error: 15138)”

The reason for this is that in SQL Server 2005, if a user is associated with a Schema, then that user has to be first replaced by another user in the schema before you can drop the user from the database.

Fix the Error

In SQL Server 2005 Management Studio, expand the node

Database > yourdatabasename > Security and then click Schemas. On the right pane, you will see a name value pairs list of the schemas and the corresponding owners.

For one or more of the schemas, you should see the user you are trying to drop listed as the owner. For each of these schemas, do the following.

Right click the schema, and click Properties. In the schema owner box, type the name of the schema, ex. in the following, I would type db_admin over the mynewcommunity_admin.
Click OK.
After you do this for all schemas that the user you are trying to drop is the owner of, you should see something like this.

Now, if you right click the user and click Delete, you should be able to successfully drop the user from the database.

Fix for ‘XML Parsing Error: not well-formed Line Number 1, Column 2′ Error

Shiva Manjunath — Tue, 27 Mar 2007 01:33:41 +0000

When you access an ASP.NET page in your browser, you may get an XML Parsing Error that says that the XML is not well formed. The error message also displays the page directive statement present in the 1st line of the .aspx file. First we will fix this error, then we will look at one possible reason why you may be getting this error in ASP.NET.

Fix the ‘XML Parsing Error’

Click Start > Run, and type the following command depending on which ASP.NET framework is in use by the default web site in your IIS.

ASP.NET 2.0 Framework

%Windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

ASP.NET 1.1 Framework

%Windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

You should see a command window that is displayed briefly, that shows that ASP.NET is being installed. After the registration is successful, the window will be closed.

Now refresh the .aspx page that you got the XML Parser error for in the browser and your page should be rendered correctly.

Why did you get this error ?

I have seen this error happen to me in situations where I had installed IIS after the installing the .Net Framework. This make sense. If you install IIS after you install the .Net Framework, then the framework is not registered with IIS. So when a request for a .aspx page comes to IIS, it simply passes on the contents of the page as-is without processing it. So in effect, the browser receives the entire .aspx page’s code, tried to parse it as an XML file, encounters the parsing error at the second character in the page directive and stops.

Related: ASP.NET IIS Registration Tool