sql error 15138: 2012

Thursday, March 29, 2012

Error 193 installing

When installing SQL Server 2005 the first component to be installed by the setup it is it (.NET Framework 2.0), but it happens the following mistake
" Error 193 installing .NET Framework 2.0 "... what is doing wrong and which would be solution

You can try to install .NET 2.0 from windows update or download it separatly and try to install it manually.

http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

If it still fails try to include all error messages as it might give a better idea what is going on.

Have you had any Visual Studio 2005/.NET 2.0 beta versions installed?

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.
sql

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

Error 1920. Service 'ReportServer' (ReportServer) failed to start

Hello, I cannot install Reporting Services Developer Version, at the end of
the setup I got a message like:
Error 1920. Service 'ReportServer' (ReportServer) failed to start. Verify
that you have sufficient privileges to start system services.
I have SQL SP3a, IIS, .NET 2003 all in the same computer.
Just cannot find how to solve the problem, seems to be something with the
account used to start the service, but with neither the built in account, not
a computer admin account can continue. Have no problem creating the database,
just to start the service.
Help pleaseMy problem is solved; I think you only need to change the installation path
of RS during the setup, but the following are the steps I follow:
1. Uninstall RS
2. Clean all signs of RS in the registry, the service and components
Delete in the registry the entries in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RS Rep..
Delete the service from the command prompt
sc delete ReportServer
Delete the components in Component Services in
the control panel Administrative Tools in the COM+ Applications for the ISS
3. Install RS in a different path
I install RS in C:\Program Files\Microsoft SQL ServerRS
Also i rename the services in the setup to MSReportService, MSReports for
the
IIS part.
I have Windows XP with all in one box; I use a domain account, for the
services
and for the SQL login.

Error 1911 replication column does not exist

Source server MSSQL7.0
Destination server MSSQL2K

I'm setting up replication for reporting purposes to another SQL-server.
When I start the distribution agent I get the following error:
Column name '<here's the name of a column I didn't publish and don't need to replicate>' does not exist in the target table.
Error number: 1911

I assume this is because of some dependencies between the columns.

Is there any way I can replicate without those columns?

RegardsDependency doesn't get replicated unless you specified. If you think the error was caused by the column dependency, check the unique index and the foreign key constraint to see whether the 'for replication' is checked or not.|||Thanks, you gave me the hint I needed.
I was scripting the creation of the publication because I need to setup replication for over 20 db's.
In the script you have to change the sp_addarticle @.schema_option value.

Regards

Error 18483 while configuring distributor

I want to setup a publisher, distributor and subscriber on the same machine.
While configuring my distributor using Wizard, I received the following
error:
Error 18483: Could not connect to server 'HONB" because "distributor_admin"
is not defined as a remote login at the server.
I am using SQL Server Developer version and "HONB" is my computer name. Can
someone tell what I have mis-configed?
This is usually a naming issue.
Try:
Use Master
go
Select @.@.Servername
This should return your current server name but if it
returns NULL then try:
Use Master
go
Sp_DropServer 'Server1'
GO
Use Master
go
Sp_Addserver 'Server1', 'local'
GO
Stop and Start SQL Services
If this is not the issue, but you are working across non-trusted doamins
there is the same error, so you might want to have a look at his article:
http://support.microsoft.com/?id=321822.
Regards,
Paul Ibison
|||I tried to run the sql, the servername is ok.
I read articale, but it seems not related to my problem, since I want to
setup the replication on a single machine.
Is it related to sql server agent? I am using system account as the startup
account in Sql server agent.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> bl
news:Oocp%23YwKEHA.4052@.TK2MSFTNGP11.phx.gbl g...
> This is usually a naming issue.
> Try:
> Use Master
> go
> Select @.@.Servername
> This should return your current server name but if it
> returns NULL then try:
> Use Master
> go
> Sp_DropServer 'Server1'
> GO
> Use Master
> go
> Sp_Addserver 'Server1', 'local'
> GO
> Stop and Start SQL Services
> If this is not the issue, but you are working across non-trusted doamins
> there is the same error, so you might want to have a look at his article:
> http://support.microsoft.com/?id=321822.
> Regards,
> Paul Ibison
>
|||The system account is OK if it is all done on the same box.
You might be able to use sp_remoteoption and sp_addremotelogin to fix the
issue.
HTH,
Paul Ibison
|||can you remove replication, and then re-install it.
"gh" <ghghghgh@.FSAF.COM> wrote in message
news:uinEcarKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> I want to setup a publisher, distributor and subscriber on the same
machine.
> While configuring my distributor using Wizard, I received the following
> error:
> Error 18483: Could not connect to server 'HONB" because
"distributor_admin"
> is not defined as a remote login at the server.
> I am using SQL Server Developer version and "HONB" is my computer name.
Can
> someone tell what I have mis-configed?
>
>
>

Error 18483 'distributor_admin'

I'm trying to publish a database and when I get to the end of the wizard, I
am greeted by this message:
SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
Distributor for 'SERVERNAME'.
Error 18483: Could not connect to server 'SERVERNAME' because
'distributor_admin' is not defined as a remote login at the server.
The MS articles did not help me. Can someone, please?
Wack
This message will self destruct.
try to drop the server and then recreate it
sp_dropserver @.@.servername
GO
sp_addserver @.@.servername, 'local'
GO
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ray Lewis" <dav5489@.hotmail.com> wrote in message
news:uO9gjUYJFHA.4060@.TK2MSFTNGP14.phx.gbl...
> I'm trying to publish a database and when I get to the end of the wizard,
I
> am greeted by this message:
> SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
> Distributor for 'SERVERNAME'.
> Error 18483: Could not connect to server 'SERVERNAME' because
> 'distributor_admin' is not defined as a remote login at the server.
> The MS articles did not help me. Can someone, please?
> --
> Wack
> --
> This message will self destruct.
>
|||I tried this, and used MS article 818334. I found that the SQL Server Name
was not the same as the Computer Name. However, when I try and drop the SQL
server name, I get a message stating that the SQL server does not exist.
So, I cannot rename my SQL Server 2000 server. What now?
Wack
This message will self destruct.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uZUqNwaJFHA.1392@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> try to drop the server and then recreate it
> sp_dropserver @.@.servername
> GO
> sp_addserver @.@.servername, 'local'
> GO
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ray Lewis" <dav5489@.hotmail.com> wrote in message
> news:uO9gjUYJFHA.4060@.TK2MSFTNGP14.phx.gbl...
wizard,
> I
>
|||Hi,
is the login used to configure the publication a member of the 'system administrators'? I had a similar problem when creating a pull subscription and this solved it!
Bruno

