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 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 - 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 15401 adding login to SQL Server

I have a SAP Server running SQL2000 on Windows 2003.
Recently I migrated the server from a NT4 Domain to a AD Domain using
ADMT (with SID Migration for users) and everything seems ok.
Now, after one month, I have to shut down the old NT4 domain and before
doing it I have to replace the old logins in SQL with the correspondent
users in the new domain.
I applied a script which returned Error 15401: Windows NT user or group
NEWDOM\User not found. Check the name again.
I checked the KB article 324321
http://support.microsoft.com/default...b;en-us;324321
I applied the suggestion to verify if
SELECT name FROM sysxlogins WHERE sid = SUSER_SID 'NEWDOM\User')
returns a row, but this is not happening.
Then I tried to create the new login from the Enterprise Manager. So I
browse for the user and I'm able to find it (It exists! It's the same
user I use to login on the server) but when I apply the changes I get
the same 15401 Error.
So it seems that the KB article is not useful because:
1) There is no duplicate security identifier
2) It's not an authentication failure because I can login and browse
the AD. Also if I choose another AD user it works!
3) I don't think it's a case sensitivity problem because it happens
also from EM. By the way, I verified the SAMAccountName AD property of
the user and the name is all UpperCase.
I checked lots of posts dealing with this matter but they don't seem to
apply.
Any help would be greatly appreciated
Thanks
Dave
This post suggests that if all else fails, you may need to reboot the
server to refresh its locally cached credentials:
http://groups.google.co.uk/groups?hl...xa06 .phx.gbl
If you've already done that, then I would consider calling Microsoft -
if you've exhausted other resources, it's probably going to be the
fastest way to resolve the issue.
Simon

Error 15401 adding login to SQL Server

I have a SAP Server running SQL2000 on Windows 2003.
Recently I migrated the server from a NT4 Domain to a AD Domain using
ADMT (with SID Migration for users) and everything seems ok.
Now, after one month, I have to shut down the old NT4 domain and before
doing it I have to replace the old logins in SQL with the correspondent
users in the new domain.
I applied a script which returned Error 15401: Windows NT user or group
NEWDOM\User not found. Check the name again.
I checked the KB article 324321
http://support.microsoft.com/defaul...kb;en-us;324321
I applied the suggestion to verify if
SELECT name FROM sysxlogins WHERE sid = SUSER_SID 'NEWDOM\User')
returns a row, but this is not happening.
Then I tried to create the new login from the Enterprise Manager. So I
browse for the user and I'm able to find it (It exists! It's the same
user I use to login on the server) but when I apply the changes I get
the same 15401 Error.
So it seems that the KB article is not useful because:
1) There is no duplicate security identifier
2) It's not an authentication failure because I can login and browse
the AD. Also if I choose another AD user it works!
3) I don't think it's a case sensitivity problem because it happens
also from EM. By the way, I verified the SAMAccountName AD property of
the user and the name is all UpperCase.
I checked lots of posts dealing with this matter but they don't seem to
apply.
Any help would be greatly appreciated
Thanks
DaveThis post suggests that if all else fails, you may need to reboot the
server to refresh its locally cached credentials:
http://groups.google.co.uk/groups?h...tngxa06.phx.gbl
If you've already done that, then I would consider calling Microsoft -
if you've exhausted other resources, it's probably going to be the
fastest way to resolve the issue.
Simon

Error 15401 adding login to SQL Server

I have a SAP Server running SQL2000 on Windows 2003.
Recently I migrated the server from a NT4 Domain to a AD Domain using
ADMT (with SID Migration for users) and everything seems ok.
Now, after one month, I have to shut down the old NT4 domain and before
doing it I have to replace the old logins in SQL with the correspondent
users in the new domain.
I applied a script which returned Error 15401: Windows NT user or group
NEWDOM\User not found. Check the name again.

I checked the KB article 324321
http://support.microsoft.com/defaul...kb;en-us;324321
I applied the suggestion to verify if
SELECT name FROM sysxlogins WHERE sid = SUSER_SID 'NEWDOM\User')
returns a row, but this is not happening.

Then I tried to create the new login from the Enterprise Manager. So I
browse for the user and I'm able to find it (It exists! It's the same
user I use to login on the server) but when I apply the changes I get
the same 15401 Error.

