Re: Connextion Error After Installing SQL Server 2005 on Vista

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Bob-PC\SQLServer2005MSFTEUser$BOB-PC$MSSQLSERVER is used by the Full Text Search Service.
Bob-PC\SQLServer2005MSSQLUser$BOB-PC$MSSQLSERVER is used by the SQL Server Database Engine Service.
Bob-PC\SQLServer2005SQLAgentUser$BOB-PC$MSSQLSERVER is used by the SQL Server Agent Service.
These are required so that the Windows services can connect to SQL Server. You can ignore them. Don't delete them.

When you run Management Studio as an administrator you get into SQL Server using that BUILDIN\Administrators login. What you want is an individual login.
1. Right-click Logins, and then click New Login.
2. Create a login for Bob-PC\Bob, and make it a sysadmin.
Then you will be able to connect with Management Studio without using your Administrators credentials.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Bob Bryan" <RobertGBryanREMOVETHIS@xxxxxxx> wrote in message news:giXqk.2887$Is1.1957@xxxxxxxxxxxxxxx
Hi Rick,

Your suggestion of right clicking and running as an admin worked perfectly. Thanks very much for the info. I clicked on the link you listed, but do not quite understand something. In Management Studio, under Security/Logins there are 6 accounts listed:

1. Bob-PC\SQLServer2005MSFTEUser$BOB-PC$MSSQLSERVER
2. Bob-PC\SQLServer2005MSSQLUser$BOB-PC$MSSQLSERVER
3. Bob-PC\SQLServer2005SQLAgentUser$BOB-PC$MSSQLSERVER
4. BUILTIN\Administrators
5. NT AUTHORITY\SYSTEM
6. sa

I right clicked the first login above and selected Properties. It did not have any admin privs under Server Roles. So, I added sysadmin privs for this login. All the other logins already had sysadmin selected. When I exited and tried to restart, this time without right clicking and selecting "run as admin", it failed to connect again. So, can you tell me what the first 3 logins are used for and if I need to create a new login, then what should be the exact name of that login?

Thanks again for your help.

Bob Bryan

"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E2BEF355-D50A-4329-BF9B-99853A5876DF@xxxxxxxxxxxxxxxx
You are probably trying to connect as Bob using your membership in the computers local administrators group; the BUILTIN\ADMINISTRATORS group being a member of the sysadmin fixed server role in SQL Server. But Vista User Account Control (UAC) doesn't automatically pass your administrator credentials to programs. The solution is to explicitly grant Bob access to SQL Server.
Right-click Management Studio and click Run as Administrator (passing your admin credentials). Then, if this was your problem you will be able to connect. Add Bob as a login and as a sysadmin.
From now on you can connect without using your administrator credentials.
For more info: http://msdn.microsoft.com/en-us/library/bb326612.aspx
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Bob Bryan" <RobertGBryanREMOVETHIS@xxxxxxx> wrote in message news:RcTqk.23542$LF2.22284@xxxxxxxxxxxxxxx
I just installed SQL Server 2005 on my Vista (SP1) laptop. I also successfully installed SQL Server SP2 for Vista. When going into SQL Server Management Studio and connection to the default instance of the server that was just installed, the following error is generated in the log file:

2008-08-20 03:09:55.36 Logon Error: 18456, Severity: 14, State: 11.
2008-08-20 03:09:55.36 Logon Login failed for user 'Bob-PC\Bob'. [CLIENT: <local machine>]

During the installation, I was prompted a couple of times to install a service pack for Visual Studio 2005, which is not currently installed. Visual Studio 2008 with Beta SP1 is installed. Using the Surface Area Configuration tool, the Database engine component, SQL Server Agent, Full-Text Search, and SQL Server Browser are all running.

SQL Server 2008 was installed on this machine previously, but since there were similar problems with connecting, I tried to un-install it, but not all of the components were completely removed. I have now spent at least 10 hours trying to get this to work and am about to give up and try another database. I never had any problems installing or connecting to SQL Server 2005 with Windows XP. Can anyone offer any helpful suggestions?

Thanks,

Bob Bryan



.

Relevant Pages

  • Re: Connextion Error After Installing SQL Server 2005 on Vista
    ... Your suggestion of right clicking and running as an admin worked perfectly. ... I right clicked the first login above and selected Properties. ... The solution is to explicitly grant Bob access to SQL Server. ... During the installation, I was prompted a couple of times to install a service pack for Visual Studio 2005, which is not currently installed. ...
    (microsoft.public.sqlserver.connect)
  • Re: Is there any way to prevent hacker trying to guess sa password?
    ... What is the migration path like to SQL Server 2005? ... How is installation and setup? ... I setup my own SQL Server accounts and use those. ... You can include the login (such as sa, admin, ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server Management Studio Express 2008
    ... SQL Server 2008 Express Edition with Tools and Advanced Services have SQL Server Management Studio Basic with them and this feature is called "Management Tools - Basic" and you can check this feature to be installed during SQL Server 2008 Express Edition installation. ...
    (microsoft.public.sqlserver.setup)
  • Re: Where is SQL Management Studio?
    ... Run setup from your sql server dvd and select database engine, ... installation features selected) and can't figure out how I am supposed to ... None of these puts up an UI that I can use to develop databases! ... Management Studio, but I don't ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server Management Studio Express 2008
    ... SQL Server 2008 Express Edition with Tools and Advanced Services have SQL ... Server Management Studio Basic with them and this feature is ... However, if you did not check it during an installation, you can simply ...
    (microsoft.public.sqlserver.setup)