Quote:

Originally posted by Ray Lewis
I'm trying to publish a database and when I get to the end of the wizard, I
am greeted by this message:
SQL Server Enterprise Manager could not configure 'SERVERNAME' as the
Distributor for 'SERVERNAME'.
Error 18483: Could not connect to server 'SERVERNAME' because
'distributor_admin' is not defined as a remote login at the server.
The MS articles did not help me. Can someone, please?
Wack
This message will self destruct.

sql

error 18483 & 18482

Hi ,
At first i was trying to set up replication where i got the Error 18483:
could not connect to server 'SQL1; because 'distributor_admin' is not defined
as a remote login at the server.
as per some of the posting i used "Select @.@.Servername" (e.g SQL2)and found
that the name returned is not the same as the computer name(e.g SQL1)
so i executed sp_dropserver @.@.Servername (SQl2)
now when i tried to configure it as a publisher , it gives me "could not
configure SQL1 as the distributor for SQL1. error 18482 : could not connect
to SQL1 because 'SQL2' is not defined as a remote server
i have tried sp_addserver SQL1 but it does not work either
kindly advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
Hi ,
After i stop & start SQL Server , i got error 14114 : null is not
configured as a distributor and null is returned for select @.@.Servername
kindly advise
tks & rdgs
maxzsim wrote:
>Hi ,
> At first i was trying to set up replication where i got the Error 18483:
>could not connect to server 'SQL1; because 'distributor_admin' is not defined
>as a remote login at the server.
>as per some of the posting i used "Select @.@.Servername" (e.g SQL2)and found
>that the name returned is not the same as the computer name(e.g SQL1)
>so i executed sp_dropserver @.@.Servername (SQl2)
>now when i tried to configure it as a publisher , it gives me "could not
>configure SQL1 as the distributor for SQL1. error 18482 : could not connect
>to SQL1 because 'SQL2' is not defined as a remote server
>i have tried sp_addserver SQL1 but it does not work either
>kindly advise
>tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Hi,
The steps below from one of the posting works
sp_dropserver 'wrong server name'
sp_addserver 'correct server name'
stop & start sql services( i forgot to do this step earlier)
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi ,
> After i stop & start SQL Server , i got error 14114 : null is not
>configured as a distributor and null is returned for select @.@.Servername
>kindly advise
>tks & rdgs
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Had similar problem with starting the replication distributor.
Got login failed message for distributor_admin user.
Problem: Local SQL Server instance name incorrect
We changed the name of the server a while back but the @.@.Servername had the
old server name.
Solution:
sp_dropserver 'oldservername'
sp_addserver 'newservername', @.local = 'local'
The @.local ='local' is required because the replication server is the local
server not a remote server.
Also you need to stop and restart SQL Server Agent.
"maxzsim via droptable.com" wrote:

> Hi,
> The steps below from one of the posting works
> sp_dropserver 'wrong server name'
> sp_addserver 'correct server name'
> stop & start sql services( i forgot to do this step earlier)
> tks & rdgs
>
> maxzsim wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ation/200512/1
>

Error 18456: Login failed for user 'DOMAIN\user'

Hi,
I've just installed SQL Server 2005 Beta 2 and added Active Directory
account to our SQL Server (under Database/Security/Logins). However, when I
try to login using the Windows Authentication, I get this error message:
Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
where DOMAIN\user is really my domain-account, which I rather not publish.
When I try to login using 'sa' and SQL Server Authentication there is no
problem.
I've tried to find out what error 18456 is but no luck. Could anyone help me
please?
Cheers,
ChrisI take it that either no one has ever heard of this error or that is so
common that its in every FAQ. In the latter case, could someone please point
me to a FAQ with a solution...
Cheers,
Chris
"Christoffer" <christoffer@.nospam.com> wrote in message
news:%23alyI3zjEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I've just installed SQL Server 2005 Beta 2 and added Active Directory
> account to our SQL Server (under Database/Security/Logins). However, when
> I try to login using the Windows Authentication, I get this error message:
> Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
> where DOMAIN\user is really my domain-account, which I rather not publish.
> When I try to login using 'sa' and SQL Server Authentication there is no
> problem.
> I've tried to find out what error 18456 is but no luck. Could anyone help
> me please?
> Cheers,
> Chris
>|||Error 18456 is "login failed for user xxx"...the error you
are getting. You have something incorrect with adding the
windows account to the logins or the permissions you have
set for the login. Try deleting the login and then try
adding it again. Make sure the login has access to whatever
database you have set up as the default database.
-Sue
On Tue, 31 Aug 2004 11:34:56 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hi,
>I've just installed SQL Server 2005 Beta 2 and added Active Directory
>account to our SQL Server (under Database/Security/Logins). However, when I
>try to login using the Windows Authentication, I get this error message:
>Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
>where DOMAIN\user is really my domain-account, which I rather not publish.
>When I try to login using 'sa' and SQL Server Authentication there is no
>problem.
>I've tried to find out what error 18456 is but no luck. Could anyone help m
e
>please?
>Cheers,
>Chris
>|||Hello
I deleted and re-added the account and I also gave it access to every
database with db_owner on every database. I also made the account a member
of the sysadmin role. Still no luck

The account is in a Active Directory, could this be the problem?
Cheers,
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:9rlpj0982j03evgpta2vla52c2jrtlg9md@.
4ax.com...
> Error 18456 is "login failed for user xxx"...the error you
> are getting. You have something incorrect with adding the
> windows account to the logins or the permissions you have
> set for the login. Try deleting the login and then try
> adding it again. Make sure the login has access to whatever
> database you have set up as the default database.
> -Sue
> On Tue, 31 Aug 2004 11:34:56 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Are you a member of a group that has been denied access to
the server? Did you try another Windows account and test
with that?
-Sue
On Tue, 7 Sep 2004 14:53:32 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hello
>I deleted and re-added the account and I also gave it access to every
>database with db_owner on every database. I also made the account a member
>of the sysadmin role. Still no luck

