Hi Chibaletoth,

When you wrote "once I set the Windows Authentication ", please, could you explain what you mean ? Do you set the Windows authentification in the connection string or in the connection form of SSMS or do you want to forbid the use of the SQL Server authentification ?

I do faced this issue many times, I think this happens when we install default mode as windows and not mixed mode, We need to select mixed mode while we install sql server.

@Hima: You are absolutely correct. The root cause is the selection of features and configuration options at install time.

Windows Authentication, being more secure is the default installation mode from SQL Server 2008 onwards. Thus, if somebody ran through the installation using the default options, and the application is using SQL users, then one is most likely to end up with this issue.

Recently, to deploy my site, I changed my authentication from 'Windows' to 'SQL authentication'. Successfully added the user to ‘Security\Logins’. But having problem enabling database role membership as it returns error 15247. I believe error 15151 is also that of permission issues.

Here's an extra info in case it might help narrow down the problem scope, if i access my server it shows this error;

"Login failed for user 'kaneXtreme' ".

In my localhost,it shows this error;

"The SELECT permission was denied on the object, database, schema"

In my opinion, I think both error messages are pointing to a similar problem which is permission.

This problem has been remained unsolved for some time now. If anyone have come across this problem before I really hope to get a few input to work around on this.

Thank you in advance.

Hi,

great article Complete description and solutions for this error