Error creating this GDB. The DEFAUILT_SCHEMA cannot be used w/ a Windows group...

[MaximSilin]

Hi Everyone,

One of my clients has been experiencing the following error:

"Error creating this geodatabase. The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys".

The error occurs when the client is trying to create a new SDE geodatabase under Database Server connection (connection itself is fine) within ArcCatalog or Catalog window in ArcMap. The funny thing is, that when, upon receiving the above error, we check it in the SQL Server Management Studio - the database is there, but not visible to ArcGIS. The client is running ArcSDE Personal with SQL Server 2008 Express R2. I've checked to make sure that the user account is not mapped to any certificates or asymmetric keys, nor there are any credentials setup on SQL Server instance (I guess that is what the 'Windows group' reference in the above message stands for, isn't it?).
On a side note, while we don't have a clear evidence if this is true or not, the client says that the issue has started after one of his colleagues upgraded from SQL Server 2008 Express to SQL Server 2008 Express R2. Not sure if that might have affected anything.

Has anyone seen this issue before? Any ideas are welcome.

Thanks,
Max

[JakeSkinner]

Hi Max,

It looks like you added a windows/domain group to you SQL Server Instance and then set a default schema for this group.  This is not allowed:

http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/7d46a024-7ed5-4c9b-b091-3640dc04f5a...

Try removing the default schema from the windows group and then try creating the database.

[MaximSilin]

Try removing the default schema from the windows group and then try creating the database.

Jake,
Yes, I've seen that MSDN post, but how do I remove the default schema from a windows group? And how do I know which group it is?
Thanks,
Max

[MaximSilin]

Furthermore, would such case affect any users on the SQL Server instance or only those who are part of that Windows/domain group?

[JakeSkinner]

You can find out which Windows Group has the default schema using SQL Server Management Studio.  Navigate to the database > Security > Users.  Right-click on the Windows Group > Properties.  Here it will state what the default schema is.  You can remove the default schema from the Windows Group by deleting the schema from the geodatabase by going to the database > Security > Schemas > right-click on the schema > Delete.

The users that are a part of this Windows Group should still be able to connect to the geodatabase successfully.

[MaximSilin]

You can find out which Windows Group has the default schema using SQL Server Management Studio.  Navigate to the database > Security > Users.  Right-click on the Windows Group > Properties.  Here it will state what the default schema is.  You can remove the default schema from the Windows Group by deleting the schema from the geodatabase by going to the database > Security > Schemas > right-click on the schema > Delete.

The users that are a part of this Windows Group should still be able to connect to the geodatabase successfully.

Okay, so let me clarify something here: the error similar to the one I've referenced above is what one would get if tried to assign a Default Schema to a Windows Group in SQL Server Management Studio (see attached screenshot) on an existing database. But in my case the error comes up upon trying to create a NEW geodatabase through ArcCatalog. Following the error message, the new database appears in the list of Databases in the SQL Server Management Studio, but there are no tables in it at all.
The issue occurs on multiple domain users.

[JakeSkinner]

Right-click on your SQL Server instance in the Catalog window > Permissions.  Do you have any Windows Groups listed here?  If you do, temporarily remove the windows group.  Afterwards, try creating the geodatabase.  If this works add the Windows Group back to the instance.