>The account is in a Active Directory, could this be the problem?
>Cheers,
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:9rlpj0982j03evgpta2vla52c2jrtlg9md@.
4ax.com...
>|||Hello,
I think I have found the problem. When I add my login (DOMAIN\USER) using
the Microsoft SQL Server Management Studio (2005 Beta 2), the property
"Server Access" is set to "Via Group Membership". If I change this to
"Permit" I can login!
My question is: What is "Via Group Membership" and is this the best practice
when adding Windows logins?
Thanks,
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:90psj0p1dethn063mh6sd61u9fi93c1ec9@.
4ax.com...
> Are you a member of a group that has been denied access to
> the server? Did you try another Windows account and test
> with that?
> -Sue
> On Tue, 7 Sep 2004 14:53:32 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Via group membership means the login was has access to SQL
Server through their membership in a windows group.
Managing logins through windows group can definitely make
the management of logins much easier.
-Sue
On Wed, 8 Sep 2004 10:31:06 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hello,
>I think I have found the problem. When I add my login (DOMAIN\USER) using
>the Microsoft SQL Server Management Studio (2005 Beta 2), the property
>"Server Access" is set to "Via Group Membership". If I change this to
>"Permit" I can login!
>My question is: What is "Via Group Membership" and is this the best practic
e
>when adding Windows logins?
>Thanks,
>Chris
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:90psj0p1dethn063mh6sd61u9fi93c1ec9@.
4ax.com...
>|||I see, the thing is, there is no added Windows groups login in the SQL
Server. I tried adding DOMAIN\Administrators but I got the errore message:
"The login 'DOMAIN\Administrators' does not exist. (Microsoft SQL Server,
Error: 15007)"
But I'm sure it exists since I browsed to it using the Active Directory. Is
there some limitation to adding the DOMAIN\Administrators group? Should I
try to set up yet another group for database access?
Thanks for your help!
/Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8pttj05a5jihmdoqe1ekg4iufo7er08j5f@.
4ax.com...
> Via group membership means the login was has access to SQL
> Server through their membership in a windows group.
> Managing logins through windows group can definitely make
> the management of logins much easier.
> -Sue
> On Wed, 8 Sep 2004 10:31:06 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Chris,
I'm not real clear on when you are receiving this error. It doesn't
look like something you would get when you actually try to add the
login. Try add the account using Query Analyzer instead and executing
sp_grantlogin. The help file has more information on sp_grantlogin.
Whether you set up another group or not depends upon how you are going
to design your security model. Using Windows groups certainly can be
easier but whether that works for you or not depends on how your
windows groups are set up, how well they reflect the access, security
needs of the applications that will use the databases on the server,
etc.
-Sue
On Wed, 8 Sep 2004 14:21:49 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>I see, the thing is, there is no added Windows groups login in the SQL
>Server. I tried adding DOMAIN\Administrators but I got the errore message:
>"The login 'DOMAIN\Administrators' does not exist. (Microsoft SQL Server,
>Error: 15007)"
>But I'm sure it exists since I browsed to it using the Active Directory. Is
>there some limitation to adding the DOMAIN\Administrators group? Should I
>try to set up yet another group for database access?
>Thanks for your help!
>/Chris
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:8pttj05a5jihmdoqe1ekg4iufo7er08j5f@.
4ax.com...
>|||Hi,
When I use the Microsoft SQL Server Management Studio, which is in SQL
Server 2005 and is equivalent to Enterprise Manager for SQL Server 2000, to
add a Windows login, the login's Server access property is set to "Via group
membership".
If I use the stored procedures sp_grantlogin on SQL Server 2005, the login's
Server access property is set to "Permit".
If I use the old Enterprise Manager for SQL Server 2000, the login's Server
access property is set to "Permit".
Why does the SQL Server Management Studio (2005) set the Server access
property to "Via group membership" instead of "Permit". I know this is a
beta and an answer might not be possible to give...
Thanks for helping me out, I no longer experience the 18456 error, this is
just out of curiousity

/Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:iq7uj0tv8g78vlco9b6dr4m36uq1b3n1tc@.
4ax.com...
> Chris,
> I'm not real clear on when you are receiving this error. It doesn't
> look like something you would get when you actually try to add the
> login. Try add the account using Query Analyzer instead and executing
> sp_grantlogin. The help file has more information on sp_grantlogin.
> Whether you set up another group or not depends upon how you are going
> to design your security model. Using Windows groups certainly can be
> easier but whether that works for you or not depends on how your
> windows groups are set up, how well they reflect the access, security
> needs of the applications that will use the databases on the server,
> etc.
> -Sue
> On Wed, 8 Sep 2004 14:21:49 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>

Error 18456: Login failed for user 'Distributor_admin'

Hi,
When going through the replication wizard to setup transactional replication
the following error is returned when it starts to setup replication.
SQL Server Enterprise Manager could not configure '<four part servername>'
as the distributor for '<four part servername>'
Error 18456: Login failed for user 'Distributor_admin'
Can someone please help. Is it because of the four part server name?
Thanks
It could be. What happens when you create an alias using the client network
utility. After doing this de-register your server in EM, and then reregister
it with the new one part alias.
Is the distributor local?
"mm" <postto@.news.com> wrote in message
news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> Hi,
> When going through the replication wizard to setup transactional
> replication
> the following error is returned when it starts to setup replication.
> SQL Server Enterprise Manager could not configure '<four part servername>'
> as the distributor for '<four part servername>'
> Error 18456: Login failed for user 'Distributor_admin'
>
> Can someone please help. Is it because of the four part server name?
> Thanks
>
>
|||Hi Hilary,
There is no alisa defined in the the client network utility.
This happens when trying to setup a local distributor. However there is a
database on the SQL server that subscribes to a remote distributor.
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eiLeJZi$EHA.3472@.TK2MSFTNGP14.phx.gbl...
> It could be. What happens when you create an alias using the client
network
> utility. After doing this de-register your server in EM, and then
reregister[vbcol=seagreen]
> it with the new one part alias.
> Is the distributor local?
>
> "mm" <postto@.news.com> wrote in message
> news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
servername>'
>

Error 18456, State 28000

Hello,
Running SQL Server 2000... I've installed a new instance of this on a new
server (to migrate from server1 to server2).
On server1, i have a group set up (domain/SQLGroup)...
On server2, i have the exact same group set up... unfortunately all the
users in this group doesn't get recognized by my new sql installation. I
get the error above (SQL Error 18456, State '28000')..
I can change permissions for all the users in this group to have "Domain
Admins", but obviously i don't want to do that... by doing this though, all
access works as before...
SP4 is installed on server2, but not on server1...
Does anyone have any suggestions on how to proceed with this?
Thanks.One thing i should add about this...
Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
Server2 is just windows 2003, and is dedicated to sql server 2000...
Thanks,
...Robin
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:u1nxZaSUGHA.4952@.TK2MSFTNGP09.phx.gbl...
> Hello,
> Running SQL Server 2000... I've installed a new instance of this on a new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000')..
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>

