Re: Connextion Error After Installing SQL Server 2005 on Vista

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: SQL Server 2005 faulure when updating to SP1
    ... The local machine's "Administrator" group has an entry on the directory ... and each file granting "Full Control" along with the Local Windows SQL Server ... When installing the Service Pack, the Indexing Service is disabled and I ... have stopped the Antivirus service when I try the Service Pack installation. ...
    (microsoft.public.sqlserver.setup)
  • Re: Failed SQL 2005 install, unable to start again.
    ... I just want you to consider UAC of Windows Vista\Server 2008 or just simply right click on the SQL Server Setup file and click Run as Administrator to run the setup under your administrator role. ... Also, before, I've seen that creating a false file with the same name as just the SQL Server Setup asked simply worked. ... you can go to Control Panel\Programs & Features and remove all installed components of SQL Server and start a new installation from your SQL Server media. ...
    (microsoft.public.sqlserver.setup)
  • Securing SQL Server after administration installation
    ... domain user account for both the SQL Server and SQL Server agent ... would creating the SQL service user before installation ... and using that instead of administrator have helped? ...
    (microsoft.public.sqlserver.setup)
  • Securing SQL Server after administration installation
    ... domain user account for both the SQL Server and SQL Server agent ... would creating the SQL service user before installation ... and using that instead of administrator have helped? ...
    (microsoft.public.sqlserver.security)
  • [NT] SQL Server Installation Process May Leave Passwords on System
    ... service pack for SQL Server 7.0 or SQL Server 2000, ... without having to actually perform an installation. ... to SQL Server 7.0 Service Pack 4, the passwords were stored in clear text. ... information in the setup.iss and log files would not allow any access. ...
    (Securiteam)