So it seems that the KB article is not useful because:

1) There is no duplicate security identifier
2) It's not an authentication failure because I can login and browse
the AD. Also if I choose another AD user it works!
3) I don't think it's a case sensitivity problem because it happens
also from EM. By the way, I verified the SAMAccountName AD property of
the user and the name is all UpperCase.

I checked lots of posts dealing with this matter but they don't seem to
apply.

Any help would be greatly appreciated

Thanks
DaveThis post suggests that if all else fails, you may need to reboot the
server to refresh its locally cached credentials:

http://groups.google.co.uk/groups?h...tngxa06.phx.gbl

If you've already done that, then I would consider calling Microsoft -
if you've exhausted other resources, it's probably going to be the
fastest way to resolve the issue.

Simon

Error 15401 adding login to SQL Server

I have a SAP Server running SQL2000 on Windows 2003.
Recently I migrated the server from a NT4 Domain to a AD Domain using
ADMT (with SID Migration for users) and everything seems ok.
Now, after one month, I have to shut down the old NT4 domain and before
doing it I have to replace the old logins in SQL with the correspondent
users in the new domain.
I applied a script which returned Error 15401: Windows NT user or group
NEWDOM\User not found. Check the name again.
I checked the KB article 324321
http://support.microsoft.com/default.aspx?scid=kb;en-us;324321
I applied the suggestion to verify if
SELECT name FROM sysxlogins WHERE sid = SUSER_SID 'NEWDOM\User')
returns a row, but this is not happening.
Then I tried to create the new login from the Enterprise Manager. So I
browse for the user and I'm able to find it (It exists! It's the same
user I use to login on the server) but when I apply the changes I get
the same 15401 Error.
So it seems that the KB article is not useful because:
1) There is no duplicate security identifier
2) It's not an authentication failure because I can login and browse
the AD. Also if I choose another AD user it works!
3) I don't think it's a case sensitivity problem because it happens
also from EM. By the way, I verified the SAMAccountName AD property of
the user and the name is all UpperCase.
I checked lots of posts dealing with this matter but they don't seem to
apply.
Any help would be greatly appreciated
Thanks
DaveThis post suggests that if all else fails, you may need to reboot the
server to refresh its locally cached credentials:
http://groups.google.co.uk/groups?hl=en&lr=&client=firefox-a&rls=org.mozilla:en-GB:official&selm=0%24bzU5aCDHA.1120%40cpmsftngxa06.phx.gbl
If you've already done that, then I would consider calling Microsoft -
if you've exhausted other resources, it's probably going to be the
fastest way to resolve the issue.
Simonsql

Error 15401 Adding Domain Group to SQL Server

I have tried rebooting the system, I have ran the script to look for duplicate sids and am still having the issue when trying to add a domain group to SQL. I get the Error 15401: Windows NT user or group'mi\Trust Legal' not found. Check the name again. Running SQL 2000 Std, with SP3a, and the collation is set to SQL_Latin1_General_CP850_BIN, which makes this instance case sensitive, and the group name is spelt right and am following the case sensitivity of the name as well.

This is most likely an issue due to using a different casing. You could use a tool like sid2name, to obtain the correct casing of the group name from Windows. Then use that same casing and the statement should succeed. You might want to quickly try and capitalize the domain name: MI instead of mi; if this doesn't work then look for a sid2name tool and use it to determine the correct casing. If you cannot find such tool, you could write one easily by calling the LookupAccountSid WinAPI. You could use this post as an example: http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.

Thanks
Laurentiu

|||

Most likely the cause of such failure is because the SQL Server cannot gather the information for this account from the domain controller.

Please make sure that the service account used to run SQL Server has permission to query the domain controller (in most cases being a member of the domain is sufficient to query the domain controller), and that the machine has access to the domain controller.

-Raul Garcia

SDE/T

SQL Server Engine

|||

OK, so you've got two suggestions. To quickly discern between these, try to ACL something to the group, on the machine on which the server is installed. If you can, then the issue is not with reaching the DC; if you cannot, then it is a DC issue.

Thanks
Laurentiu

|||

Apprciate all the great advice, but nothing seemed to help.

1) I am able to login into server using the account in which sql is running under, and am able to add the group to a folder on the box

2) ran the groups sid up against sid2name, and found the following:

MI\Trust Legal, is a group

enter the username just like that when adding another user to SQL and get the same message?

|||

What command are you executing? sp_addlogin or sp_adduser?

Thanks
Laurentiu

|||

Neither actually:

use IMCEXCLUSIVE
exec sp_grantlogin 'MI\Trust Legal'

since its a domain group, from what I read grantlogin was the proper SP to use, am I wrong?

|||

No, you're right. sp_grantlogin is the right command.

You're using the right command and what appears to be the correct group name. So the issue is probably elsewhere. Does the command work for other groups or users in the same domain or does it consistently fail? What about users or groups from another domain? Does it work for local accounts? We need to try to identify the extent of this issue - it might hopefully lead us to its cause. If this is a blocking issue for you, I suggest to contact customer support as well.

Thanks
Laurentiu

|||Interesting idea, now when I try to add a user MI\15451a it works fine, when I try to add another group MI\Trust Technology Services it works just fine, just an issue so far with this one group MI\Trust Legal, arrgghhhhh this sucks. @. this point, if I cant get it fixed, I might just create a new group and go that route.|||

The group must be different in some way from the others. You might want to try downloading SQL Server 2005 Express SP1 and trying this command out on it, to see if you get the same issue.

Thanks
Laurentiu

Error 0x80070534 when changing service account

Hi people
I'm trying to change the SQL Server service account to a domain account and
got error 0x80070534. I explain a little...
I have three servers, a DC, another DC with SQL Server installed and a
member server with SQL Server installed.
In the member server I wasable to successfully change the SQL Server service
account (and for other SQL services also), so the doman user has needed
privileges in domain and in member server files.
In the second DC, I installed SQ Server prior to promote it to DC. In this
server, if I use domain administrator account to start SQL Server, it starts
without problem. But I want to make it start with same domain account the
other SQL Server starts. So I try to assign the service account using SQL
Configuration Manager and error 0x80070534 "No mapping between account names
and security IDs was done" appears.
Any help will be geatly appreaciated.
Thank you
AlexYou can get the error when the account can't be mapped to
the correct SID - did you try another account? With the DC
issue, you may also want to try without the domain prefix -
along the lines of ServiceAcctName (instead of
Domain\ServiceAcctName)
-Sue
On Tue, 13 Feb 2007 15:35:01 -0800, Alex Luna
<AlexLuna@.discussions.microsoft.com> wrote:

>Hi people
>I'm trying to change the SQL Server service account to a domain account and
>got error 0x80070534. I explain a little...
>I have three servers, a DC, another DC with SQL Server installed and a
>member server with SQL Server installed.
>In the member server I wasable to successfully change the SQL Server servic
e
>account (and for other SQL services also), so the doman user has needed
>privileges in domain and in member server files.
>In the second DC, I installed SQ Server prior to promote it to DC. In this
>server, if I use domain administrator account to start SQL Server, it start
s
>without problem. But I want to make it start with same domain account the
>other SQL Server starts. So I try to assign the service account using SQL
>Configuration Manager and error 0x80070534 "No mapping between account name
s
>and security IDs was done" appears.
>Any help will be geatly appreaciated.
>Thank you
>Alex|||Hello Sue,
Thank you or your help. If I try using the account name without domain name
prefix, an error 0x80070056 "The specified network password is not correct."
shows up.
I also tried to use another domain account as service account and error
0x80070534 appears. I added the desired service account to domain admin grou
p
and still got the same error. So, only with admin user account I'm able to
start SQL Server.
Any suggestions?
Alex
"Sue Hoegemeier" wrote:

> You can get the error when the account can't be mapped to
> the correct SID - did you try another account? With the DC
> issue, you may also want to try without the domain prefix -
> along the lines of ServiceAcctName (instead of
> Domain\ServiceAcctName)
> -Sue
> On Tue, 13 Feb 2007 15:35:01 -0800, Alex Luna
> <AlexLuna@.discussions.microsoft.com> wrote:
>
>|||When you create a new account, make sure to set the correct
settings for the service account. Then add the account to
the sysadmins server role in SQL Server. Then change the
service account using the Configuration Manager.
-Sue
On Wed, 14 Feb 2007 06:19:03 -0800, Alex Luna
<AlexLuna@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hello Sue,
>Thank you or your help. If I try using the account name without domain name
>prefix, an error 0x80070056 "The specified network password is not correct.
"
>shows up.
>I also tried to use another domain account as service account and error
>0x80070534 appears. I added the desired service account to domain admin gro
up
>and still got the same error. So, only with admin user account I'm able to
>start SQL Server.
>Any suggestions?
>Alex
>"Sue Hoegemeier" wrote:
>|||Thank you Sue, but still got the same error at Configuration Manager.
The account has granted Logon as Service right in the domain and in Domain
Controllers. I had set the same permissions for that account in both SQL
Server. The only difference I see is that the SQL Server where the account i
s
able to start the service is not a domain controller, and the other SQL
Server it is.
-Alex
"Sue Hoegemeier" wrote:

> When you create a new account, make sure to set the correct
> settings for the service account. Then add the account to
> the sysadmins server role in SQL Server. Then change the
> service account using the Configuration Manager.
> -Sue
> On Wed, 14 Feb 2007 06:19:03 -0800, Alex Luna
> <AlexLuna@.discussions.microsoft.com> wrote:
>
>|||Which same error? One error you are getting due to running
SQL Server on a domain controller is using the domain
prefix. When you removed the prefix, the error was:
"The specified network password is not correct."
Which means the password you used for the account was
incorrect.
-Sue
On Thu, 22 Feb 2007 13:02:47 -0800, Alex Luna
<AlexLuna@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thank you Sue, but still got the same error at Configuration Manager.
>The account has granted Logon as Service right in the domain and in Domain
>Controllers. I had set the same permissions for that account in both SQL
>Server. The only difference I see is that the SQL Server where the account
is
>able to start the service is not a domain controller, and the other SQL
>Server it is.
>-Alex
>"Sue Hoegemeier" wrote:
>|||Sue
If I use the prefix, I got error 0x80070534, if I don't use the prefix I got
the error 0x80070056, incorrect network password, but I'm sure the password
is correct. Something similar happens when I use RUN AS command (or screen)
on the DC, if I type the user with domain prefix, it starts the app as that
user (the same I want SQL services start with), but if I don't use the prefi
x
at RUN AS window or command, the password error appears. Maybe, I have a
misconfiguration at domain level...?
Thank you for your help
-Alex
"Sue Hoegemeier" wrote:
[vbcol=seagreen]
> Which same error? One error you are getting due to running
> SQL Server on a domain controller is using the domain
> prefix. When you removed the prefix, the error was:
> "The specified network password is not correct."
> Which means the password you used for the account was
> incorrect.
> -Sue
> On Thu, 22 Feb 2007 13:02:47 -0800, Alex Luna
> <AlexLuna@.discussions.microsoft.com> wrote:
>|||Hi Alex,
Managing this on a domain controller can be a pain. The
permissions don't always get set correctly due to security
issues - it's a different risk when you install SQL Server
on a domain controller.
You'll need to start by walking through all the permissions
for the service account. The following link is probably the
best resource on this:
http://support.microsoft.com/?id=283811
-Sue
On Mon, 26 Feb 2007 08:11:08 -0800, Alex Luna
<AlexLuna@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue
>If I use the prefix, I got error 0x80070534, if I don't use the prefix I go
t
>the error 0x80070056, incorrect network password, but I'm sure the password
>is correct. Something similar happens when I use RUN AS command (or screen)
>on the DC, if I type the user with domain prefix, it starts the app as that
>user (the same I want SQL services start with), but if I don't use the pref
ix
>at RUN AS window or command, the password error appears. Maybe, I have a
>misconfiguration at domain level...?
>Thank you for your help
>-Alex
>"Sue Hoegemeier" wrote:
>

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitI
n\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while startin
g
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
>|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft.com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft.com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator grou
p
and then added this user to serverAdmin/Sysadmin group in SQL Server. I stil
l
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

Error "Logon failed" - SSRS Service user account rights

I am facing a problem which is based on the restrictions on the domain of the customer. After deplyoing the report on the server we are getting the following error message in the report manager after executing (clicking) a report link:

Logon failed.

Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)