Error 18456" error message when you specify configuration database

I appreciate if some one please help me to solve the following problem
SYMPTOMS
I am runnning the Setup program to install Microsoft Windows SharePoint
Services. After the Setup program is completed successfully, I configure
Windows SharePoint Services settings in SharePoint Central Administration. I
then specify configuration database settings on the Set Configuration
Database Server page of SharePoint Central Administration, and then I click
OK. Then, I receive one of the following error messages:
"Error 18456" error message when you specify configuration database settings
on the Set Configuration Database Server page of SharePoint Central
Administrator"
I have gone through the article on
http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
Please let me know if some one came across this problem & i could solve it
with your support
Thanks in advance
RegardsError 18456
Severity Level 14
Message Text
Login failed for user '%ls'.
Make sure that the user you specified is correct and has the correct password.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Yakoob" wrote:
> I appreciate if some one please help me to solve the following problem
>
> SYMPTOMS
> I am runnning the Setup program to install Microsoft Windows SharePoint
> Services. After the Setup program is completed successfully, I configure
> Windows SharePoint Services settings in SharePoint Central Administration. I
> then specify configuration database settings on the Set Configuration
> Database Server page of SharePoint Central Administration, and then I click
> OK. Then, I receive one of the following error messages:
> "Error 18456" error message when you specify configuration database settings
> on the Set Configuration Database Server page of SharePoint Central
> Administrator"
> I have gone through the article on
> http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
> Please let me know if some one came across this problem & i could solve it
> with your support
> Thanks in advance
> Regards|||Here it is not asking for any user, In database connection type, i have using
the option "user windows authentication" so i dont know which account its
going to use here to create the database.
Please help me out
Thanks
"Mike Epprecht (SQL MVP)" wrote:
> Error 18456
> Severity Level 14
> Message Text
> Login failed for user '%ls'.
>
> Make sure that the user you specified is correct and has the correct password.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Yakoob" wrote:
> > I appreciate if some one please help me to solve the following problem
> >
> >
> > SYMPTOMS
> >
> > I am runnning the Setup program to install Microsoft Windows SharePoint
> > Services. After the Setup program is completed successfully, I configure
> > Windows SharePoint Services settings in SharePoint Central Administration. I
> > then specify configuration database settings on the Set Configuration
> > Database Server page of SharePoint Central Administration, and then I click
> > OK. Then, I receive one of the following error messages:
> > "Error 18456" error message when you specify configuration database settings
> > on the Set Configuration Database Server page of SharePoint Central
> > Administrator"
> >
> > I have gone through the article on
> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me out.
> > Please let me know if some one came across this problem & i could solve it
> > with your support
> > Thanks in advance
> > Regards|||It's probably [NT AUTHORITY\NETWORK SERVICE]. You should be able to see the
error in the SQL Error log (Open SQL Enterprise Manager and connect to the
SQL Server instance in question and navigate to Management>SQL Server Logs)
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Yakoob" <Yakoob@.discussions.microsoft.com> wrote in message
news:D91EF3D6-7AE4-4707-9F60-FEEFB797B771@.microsoft.com...
> Here it is not asking for any user, In database connection type, i have
> using
> the option "user windows authentication" so i dont know which account its
> going to use here to create the database.
> Please help me out
> Thanks
> "Mike Epprecht (SQL MVP)" wrote:
>> Error 18456
>> Severity Level 14
>> Message Text
>> Login failed for user '%ls'.
>>
>> Make sure that the user you specified is correct and has the correct
>> password.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>>
>> "Yakoob" wrote:
>> > I appreciate if some one please help me to solve the following problem
>> >
>> >
>> > SYMPTOMS
>> >
>> > I am runnning the Setup program to install Microsoft Windows SharePoint
>> > Services. After the Setup program is completed successfully, I
>> > configure
>> > Windows SharePoint Services settings in SharePoint Central
>> > Administration. I
>> > then specify configuration database settings on the Set Configuration
>> > Database Server page of SharePoint Central Administration, and then I
>> > click
>> > OK. Then, I receive one of the following error messages:
>> > "Error 18456" error message when you specify configuration database
>> > settings
>> > on the Set Configuration Database Server page of SharePoint Central
>> > Administrator"
>> >
>> > I have gone through the article on
>> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me
>> > out.
>> > Please let me know if some one came across this problem & i could solve
>> > it
>> > with your support
>> > Thanks in advance
>> > Regards|||Thanks for your reply, yes i understand that it iw using NT AUTHORITY\NETWORK
SERVICE, but even this i didn't find in SQL server logs as you have
mentioned. If i have to check for correct password then where? because i am
not providing here any password during "set configuration database server". I
am selecting the following options which is mandatory as per installation
guide for MS project 2003 server.
1. Database server = "i give sql server name"
2. SQL server database name = "database name as sharepointdb"
3. selected the option "use windows authentication
4. then last option " users already have domain accounts. Do not creat
active directory accounts.
I dont see any NT AUTHORITY account in active directory to give permission
for database create or to see for its password, please let me know
Thanks & Regards
"Jasper Smith" wrote:
> It's probably [NT AUTHORITY\NETWORK SERVICE]. You should be able to see the
> error in the SQL Error log (Open SQL Enterprise Manager and connect to the
> SQL Server instance in question and navigate to Management>SQL Server Logs)
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Yakoob" <Yakoob@.discussions.microsoft.com> wrote in message
> news:D91EF3D6-7AE4-4707-9F60-FEEFB797B771@.microsoft.com...
> > Here it is not asking for any user, In database connection type, i have
> > using
> > the option "user windows authentication" so i dont know which account its
> > going to use here to create the database.
> > Please help me out
> >
> > Thanks
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> >> Error 18456
> >> Severity Level 14
> >> Message Text
> >> Login failed for user '%ls'.
> >>
> >>
> >> Make sure that the user you specified is correct and has the correct
> >> password.
> >>
> >> Regards
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >>
> >>
> >> "Yakoob" wrote:
> >>
> >> > I appreciate if some one please help me to solve the following problem
> >> >
> >> >
> >> > SYMPTOMS
> >> >
> >> > I am runnning the Setup program to install Microsoft Windows SharePoint
> >> > Services. After the Setup program is completed successfully, I
> >> > configure
> >> > Windows SharePoint Services settings in SharePoint Central
> >> > Administration. I
> >> > then specify configuration database settings on the Set Configuration
> >> > Database Server page of SharePoint Central Administration, and then I
> >> > click
> >> > OK. Then, I receive one of the following error messages:
> >> > "Error 18456" error message when you specify configuration database
> >> > settings
> >> > on the Set Configuration Database Server page of SharePoint Central
> >> > Administrator"
> >> >
> >> > I have gone through the article on
> >> > http://support.microsoft.com/?kbid=889646&FR=1 but it does not help me
> >> > out.
> >> > Please let me know if some one came across this problem & i could solve
> >> > it
> >> > with your support
> >> > Thanks in advance
> >> > Regards
>
>

