Friday, March 30, 2012

Need Help Configuring SQL Server Express

I have Visual Studio 2005 Professional installed and SQL Server Express installed. In following along with the Microsoft Visual C# Step by Step book, there is a procedure on page xxi to get access to SQL Server Express. At the 2> prompt, however, when I type in go and then press enter, I get the following message:

Msg 15247 Level 16, State 1, Server MyServerName\SQLEXPRESS, Procedure sp_grantlogin, Line 13

User does not have permission to perform this action.

The computer is my own personal computer, with Window Vista installed and no previous versions of MSDE installed. I also have administrator persmissions. The only guidelines in the procedure regarding what to do in the event of an error message is to ensure that the commands were typed in correctly. What could be causing this message, since I do have administrator permissions?

hi,

as you are dealing with Vista and UAC related issues, please verify your actual login has the minimal required permissions to execute sp_grantlogin system stored procedure, ALTER ANY LOGIN or higher...

regards

|||

Hi. When I go to Start->Control Panel->User Accounts, and then click on the Change Your Account Type link, the window that appears shows my present status, which is Administrator. A message in the window states:

"Administrators have complete access to the computer and can make any desired changes."

Following that sentence is a sentence which has advice about creating a password. I then cancel the task, since I really didn't want to change my status. Was that sufficient to verify that I've got the minimal required permissions to execute sp_grantlogin?

I'm not sure what UAC means (User Account Control?). But I do have a problem with Windows Defender not working...giving me a message that it cannot update the definitions. In following the help threads on Windows Defender problems, I discovered that there is no wuaucpl.cpl file in my windows directory. I've opened up an email help procedure with Microsoft on that.

Edit: I realize now that wuaucpl.cpl is no longer a file included in Windows Vista (though my SQL Server problem is probably not related to my problem with Windows Defender).

|||

hi,

this is correct at the OS level, but please verify "inside" SQLExpress that your login has appropriate permissions as well..

regards

|||Hi. Unfortunately, I am a complete neophyte when it comes to SQL Server. How do I verify that my login has the appropriate permissions? I've never actually started SQLExpress or done anything with it. I know that I have a SQL Sever configuration manager tool, and when I open it and look at the SQL Server 2005 Services folder, I can see that SQLExpress is running.|||

Vista has changed the playing field and now forces everyone to run as a non-administrative user, even if you're an administrator, until you explicity request to be elevated to administrative privleges. I've explained a bit about how this works and how to correctly configure SQL Express on Vista in this blog post. You already have SQL installed, so make sure you're using SP2 and then follow the instruction for running the Provisioning tool to correctly set your access level.

Mike

|||Mike, thanks for that info. I do have SP2 installed. I just want to clear up one more thing. When I open up the SAC tool, and click on Add New Administrator, the SQL Server 2005 User Provisioning Tool for Vista window opens. In it there is a text box that has MyServerName\UserName as the user to provision. In the available privileges in the left pane, there is SQLEXPRESS with one item named: Member of SQL Server SysAdmin role on SQLEXPRESS. This is the only availbable privilege showing. So I should transfer this privilege, and I should then be able to grant myself the sp_grantlogin permission? Just want to make sure about this before I do anything.|||

All you need to do is give yourself SysAdmin privledges and you're done, no need to use sp_grantlogin. Once you're a SysAdmin you have every permission that it is possible to have.

Mike

|||Thanks for all the help, Mike.

No comments:

Post a Comment