I googled for that and it seems to be an authentication issue where some user / account is not granted to log on as service / locally, but the problems is better described than the solutions. Did anyone faced that problem so far ? Which account has to be granted what priviledges or permissions in Windows. We are using a SQL Server 2005 / Reporting Services 2005 running on the same machine whereas the virtual directories Reports and Reportserver are running in a separate Application Pool

Thanks,

Thomas

I 've exactly the same issue.

I thought that it's a delegation problem, because we work on different machines for SSRS and SSAS.

But it really looks like having a problem with the windows authenitcation on the SSAS server.

Error "Logon failed" - SSRS Service user account rights

I am facing a problem which is based on the restrictions on the domain of the customer. After deplyoing the report on the server we are getting the following error message in the report manager after executing (clicking) a report link:

Logon failed.

Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)

I googled for that and it seems to be an authentication issue where some user / account is not granted to log on as service / locally, but the problems is better described than the solutions. Did anyone faced that problem so far ? Which account has to be granted what priviledges or permissions in Windows. We are using a SQL Server 2005 / Reporting Services 2005 running on the same machine whereas the virtual directories Reports and Reportserver are running in a separate Application Pool

Thanks,

Thomas

I 've exactly the same issue.

I thought that it's a delegation problem, because we work on different machines for SSRS and SSAS.

But it really looks like having a problem with the windows authenitcation on the SSAS server.

error - Cannot create a connection to data source