Error 18456" error message when you specify configuration database

Error 18456 with logon using Windows accounts

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?

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

error 18456 when trying to connect to 2005 using odbc

Hi all

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

error 18456 when running job

sql2k sp3
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.

Error 18456 State 6

Hi,

I am trying to connect to a remote SQL server via Management Studio. I am using the windows credentials I use to log into the computer but when I enter the same domain\username and password I get error 18456. I check the logs and see it is a state 6 error. After checking http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx I see that means

Attempt to use a Windows login name with SQL Authentication

Is it possible for me to access a SQL server remotely?

Thanks

From your description, I would assume that you chose “SQL Server Authentication” and provided a user name that was a Windows user name, correct? “SQL Server Authentication” is used only for principals whose information is completely under the control of the SQL Server instance (i.e. the SID, login and password are only valid to SQL Server).

When using Windows authentication the server will use the Windows token from your client program (in this case Management Studio) to authenticate the connection, without the need to type any login or password.

When you connect to SQL Server using Management Studio, make sure you choose the option “Windows Authentication” for the “Authentication” value, the user name and password fields should be grayed out.

I hope this helps, but let us know if you still have any questions.

-Raul Garcia

SDE/T

SQL Server Engine

sql

Error 18456 Severity: 14 State 11 problem

I am installing diskeeper administrator on one server with at database on our sql2005 server. When I am trying to connect to the database the diskeeper software says verify username and password. I try to connect using windows authentication .And in the serverlog this error occurs

2006-11-27 15:04:56.01 Logon Login failed for user 'NB\Servername$'. [CLIENT: "Ipadress"]

2006-11-27 15:04:56.01 Logon Error: 18456, Severity: 14, State: 11.

When i try to connect with Sql server authentication, this error occurs in the log:

2006-11-27 15:48:35.46 Logon Login failed for user 'NB\SERVERNAME$'. [CLIENT: ipadress

]2006-11-27 16:04:22.94 Logon Error: 18456, Severity: 14, State: 16.

I have tried to disable filesharing, and run installation of diskeepper as the domain administrator. But the same error occurs.

Can anyone help me with this

Regards Oyvind

State 11 indicates an error determining the database to be used after authentication. This could happen if the database cannot be accessed for some reason. You could try to connect to the master database initially, to see if that works, then change context to the database that you normally use and see what error you encounter, if any.

However, I am not familiar with the diskeeper software and I don't understand its relation with SQL Server, so I'm not sure how to help you further.

Thanks
Laurentiu

|||

Diskeeper do not have any link with SQL Server in this case, and also it is no use in running for linked server related error.

What is the privilege for the account used on the linked server?

Refer to KBA http://support.microsoft.com/kb/889646 fyi.

|||

The privilege for the account is sysadmin.

The default database is master.

I also tried to connect with odbc, but the same error occurs

Regards

Oyvind

|||have you contacted the vendor in this case?|||

Correction to my previous post: the state discussion applies to state 16, not to state 11.

State 11 indicates a different problem.

What is strange is that, while you mention using Windows and SQL authentication, both connections appear to be attempted via Windows authentication, using the machine account credentials.

Best thing would be to check with the diskeeper customer support.

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

ERROR 18456 not being logged in event viewer

Hi.
I made an alert that will email me whenever someone causes error 18456 to be
raised... My thinking behind this is that if anyones trying to access my
server and FAILS, then they are probably up to no good.
So anyway... This alert was created... I verified that SQL Server Agent
Mail is running, as is SQL Mail... so thats not the point of failure.
I just attempted to log in with sa and a fake password. It predictably did
not give me access to the databases, but the event was NOT logged to the
application log. I checked in enterprise manager, and the checkbox that
says "Always write to Windows eventlog" is checked.
I also verified that the SQL Server Agent is running under a local and
domain admin, and this is the case.
Does anybody have any ideas?
Thanks in advance,
-- Jason
I assume that this error number is failed login. If so, you handle this in a special way. EM, right-click your
server, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jeigh" <folkens.jason@.acd.net> wrote in message news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...
> Hi.
> I made an alert that will email me whenever someone causes error 18456 to be
> raised... My thinking behind this is that if anyones trying to access my
> server and FAILS, then they are probably up to no good.
> So anyway... This alert was created... I verified that SQL Server Agent
> Mail is running, as is SQL Mail... so thats not the point of failure.
> I just attempted to log in with sa and a fake password. It predictably did
> not give me access to the databases, but the event was NOT logged to the
> application log. I checked in enterprise manager, and the checkbox that
> says "Always write to Windows eventlog" is checked.
> I also verified that the SQL Server Agent is running under a local and
> domain admin, and this is the case.
> Does anybody have any ideas?
> Thanks in advance,
> -- Jason
>
|||Are you referring to the "Audit Level" raido buttons?
Changing it from "None" to "Failure" didnt seem to make that much of a
difference. Am I looking at the right thing?
Thanks,
-- Jason
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:O6NBB4STEHA.2416@.TK2MSFTNGP09.phx.gbl...
> I assume that this error number is failed login. If so, you handle this in
a special way. EM, right-click your
> server, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jeigh" <folkens.jason@.acd.net> wrote in message
news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...[vbcol=seagreen]
to be[vbcol=seagreen]
my[vbcol=seagreen]
Agent[vbcol=seagreen]
did
>
|||Yep, that's the one I was referring to. So you don't see the events logged to eventlog, after checking the
checkbox. Strange, I know it work for me. Perhaps time to open a case with MS?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jeigh" <folkens.jason@.acd.net> wrote in message news:p7GdnZI30-avWFjd4p2dnA@.giganews.com...
> Are you referring to the "Audit Level" raido buttons?
> Changing it from "None" to "Failure" didnt seem to make that much of a
> difference. Am I looking at the right thing?
> Thanks,
> -- Jason
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:O6NBB4STEHA.2416@.TK2MSFTNGP09.phx.gbl...
> a special way. EM, right-click your
> news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...
> to be
> my
> Agent
> did
>

