Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user
Any idea's?In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?
I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.
Regards,
Hugh Scott
Originally posted by dbJeff
Hi,
I've installed SQL 2000 SP3 on a Windows 2000 server with Active Directory (not the PDC), but when I try to logon using a Windows account (domain\user) I get the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
SQL State: 28000
DB error: 18456
The same happens when I try to logon with the Query Analyzer or register the server in Enterprise Manager. I looked around other forums to figure this one out but none of the tips there worked:
- Authentication is mixed mode
- IIS is not installed
- There is a login created in SQL for the Windows user
Any idea's?|||Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?
Originally posted by hmscott
In the back of my mind somewhere, I have a recollection that when AD is installed the Local Users for that server are disabled. Was the user you were trying to log in as Local or Domain?
I think I would try creating a Domain User, adding that user into the Local Computer Administrators group and then logging in as that Domain User.
Regards,
Hugh Scott|||D'oh! That wasn't very smart of me!
Did you try using sp_grantaccess to ensure that the domain account you were trying to use can access the server?
I don't have much experience running SQL Server with AD; I am running a home network with AD and SQL running on the PDC. I am authenticating using a local account on my Windows XP notebook with no problems. Before I promoted the server to DC, I had a local account with identical credentials in the Administrators group. I have had no problems keeping that account up and running.
I'm afraid I don't have many other suggestions...sorry.
Regards,
Hugh
Originally posted by dbJeff
Hugh, you're right that Local Users are disabled with AD, but Local Groups are as well. Any other idea's?
Showing posts with label logon. Show all posts
Showing posts with label logon. Show all posts
Thursday, March 29, 2012
Error 18456 Severity 14 State 16
I am getting the following error in my Sql logs and in my Application Event
viewer:
03/16/2007 07:56:00,Logon,Unknown,Login failed for user
'CTPC\Administrator'. [CLIENT: <local machine>]
03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1
6.
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
0018: 45 00 54 00 00 00 07 00 E.T....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...
I have tried figure out what process is trying to hit this database but to
no avail, how should I go about troubleshooting this? It logs this every on
e
minute and it is on our Portal server.
Thanks,
RobYou can run a trace or Profiler when a login fails and see
what shows up for the application name when auditing the
Login Failures.
It's on the same box as SQL Server so you could also check
what services may be running under the local administrator
account.The security logs may have more information as well
if you track the logins and details for the logins.
-Sue
On Fri, 16 Mar 2007 06:02:16 -0700, Rob
<Rob@.discussions.microsoft.com> wrote:
>I am getting the following error in my Sql logs and in my Application Event
>viewer:
>03/16/2007 07:56:00,Logon,Unknown,Login failed for user
>'CTPC\Administrator'. [CLIENT: <local machine>]
>03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
>0000: 18 48 00 00 0e 00 00 00 .H.....
>0008: 09 00 00 00 49 00 4e 00 ...I.N.
>0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
>0018: 45 00 54 00 00 00 07 00 E.T....
>0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
>0028: 74 00 65 00 72 00 00 00 t.e.r...
>I have tried figure out what process is trying to hit this database but to
>no avail, how should I go about troubleshooting this? It logs this every o
ne
>minute and it is on our Portal server.
>Thanks,
>Rob
viewer:
03/16/2007 07:56:00,Logon,Unknown,Login failed for user
'CTPC\Administrator'. [CLIENT: <local machine>]
03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1
6.
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
0018: 45 00 54 00 00 00 07 00 E.T....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...
I have tried figure out what process is trying to hit this database but to
no avail, how should I go about troubleshooting this? It logs this every on
e
minute and it is on our Portal server.
Thanks,
RobYou can run a trace or Profiler when a login fails and see
what shows up for the application name when auditing the
Login Failures.
It's on the same box as SQL Server so you could also check
what services may be running under the local administrator
account.The security logs may have more information as well
if you track the logins and details for the logins.
-Sue
On Fri, 16 Mar 2007 06:02:16 -0700, Rob
<Rob@.discussions.microsoft.com> wrote:
>I am getting the following error in my Sql logs and in my Application Event
>viewer:
>03/16/2007 07:56:00,Logon,Unknown,Login failed for user
>'CTPC\Administrator'. [CLIENT: <local machine>]
>03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
>0000: 18 48 00 00 0e 00 00 00 .H.....
>0008: 09 00 00 00 49 00 4e 00 ...I.N.
>0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
>0018: 45 00 54 00 00 00 07 00 E.T....
>0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
>0028: 74 00 65 00 72 00 00 00 t.e.r...
>I have tried figure out what process is trying to hit this database but to
>no avail, how should I go about troubleshooting this? It logs this every o
ne
>minute and it is on our Portal server.
>Thanks,
>Rob
Error 18456
Hello I am getting:
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.State 8 is an invalid password.
Passwords in SQL Server 2005 are case sensitive so make sure
you are checking that as well. If you can't log in at all
and no one can log in, try logging in as local administrator
on the box and then log into SQL Server using windows
authentication.
-Sue
On Wed, 15 Mar 2006 19:34:00 -0600, "JimS"
<noholycowsspam@.ya_NoJunk_hoo.com> wrote:
>Hello I am getting:
>"login failed" (Error 18456) error messages in SQL Server 2005 Error is
>18456, Severity: 14, State: 8.
>I have tried to logon to other databases and this isnt possible. I get th
e
>same error message. Creating new logins, and triple-checking the passwords
>did not help. The database engine will not allow any logons to any
>database. The other engines seem to be fine.
>This still means that I do not have permissions for any of the databases.
>This is using any of the local or domain accounts. I cannot log onto any o
f
>the databases. I have tried to attach using SQLCMD and I cannot get logged
>in to the database.
>The log files show success from earlier in the day and week for these same
>accounts.
>I created this problem by detaching one database running on the server. I
>went to connect the datafiles and now I cannot get into the server at all.
>I am using SQL2005, Sharepoint services and a Windows 2003 server.
>I would appreciate any insight or suggestions.
>|||Thanks for the help....
We detached a database in order to copy the files. When I detached the
database it seemed to lock all users with access to that database out any
access to this SQL2005 server.
I was able to use SQLCMD to gain access and rebuild access for my database
admin account. I was then able to use this account to reattach the detached
database. When I did this the database and all user access to SQL2005 was
back to normal. I am not sure why this happened. We have about ten other
databases on this SQL server. The same users had access to these tables as
well as the detached table so the detached table was not the only table for
which they had access. The detached table was just a table of 'production'
data. I will try and see if I can recreate the problem but will wait for
the weekend to try that!
Thanks
"JimS" <noholycowsspam@.ya_NoJunk_hoo.com> wrote in message
news:%23EnC0mJSGHA.1576@.tk2msftngp13.phx.gbl...
Hello I am getting:
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.State 8 is an invalid password.
Passwords in SQL Server 2005 are case sensitive so make sure
you are checking that as well. If you can't log in at all
and no one can log in, try logging in as local administrator
on the box and then log into SQL Server using windows
authentication.
-Sue
On Wed, 15 Mar 2006 19:34:00 -0600, "JimS"
<noholycowsspam@.ya_NoJunk_hoo.com> wrote:
>Hello I am getting:
>"login failed" (Error 18456) error messages in SQL Server 2005 Error is
>18456, Severity: 14, State: 8.
>I have tried to logon to other databases and this isnt possible. I get th
e
>same error message. Creating new logins, and triple-checking the passwords
>did not help. The database engine will not allow any logons to any
>database. The other engines seem to be fine.
>This still means that I do not have permissions for any of the databases.
>This is using any of the local or domain accounts. I cannot log onto any o
f
>the databases. I have tried to attach using SQLCMD and I cannot get logged
>in to the database.
>The log files show success from earlier in the day and week for these same
>accounts.
>I created this problem by detaching one database running on the server. I
>went to connect the datafiles and now I cannot get into the server at all.
>I am using SQL2005, Sharepoint services and a Windows 2003 server.
>I would appreciate any insight or suggestions.
>|||Thanks for the help....
We detached a database in order to copy the files. When I detached the
database it seemed to lock all users with access to that database out any
access to this SQL2005 server.
I was able to use SQLCMD to gain access and rebuild access for my database
admin account. I was then able to use this account to reattach the detached
database. When I did this the database and all user access to SQL2005 was
back to normal. I am not sure why this happened. We have about ten other
databases on this SQL server. The same users had access to these tables as
well as the detached table so the detached table was not the only table for
which they had access. The detached table was just a table of 'production'
data. I will try and see if I can recreate the problem but will wait for
the weekend to try that!
Thanks
"JimS" <noholycowsspam@.ya_NoJunk_hoo.com> wrote in message
news:%23EnC0mJSGHA.1576@.tk2msftngp13.phx.gbl...
Hello I am getting:
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.
Error 18456
I am repeatedly receiving the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
This has been occuring since a network wide password
change ( for an employee leaving the company ) and I do
realize that there is some process trying to connect, but
I do not know how to find out what the process is, or
what it is trying to connect as. Is there a way to trace
this information?You may be able to catch this with SQL Profiler and/or a network trace.
The network trace will only work if the connection is coming from a remote
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Have tried the profiler and don't get enough information
to track. Haven't tried a network trace, I will try, but
I don't think it is a remote connection. Thanks for your
help.
Rachel
>--Original Message--
>You may be able to catch this with SQL Profiler and/or a
network trace.
>The network trace will only work if the connection is
coming from a remote
>machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
This has been occuring since a network wide password
change ( for an employee leaving the company ) and I do
realize that there is some process trying to connect, but
I do not know how to find out what the process is, or
what it is trying to connect as. Is there a way to trace
this information?You may be able to catch this with SQL Profiler and/or a network trace.
The network trace will only work if the connection is coming from a remote
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Have tried the profiler and don't get enough information
to track. Haven't tried a network trace, I will try, but
I don't think it is a remote connection. Thanks for your
help.
Rachel
>--Original Message--
>You may be able to catch this with SQL Profiler and/or a
network trace.
>The network trace will only work if the connection is
coming from a remote
>machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
Sunday, March 11, 2012
error 1069: The service did not start due to logon problems
The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.
I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.
Any suggestions would be helpful.
Thanks
try this article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q282254
error 1069: The service did not start due to logon problems
The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.
I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.
Any suggestions would be helpful.
Thanks
try this article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q282254
error 1069
'the service did not start due to a logon failure' return
trying to start SQL server after I changed my password.
Does this make sense?Go to control panel services. Change the account password to start the
MSSQLServer Service and /or SQLAgent.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
trying to start SQL server after I changed my password.
Does this make sense?Go to control panel services. Change the account password to start the
MSSQLServer Service and /or SQLAgent.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Friday, March 9, 2012
Error 10061, SQL Server 2005 DEV actively refuses connection
I just installed a fresh SQL Server 2005 MSDN and tried to use the
management console, but all attempts to logon fail.
Message says 'failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.'
How can I change these settings or otherwise get a connection?
Thanks.First is to open up the Surface Area Configuration tool, select to
view Services and Connections. Under Database Engine, go to Remote
Connections. Change it to allow remote connections using whichever
protocols you plan on using from remote clients.
-Sue
On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
wrote:
>I just installed a fresh SQL Server 2005 MSDN and tried to use the
>management console, but all attempts to logon fail.
>Message says 'failure may be caused by the fact that under the default
>settings SQL Server does not allow remote connections.'
>How can I change these settings or otherwise get a connection?
>Thanks.|||Worked. Thank you. New to 2005.
On Tue, 17 Apr 2007 11:45:22 -0600, Sue Hoegemeier
<Sue_H@.nomail.please> wrote:
[vbcol=seagreen]
>First is to open up the Surface Area Configuration tool, select to
>view Services and Connections. Under Database Engine, go to Remote
>Connections. Change it to allow remote connections using whichever
>protocols you plan on using from remote clients.
>-Sue
>On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
>wrote:
>
management console, but all attempts to logon fail.
Message says 'failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.'
How can I change these settings or otherwise get a connection?
Thanks.First is to open up the Surface Area Configuration tool, select to
view Services and Connections. Under Database Engine, go to Remote
Connections. Change it to allow remote connections using whichever
protocols you plan on using from remote clients.
-Sue
On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
wrote:
>I just installed a fresh SQL Server 2005 MSDN and tried to use the
>management console, but all attempts to logon fail.
>Message says 'failure may be caused by the fact that under the default
>settings SQL Server does not allow remote connections.'
>How can I change these settings or otherwise get a connection?
>Thanks.|||Worked. Thank you. New to 2005.
On Tue, 17 Apr 2007 11:45:22 -0600, Sue Hoegemeier
<Sue_H@.nomail.please> wrote:
[vbcol=seagreen]
>First is to open up the Surface Area Configuration tool, select to
>view Services and Connections. Under Database Engine, go to Remote
>Connections. Change it to allow remote connections using whichever
>protocols you plan on using from remote clients.
>-Sue
>On Tue, 17 Apr 2007 12:50:23 GMT, algernon bonzo <bonzo@.manchu.net>
>wrote:
>
Subscribe to:
Posts (Atom)