Hello.
I have installed reporting Services on a serevr and have a MS SQL DB on a
different server.I am using a domain id to coneect to db server which have
required access on database.Both the server are in same domain.
also I have configured a seperate application pool in IIS for
/reportmanager which is runnig under same domain ID which i used for
reporting service .
I have created a connection which is shared by all reports.
Now problem is while browsing report i am getting error -
"Cannot create a connection to data source 'dbSPSReportingSample'.
(rsErrorOpeningConnection)
SQL Server does not exist or access denied."
I am able to test connectivity to Db server using ODBC connection manager
succesfully.
Error in logfile says --
w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
'dbSPSReportingSample': An error has occurred. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dbSPSReportingSample'. -->
System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied.
Please advice
Thanks
.When you deploy the data source the credentials do not get deployed and you
need to go to Report Manager and view the data source and set the
credentials. Have it be securely stored.
Also, I would strongly consider using a non-domain account if you can. If
you are able to have the Database server run in mixed mode then create an
SQL Server account just used for reporting. Then you can set stored
procedures to allow execute for this account. I put the account in a read
only role on the server. This keeps things clean. Plus, at my company, all
domain user ids are enforced to have the password changed every 90 days
which would be a real pain for this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Amit" <Amit@.discussions.microsoft.com> wrote in message
news:3E53F4DC-667D-40EA-B3F9-600D69917D1F@.microsoft.com...
> Hello.
> I have installed reporting Services on a serevr and have a MS SQL DB on a
> different server.I am using a domain id to coneect to db server which have
> required access on database.Both the server are in same domain.
> also I have configured a seperate application pool in IIS for
> /reportmanager which is runnig under same domain ID which i used for
> reporting service .
> I have created a connection which is shared by all reports.
> Now problem is while browsing report i am getting error -
> "Cannot create a connection to data source 'dbSPSReportingSample'.
> (rsErrorOpeningConnection)
> SQL Server does not exist or access denied."
> I am able to test connectivity to Db server using ODBC connection manager
> succesfully.
> Error in logfile says --
> w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> 'dbSPSReportingSample': An error has occurred. Details:
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> Cannot create a connection to data source 'dbSPSReportingSample'. -->
> System.Data.SqlClient.SqlException: SQL Server does not exist or access
> denied.
> Please advice
> Thanks
> .|||Hello Bruce,
Thanks for your response.
1.The domain ID which i am using are service account and are set for "
Password never expire option."
2. In the shared connection i am using "credentials stored secuely in report
server"
Still getting the same error. is the error message in sql reporting log file
gives any hint where I am missing ?
" Error in logfile says --
w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
'dbSPSReportingSample': An error has occurred. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'dbSPSReportingSample'. -->
System.Data.SqlClient.SqlException: SQL Server does not exist or access
denied.
"
Thanks Again
Amit
"Bruce L-C [MVP]" wrote:
> When you deploy the data source the credentials do not get deployed and you
> need to go to Report Manager and view the data source and set the
> credentials. Have it be securely stored.
> Also, I would strongly consider using a non-domain account if you can. If
> you are able to have the Database server run in mixed mode then create an
> SQL Server account just used for reporting. Then you can set stored
> procedures to allow execute for this account. I put the account in a read
> only role on the server. This keeps things clean. Plus, at my company, all
> domain user ids are enforced to have the password changed every 90 days
> which would be a real pain for this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Amit" <Amit@.discussions.microsoft.com> wrote in message
> news:3E53F4DC-667D-40EA-B3F9-600D69917D1F@.microsoft.com...
> > Hello.
> > I have installed reporting Services on a serevr and have a MS SQL DB on a
> > different server.I am using a domain id to coneect to db server which have
> > required access on database.Both the server are in same domain.
> >
> > also I have configured a seperate application pool in IIS for
> > /reportmanager which is runnig under same domain ID which i used for
> > reporting service .
> >
> > I have created a connection which is shared by all reports.
> > Now problem is while browsing report i am getting error -
> >
> > "Cannot create a connection to data source 'dbSPSReportingSample'.
> > (rsErrorOpeningConnection)
> > SQL Server does not exist or access denied."
> >
> > I am able to test connectivity to Db server using ODBC connection manager
> > succesfully.
> >
> > Error in logfile says --
> > w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> > 'dbSPSReportingSample': An error has occurred. Details:
> > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Cannot create a connection to data source 'dbSPSReportingSample'. -->
> > System.Data.SqlClient.SqlException: SQL Server does not exist or access
> > denied.
> >
> > Please advice
> > Thanks
> > .
>
>|||Hi Amit
Go to the report manager interface and make sure that your data source
has the right credential information, after you deploy. When you say
that RS is on one server and SQL is on another server , do you mean
that there is one web server and one data base server ? In which case
I am guessing that the RS db would be on the second server as well.
This may create a double hop issue in the network where the first hop
will be from the web server to the RS database and the second hop
would be to your stored proc. You will need kerberos enabled on the
network. If you do then check the event viewer on the sql server box
to see whether the right kerberos ticket is getting through from the
web server to the database server .
Cheers
Shai
On Nov 30, 3:13 pm, Amit <A...@.discussions.microsoft.com> wrote:
> Hello Bruce,
> Thanks for your response.
> 1.The domain ID which i am using are service account and are set for "
> Password never expire option."
> 2. In the shared connection i am using "credentials stored secuely in report
> server"
> Still getting the same error. is the error message in sql reporting log file
> gives any hint where I am missing ?
> " Error in logfile says --
> w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> 'dbSPSReportingSample': An error has occurred. Details:
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> Cannot create a connection to data source 'dbSPSReportingSample'. -->
> System.Data.SqlClient.SqlException: SQL Server does not exist or access
> denied.
> "
> Thanks Again
> Amit
> "Bruce L-C [MVP]" wrote:
>
> > When you deploy the data source the credentials do not get deployed and you
> > need to go to Report Manager and view the data source and set the
> > credentials. Have it be securely stored.
> > Also, I would strongly consider using a non-domain account if you can. If
> > you are able to have the Database server run in mixed mode then create an
> > SQL Server account just used for reporting. Then you can set stored
> > procedures to allow execute for this account. I put the account in a read
> > only role on the server. This keeps things clean. Plus, at my company, all
> > domain user ids are enforced to have the password changed every 90 days
> > which would be a real pain for this.
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> > "Amit" <A...@.discussions.microsoft.com> wrote in message
> >news:3E53F4DC-667D-40EA-B3F9-600D69917D1F@.microsoft.com...
> > > Hello.
> > > I have installed reporting Services on a serevr and have a MS SQL DB on a
> > > different server.I am using a domain id to coneect to db server which have
> > > required access on database.Both the server are in same domain.
> > > also I have configured a seperate application pool in IIS for
> > > /reportmanager which is runnig under same domain ID which i used for
> > > reporting service .
> > > I have created a connection which is shared by all reports.
> > > Now problem is while browsing report i am getting error -
> > > "Cannot create a connection to data source 'dbSPSReportingSample'.
> > > (rsErrorOpeningConnection)
> > > SQL Server does not exist or access denied."
> > > I am able to test connectivity to Db server using ODBC connection manager
> > > succesfully.
> > > Error in logfile says --
> > > w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> > > 'dbSPSReportingSample': An error has occurred. Details:
> > > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > > Cannot create a connection to data source 'dbSPSReportingSample'. -->
> > > System.Data.SqlClient.SqlException: SQL Server does not exist or access
> > > denied.
> > > Please advice
> > > Thanks
> > > .- Hide quoted text -
> - Show quoted text -|||Hello Shai,
Yes I have 2 server
Server A (windows 2003) have IIS6 and SPS 2003 and reporting services
installd.
ServerB have SQL serevr and have DB for reporting services.
Both the server are in same domain.
I am giving right credentials in data source connection.
The reports i am using are SPS reports which i got after installing SPS pack
for SQL reporting server.
Thanks
Amit
"shaikat.das@.gmail.com" wrote:
> Hi Amit
> Go to the report manager interface and make sure that your data source
> has the right credential information, after you deploy. When you say
> that RS is on one server and SQL is on another server , do you mean
> that there is one web server and one data base server ? In which case
> I am guessing that the RS db would be on the second server as well.
> This may create a double hop issue in the network where the first hop
> will be from the web server to the RS database and the second hop
> would be to your stored proc. You will need kerberos enabled on the
> network. If you do then check the event viewer on the sql server box
> to see whether the right kerberos ticket is getting through from the
> web server to the database server .
> Cheers
> Shai
>
> On Nov 30, 3:13 pm, Amit <A...@.discussions.microsoft.com> wrote:
> > Hello Bruce,
> >
> > Thanks for your response.
> > 1.The domain ID which i am using are service account and are set for "
> > Password never expire option."
> >
> > 2. In the shared connection i am using "credentials stored secuely in report
> > server"
> >
> > Still getting the same error. is the error message in sql reporting log file
> > gives any hint where I am missing ?
> > " Error in logfile says --
> > w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> > 'dbSPSReportingSample': An error has occurred. Details:
> > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Cannot create a connection to data source 'dbSPSReportingSample'. -->
> > System.Data.SqlClient.SqlException: SQL Server does not exist or access
> > denied.
> > "
> >
> > Thanks Again
> > Amit
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >
> >
> > > When you deploy the data source the credentials do not get deployed and you
> > > need to go to Report Manager and view the data source and set the
> > > credentials. Have it be securely stored.
> >
> > > Also, I would strongly consider using a non-domain account if you can. If
> > > you are able to have the Database server run in mixed mode then create an
> > > SQL Server account just used for reporting. Then you can set stored
> > > procedures to allow execute for this account. I put the account in a read
> > > only role on the server. This keeps things clean. Plus, at my company, all
> > > domain user ids are enforced to have the password changed every 90 days
> > > which would be a real pain for this.
> >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> >
> > > "Amit" <A...@.discussions.microsoft.com> wrote in message
> > >news:3E53F4DC-667D-40EA-B3F9-600D69917D1F@.microsoft.com...
> > > > Hello.
> > > > I have installed reporting Services on a serevr and have a MS SQL DB on a
> > > > different server.I am using a domain id to coneect to db server which have
> > > > required access on database.Both the server are in same domain.
> >
> > > > also I have configured a seperate application pool in IIS for
> > > > /reportmanager which is runnig under same domain ID which i used for
> > > > reporting service .
> >
> > > > I have created a connection which is shared by all reports.
> > > > Now problem is while browsing report i am getting error -
> >
> > > > "Cannot create a connection to data source 'dbSPSReportingSample'.
> > > > (rsErrorOpeningConnection)
> > > > SQL Server does not exist or access denied."
> >
> > > > I am able to test connectivity to Db server using ODBC connection manager
> > > > succesfully.
> >
> > > > Error in logfile says --
> > > > w3wp!processing!16a4!29/11/2007-14:43:59:: e ERROR: Data source
> > > > 'dbSPSReportingSample': An error has occurred. Details:
> > > > Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > > > Cannot create a connection to data source 'dbSPSReportingSample'. -->
> > > > System.Data.SqlClient.SqlException: SQL Server does not exist or access
> > > > denied.
> >
> > > > Please advice
> > > > Thanks
> > > > .- Hide quoted text -
> >
> > - Show quoted text -
>|||As I wrote earlier, you will need to enable kerberos on the network .
Cheers
Shai