Error 18456 Login failed for user domain\user

We have an application that logs into our SQL Server 2000 using ODBC. All
service packs and critical updates are current on the server and clients.
SQL Server uses mixed authentification and runs under a domain account, the
users login with their domain\username, or at least they used to. Nobody
seems to know exactly when this stopped working, and of course, nobody said
anything until this week. Attempting to login now fails with error 18456
login failed for user domain\username. I've foolwed all the debugging info I
can find on Microsofts site. Running osql, I can log in using windows
authentification and SQL Server accounts with no problem. Trying to use
domain\username fails. I've been through everything from DNS to SQL Server
settings to client settings with no resolution. Anybody have an idea where
else to look?
Any hints would be greatly appreciated.
BruceHi Bruce,
Thank you for use the newsgroup and it is my pleasure to help you with you
issue.
From you information, you application, which used to work fine now got
error message
Could you check if the ODBC connection is made through the standard
security of SQL Server of trusted connection security? Is the SQL Server
authentication mode match the security option of ODBC connection? Could you
using the Query Analyzer to connect the SQL Server? That is, if you use the
standard security, such as use the account 'sa', when using 'sa' in Query
Analyzer, could it connect the SQL Server. When it is a Windows
authentication, when connect the SQL Server by Query Analyzer, you should
choose the Windows Authenticatin in the Query Analyzer.
Looking forward to your response. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Baisong:
Using Windows Authentification or Sql Server Authentification both work
fine.
If I'm logged into the domain I can run
osql -S SERVER -d Test -E
or
osql -S SERVER -d Test -U SA -P password
with no problem I can connect through Query analyzer either way.
if I try
osql -S SERVER -d Test -U domain\username -P password
it fails with the message Error 18456 Login failed for user domain\username.
The application we are using was working with the domain\username login, I
can't use Windows Integrated security with it, and I really do not want to
setup and manage 50+ SQL Server accounts. I am assuming that something has
changed in the authentification / delegation process and am working through
that now. As far as I can tell nothing has changed, but obviously something
has.
Any ideas would be appreciated.
Bruce
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:EKzqmHs7DHA.1992@.cpmsftngxa07.phx.gbl...
> Hi Bruce,
> Thank you for use the newsgroup and it is my pleasure to help you with you
> issue.
> From you information, you application, which used to work fine now got
> error message
> Could you check if the ODBC connection is made through the standard
> security of SQL Server of trusted connection security? Is the SQL Server
> authentication mode match the security option of ODBC connection? Could
you
> using the Query Analyzer to connect the SQL Server? That is, if you use
the
> standard security, such as use the account 'sa', when using 'sa' in Query
> Analyzer, could it connect the SQL Server. When it is a Windows
> authentication, when connect the SQL Server by Query Analyzer, you should
> choose the Windows Authenticatin in the Query Analyzer.
> Looking forward to your response. Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Hi Bruce,
Thank you for your update.
For the 'osql -S SERVER -d Test -U domain\username -P password' which
failed with the error message, could you check if it is a valid SQL Server
login? You could check it by unfolder the database, unfoulder the
'Security', then in the logins, is the above 'domain\username' in the
logins?
Looking forward to your response. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Yes, it is a valid login and the password is correct. The account also has
privledges (dbowner + our SQL_Admin role) to access the test database. It
works fine with Windows Integrated Security, so I don't think it is related
to SQL Server privledges, my guess is that something has changed in the
authentification authorization or delegation between the domain and the
server or the client.
The client computers are running MDAC 2.8 or 2.7RTM, and component checker
says they are current and all is well. Servers and clients are current on
patches, SQL Server is current. I've been throgh every article I can find on
MSDN that remotely deals with this error, and everything seems to check out.
I'm sure there is some little thing I'm overlooking, but I'm totally stumped
at this point.
Bruce
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:ZZofg867DHA.2508@.cpmsftngxa07.phx.gbl...
> Hi Bruce,
> Thank you for your update.
> For the 'osql -S SERVER -d Test -U domain\username -P password' which
> failed with the error message, could you check if it is a valid SQL Server
> login? You could check it by unfolder the database, unfoulder the
> 'Security', then in the logins, is the above 'domain\username' in the
> logins?
> Looking forward to your response. Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Bruce,
The exact same thing happen here - ODBC connections that had worked
stopped working. We THINK it was related to installing patches but not
the full SP3a running on SQL 2000. We know installing SP3a fixed it.
An easy test to see if it's the same problem - in the ODBC config, set
the server name servername.subdomain.domain.?, check with the network
people for the full name if you need to.
If it works then maybe install/reinstall SP3a on the server will help.
SQL DBA in Richmond, VA
PS - I know 4 locales that suddenly experienced this same problem.
Maybe triggered by Windows critical update?
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Error 18456 Login failed for user 'distributor_admin'

Hello,
Each time I try to configure my SQL 2000 server as a distributor using the
Wizard I get the following error message:
Error 18456 Login failed for user 'distributor_admin'
Can anyone help with this?
Regards
Dave
are you using a remote distributor?
If do your Publisher has the incorrect administrative link password. Connect
to your Publisher in EM. Go to Tools, replication, configure publishers,
Subscribers, and distributor, and click on the Publisher's tab. In the
Administrative link password dialog enter the administrative link password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Check to make sure that the computer you are trying to access which has the
group 'distributor_admin' actually has the administrative access it
requires, both in the security file for the server and in the user security
for the individual database. If you play with file permissions, you may
want to check those as well. If you don't work with the file permissions
forget I added this. If you are on a network and the network administrator
has not enabled the administrator rights for the 'distributor_admin' group,
you may need to ask the administrator to grant the permission over the
network.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Sorry, I should have given a bit more info. I'm trying to set up one
machine to replicate the contents of one table to a second machine
(not located in the same place)
I figured I needed to set Machine A up as a distibutor and then allow
Machine B to have a subscription.
I don't have the 'Publisher's tab' as I have not configured it to be a
publisher yet, this I can't do as I get the aforementioned error.
I can't see a login 'distributor_admin' in Ent Mgr.
I was assuming (maybe incorrectly) that I don't need to do anything on
Machine B in order to be able to set up the publishing side on Machine
A.
Hope this helps you to help me

