Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wylbur
Starting Member
29 Posts |
 Posted - 2009-01-25 : 18:54:17
|
Hi All;I'm having a problem logging in to management Studio with a fresh install of 2005.I'm getting error 18456.I'm using Windows Authentication mode.OS is Vista home premium.Can anyone direct me to a good website that can give me a clear set of step-by-step instructions for installing 2005?Especially with regard to how to set up accounts on the server?PLEASE keep in mind that I am FAR from being the world's leadingauthority on 2005 - no - not at all.What follows is the contents of my error log:-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-2009-01-23 08:04:48.75 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 6.0 (Build 6001: Service Pack 1)2009-01-23 08:04:48.79 Server (c) 2005 Microsoft Corporation.2009-01-23 08:04:48.79 Server All rights reserved.2009-01-23 08:04:48.79 Server Server process ID is 4624.2009-01-23 08:04:48.79 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.2009-01-23 08:04:48.79 Server This instance of SQL Server last reported using a process ID of 3136 at 12/28/2008 8:35:50 PM (local) 12/29/2008 2:35:50 AM (UTC). This is an informational message only; no user action is required.2009-01-23 08:04:48.79 Server Registry startup parameters:2009-01-23 08:04:48.79 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf2009-01-23 08:04:48.79 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG2009-01-23 08:04:48.79 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf2009-01-23 08:04:49.12 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.2009-01-23 08:04:49.12 Server Detected 2 CPUs. This is an informational message; no user action is required.2009-01-23 08:05:00.13 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.2009-01-23 08:05:04.39 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.2009-01-23 08:05:05.33 Server An error occurred while trying to determine the state of the RPCSS service. A call to "OpenServiceW" returned: 5(Access is denied.). This is an informational message only. No user action is required.2009-01-23 08:05:05.37 Server An attempt to connect to Microsoft Distributed Transaction Coordinator (MS DTC) will be skipped because the RPCSS service doesn't appear to be started. Another attempt to connect to MS DTC will be made later. This is an informational message only. No user action is required.2009-01-23 08:05:07.98 Server Database Mirroring Transport is disabled in the endpoint configuration.2009-01-23 08:05:09.27 spid5s Starting up database 'master'.2009-01-23 08:05:11.91 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.2009-01-23 08:05:14.58 spid5s SQL Trace ID 1 was started by login "sa".2009-01-23 08:05:14.84 spid5s Starting up database 'mssqlsystemresource'.2009-01-23 08:05:17.77 spid5s Server name is 'JOE\INSTANCE01'. This is an informational message only. No user action is required.2009-01-23 08:05:17.81 spid9s Starting up database 'model'.2009-01-23 08:05:20.08 spid9s Clearing tempdb database.2009-01-23 08:05:24.51 Server Error: 17190, Severity: 16, State: 1.2009-01-23 08:05:24.51 Server FallBack certificate initialization failed with error code: 1.2009-01-23 08:05:24.65 Server Warning:Encryption is not available, could not find a valid certificate to load.2009-01-23 08:05:24.98 Server Server is listening on [ 'any' <ipv6> 49343].2009-01-23 08:05:24.98 Server Server is listening on [ 'any' <ipv4> 49343].2009-01-23 08:05:25.12 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSTANCE01 ].2009-01-23 08:05:25.14 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$INSTANCE01\sql\query ].2009-01-23 08:05:25.15 Server Server is listening on [ ::1 <ipv6> 49497].2009-01-23 08:05:25.17 Server Server is listening on [ 127.0.0.1 <ipv4> 49497].2009-01-23 08:05:25.17 Server Dedicated admin connection support was established for listening locally on port 49497.2009-01-23 08:05:25.85 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.2009-01-23 08:05:25.85 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.2009-01-23 08:05:27.91 spid9s Starting up database 'tempdb'.2009-01-23 08:05:32.58 spid12s The Service Broker protocol transport is disabled or not configured.2009-01-23 08:05:32.58 spid12s The Database Mirroring protocol transport is disabled or not configured.2009-01-23 08:05:34.82 spid14s Starting up database 'msdb'.2009-01-23 08:05:34.82 spid16s Starting up database 'AdventureWorks'.2009-01-23 08:05:34.82 spid15s Starting up database 'AdventureWorksDW'.2009-01-23 08:05:35.16 spid12s Service Broker manager has started.2009-01-23 08:05:40.56 spid5s Recovery is complete. This is an informational message only. No user action is required.2009-01-23 08:13:44.98 Logon Error: 18456, Severity: 14, State: 11.2009-01-23 08:13:44.98 Logon Login failed for user 'JOE\Owner'. [CLIENT: <local machine>]-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Any help with this would be greatly appreciated.THANKS!!! Wylbur======================== |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2009-01-25 : 22:15:59
|
| The error message isLogin failed for user 'JOE\Owner'. [CLIENT: <local machine>]Is the user a local admin?If it's the user you used to install then it should connect.Maybe in vista need to run studio as admin to connect - I usually turn user account control off if I get any problems.state 11 means it's a valid login which points towards it not being an admin.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
Wylbur
Starting Member
29 Posts |
Posted - 2009-01-25 : 23:05:53
|
| Hi nr and Tara;I was logged in as the administrator when I performed the installation.I think the best thing to do would be to establish a new administrative account, and go from there - start over from scratch.What would be the steps involved in doing that?THANKS!!!Wylbur======================== |
|
|
|
|
|
|
Problem with logging in to 2005 (fresh install)