Dave
|||Dave,
You're in over my head, but it sounds like a permissions error.
If you go to services and select the properties of your server, you'll see
the account that the machine starts in. Check to see that account is
someone who is in the 'distributor_admin' group. You can browse for it
there - and both sides need to be members of that group since it appears to
have the permission to run the transaction.
Hope this helps.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407180039.1d325c91@.posting.google.c om...
> Sorry, I should have given a bit more info. I'm trying to set up one
> machine to replicate the contents of one table to a second machine
> (not located in the same place)
> I figured I needed to set Machine A up as a distibutor and then allow
> Machine B to have a subscription.
> I don't have the 'Publisher's tab' as I have not configured it to be a
> publisher yet, this I can't do as I get the aforementioned error.
> I can't see a login 'distributor_admin' in Ent Mgr.
> I was assuming (maybe incorrectly) that I don't need to do anything on
> Machine B in order to be able to set up the publishing side on Machine
> A.
> Hope this helps you to help me

> Dave
|||"Giacomo" <anonymous@.msnewsgroups.com> wrote in message news:<#HHn#qLbEHA.3792@.TK2MSFTNGP09.phx.gbl>...
> Dave,
> You're in over my head, but it sounds like a permissions error.
> If you go to services and select the properties of your server, you'll see
> the account that the machine starts in. Check to see that account is
> someone who is in the 'distributor_admin' group. You can browse for it
> there - and both sides need to be members of that group since it appears to
> have the permission to run the transaction.
> Hope this helps.
> Giac
I don't have a 'distributor_admin' group in either Ent Mgr or Computer Manager.
|||Dave,
see if this link applies to you - there are 2 workarounds suggested, one of
which is the same as Hilary's first reply.
http://support.microsoft.com/default...;en-us;Q225129
HTH,
Paul Ibison
|||Thanks for the suggestions. I had set up an alias sql server as the
default had been set up as (local) which would not work.
In the end I just removed and re-added the only registration so that
it had the same name as the server and all worked fine.
Thanks again
sql

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to th
e
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'
Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'sql

Error 18456 - domain admins only users that can authenticate

Server 2003
SQL 2000 SP3a
I have my server set up and my ODBC client configured. When I log in as
myself, as a domain admin, I can set my authentication to Windows (in my
ODBC), when I log on as a Domain Users, I cannot.
I get and error 18456. My server properties show SQL Server and Windows
authentication is allowed and there is no semi-colon in my password. What
security setting am I missing to allow my domain users to authenticate via
Windows authentication?
TIAHi,
Did you gave domain OS user access to SQL Server?
If not; open Enterprise manager and use Security option to add the Domain
user/group to SQL Server.
Thanks
Hari
SQL Server MVP
"dsb" <dsb@.discussions.microsoft.com> wrote in message
news:F7A3CA7A-1012-4673-8CDF-9B4B66583A3A@.microsoft.com...
> Server 2003
> SQL 2000 SP3a
> I have my server set up and my ODBC client configured. When I log in as
> myself, as a domain admin, I can set my authentication to Windows (in my
> ODBC), when I log on as a Domain Users, I cannot.
> I get and error 18456. My server properties show SQL Server and Windows
> authentication is allowed and there is no semi-colon in my password. What
> security setting am I missing to allow my domain users to authenticate via
> Windows authentication?
> TIA

Error 18456 - Connecting via DSN

Hi,
My MS Access application needs to connect to a SQL server via a system
dsn. However, I keep getting the error 18456 - Login failed for user 'xxxx'.
The surprising bit is I am able to use the same password and user id and
connect to the server using Enterprise Manager. Any ideas on why the dsn is
throwing this error? Connection is via SQL authentication.
Any help would be much appreciated.
Rgds,
San
Any success with this? I'm having the exact same problem. I was doing
some permissions stuff the other day so I'm sure I hosed something up.
goosesr
Posted via http://www.codecomments.com
|||Yeah, I was able to resolve the issue by updating the links in Access. Right
click on the link table, select Link Table Manager, select, promt for new
location,a nd on ok, select the DSN again...
Hope it works for you too !
~San
"goosesr" wrote:

> Any success with this? I'm having the exact same problem. I was doing
> some permissions stuff the other day so I'm sure I hosed something up.
>
> --
> goosesr
> Posted via http://www.codecomments.com
>

Error 18456 - Connecting via DSN

Hi,
My MS Access application needs to connect to a SQL server via a system
dsn. However, I keep getting the error 18456 - Login failed for user 'xxxx'.
The surprising bit is I am able to use the same password and user id and
connect to the server using Enterprise Manager. Any ideas on why the dsn is
throwing this error? Connection is via SQL authentication.
Any help would be much appreciated.
Rgds,
SanAny success with this? I'm having the exact same problem. I was doing
some permissions stuff the other day so I'm sure I hosed something up.
goosesr
---
Posted via http://www.codecomments.com
---|||Yeah, I was able to resolve the issue by updating the links in Access. Right
click on the link table, select Link Table Manager, select, promt for new
location,a nd on ok, select the DSN again...
Hope it works for you too !
~San
"goosesr" wrote:

> Any success with this? I'm having the exact same problem. I was doing
> some permissions stuff the other day so I'm sure I hosed something up.
>
> --
> goosesr
> ---
> Posted via http://www.codecomments.com
> ---
>

Error 18456

I got an error of login "sa" with Error 18456 Level 14 . Server A is the MSSQL Server where the database sit and the other Server B is just with MSSQL Server tool which act as a Terminal Service and have the Accounting applications.The Accounting applicat
ion unable to perform its database transfer to another application on the Terminal Service. We use Window 2003 Server. The application programs are fine. The ODBC, MSSQL and application "sa" password are identical. Any idea? Thanks
Hi
Please enable security Audit, and check the detailed error in the security
event log.
To me it looks like a double hop issue, please check the link mentioned
below
http://msdn.microsoft.com/library/de...urity_2gmm.htm
HTH
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Li" <Li@.discussions.microsoft.com> wrote in message
news:391C4119-F467-4017-8D97-960644E93B91@.microsoft.com...
>I got an error of login "sa" with Error 18456 Level 14 . Server A is the
>MSSQL Server where the database sit and the other Server B is just with
>MSSQL Server tool which act as a Terminal Service and have the Accounting
>applications.The Accounting application unable to perform its database
>transfer to another application on the Terminal Service. We use Window 2003
>Server. The application programs are fine. The ODBC, MSSQL and application
>"sa" password are identical. Any idea? Thanks
>

Error 18456

I got an error of login "sa" with Error 18456 Level 14 . Server A is the MSSQL Server where the database sit and the other Server B is just with MSSQL Server tool which act as a Terminal Service and have the Accounting applications.The Accounting application unable to perform its database transfer to another application on the Terminal Service. We use Window 2003 Server. The application programs are fine. The ODBC, MSSQL and application "sa" password are identical. Any idea? ThanksHi
Please enable security Audit, and check the detailed error in the security
event log.
To me it looks like a double hop issue, please check the link mentioned
below
http://msdn.microsoft.com/library/default.asp?URL=/library/psdk/sql/ad_security_2gmm.htm
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Li" <Li@.discussions.microsoft.com> wrote in message
news:391C4119-F467-4017-8D97-960644E93B91@.microsoft.com...
>I got an error of login "sa" with Error 18456 Level 14 . Server A is the
>MSSQL Server where the database sit and the other Server B is just with
>MSSQL Server tool which act as a Terminal Service and have the Accounting
>applications.The Accounting application unable to perform its database
>transfer to another application on the Terminal Service. We use Window 2003
>Server. The application programs are fine. The ODBC, MSSQL and application
>"sa" password are identical. Any idea? Thanks
>sql

Error 18456

I keep getting these error messages and cannot figure out where the problem
is. Could someone help me narrow this down a bit?
11/07/2007 10:45:18,Logon,Unknown,Login failed for user
'CVILLE\Administrator'. [CLIENT: 192.168.10.26]
11/07/2007 10:45:18,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1
6.
Thanks,
Marty ShifflettMarty
Do you see it in thr ERROR.LOG or when you attempt to connect?
"Marty Shifflett" <MartyShifflett@.discussions.microsoft.com> wrote in
message news:90453E52-BA3A-4487-B7B2-9444A75E07A8@.microsoft.com...
>I keep getting these error messages and cannot figure out where the problem
> is. Could someone help me narrow this down a bit?
> 11/07/2007 10:45:18,Logon,Unknown,Login failed for user
> 'CVILLE\Administrator'. [CLIENT: 192.168.10.26]
> 11/07/2007 10:45:18,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
> 16.
> Thanks,
> Marty Shifflett|||Only in the error log.
"Uri Dimant" wrote:

> Marty
> Do you see it in thr ERROR.LOG or when you attempt to connect?
>
> "Marty Shifflett" <MartyShifflett@.discussions.microsoft.com> wrote in
> message news:90453E52-BA3A-4487-B7B2-9444A75E07A8@.microsoft.com...
>
>|||State 16 means that target database cannot be accessed. Check that
application requests valid database upon connection. Also check that the
login has valid default database set.
Martin Rakhmanov
Marty Shifflett wrote:
> I keep getting these error messages and cannot figure out where the proble
m
> is. Could someone help me narrow this down a bit?
> 11/07/2007 10:45:18,Logon,Unknown,Login failed for user
> 'CVILLE\Administrator'. [CLIENT: 192.168.10.26]
> 11/07/2007 10:45:18,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
> Thanks,
> Marty Shifflett|||Marty
Perhaps some one (even hacker) tries to reach your server by using this
Login
"Marty Shifflett" <MartyShifflett@.discussions.microsoft.com> wrote in
message news:5C82F61A-7C99-4D0C-9AA8-74BC57887518@.microsoft.com...[vbcol=seagreen]
> Only in the error log.
> "Uri Dimant" wrote:
>

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.

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.
>
>.
>

Error 18456

I got an error of login "sa" with Error 18456 Level 14 . Server A is the MSS
QL Server where the database sit and the other Server B is just with MSSQL S
erver tool which act as a Terminal Service and have the Accounting applicati
ons.The Accounting applicat
ion unable to perform its database transfer to another application on the Te
rminal Service. We use Window 2003 Server. The application programs are fine
. The ODBC, MSSQL and application "sa" password are identical. Any idea? Tha
nksHi
Please enable security Audit, and check the detailed error in the security
event log.
To me it looks like a double hop issue, please check the link mentioned
below
mm.htm" target="_blank">http://msdn.microsoft.com/library/d...g
mm.htm
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Li" <Li@.discussions.microsoft.com> wrote in message
news:391C4119-F467-4017-8D97-960644E93B91@.microsoft.com...
>I got an error of login "sa" with Error 18456 Level 14 . Server A is the
>MSSQL Server where the database sit and the other Server B is just with
>MSSQL Server tool which act as a Terminal Service and have the Accounting
>applications.The Accounting application unable to perform its database
>transfer to another application on the Terminal Service. We use Window 2003
>Server. The application programs are fine. The ODBC, MSSQL and application
>"sa" password are identical. Any idea? Thanks
>

Tuesday, March 27, 2012

Error 18452 Login failed for user <null>. The user account is not

We have a SQL 2005 installation using SQL and Windows Authentication. We
have a login that is mapped to a active directory group and has the
appropriate permissions to the database. However, when we try to create
an ODBC connection to the server from an XP client (and the user is a
member of the appropriate domain group) we get the above mentioned error.
Also logged on the SQL server is the following error:
SSPI handshake failed with error code 0x8009030c...
The only info I can find on this error has to do with IIS
configurations, but I don't see what IIS has to do with this as we are
only trying to make an ODBC connection.Maybe your service account is Local System.
You can change to AD Service account.
"Jan Leste"?? ??? ??:

> We have a SQL 2005 installation using SQL and Windows Authentication. We
> have a login that is mapped to a active directory group and has the
> appropriate permissions to the database. However, when we try to create
> an ODBC connection to the server from an XP client (and the user is a
> member of the appropriate domain group) we get the above mentioned error.
> Also logged on the SQL server is the following error:
> SSPI handshake failed with error code 0x8009030c...
> The only info I can find on this error has to do with IIS
> configurations, but I don't see what IIS has to do with this as we are
> only trying to make an ODBC connection.
>

Thursday, March 29, 2012

Tuesday, March 27, 2012

Blog Archive

About Me