Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Login failed for user - when access SS from web service

172 views
Skip to first unread message

Dave

unread,
Feb 3, 2010, 5:42:45 PM2/3/10
to
I'm hitting the following error when my web service API tries to call
a SS PROC. It's working fine from another web service (production
service set up on another box) but i cannot get this web service set
up properly somehow. It's to serve as development / staging web
service and is thereby crucial to get working! I'm using the same
bits (web.config file...) for both web services so the connection
strings should be the same.

Hit exception when making Web Service call
System.Web.Services.Protocols.SoapException: Server was unable to
process request. ---> System.Data.SqlClient.SqlException: Login failed
for user 'DOMAIN\MACHINENAME$'.
at System.Data.ProviderBase.DbConnectionPool.GetConnection
(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.CreateObject
(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection
(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at ICISvcMain.WebSvcMain.GetChannels(Guid listnerId) in C:\src\Web
Service\SvcMain.asmx.cs:line 195
--- End of inner exception stack trace ---

Any ideas would be welcomed, thanks, dave

Erland Sommarskog

unread,
Feb 3, 2010, 6:03:15 PM2/3/10
to
Dave (djoha...@gmail.com) writes:
> I'm hitting the following error when my web service API tries to call
> a SS PROC. It's working fine from another web service (production
> service set up on another box) but i cannot get this web service set
> up properly somehow. It's to serve as development / staging web
> service and is thereby crucial to get working! I'm using the same
> bits (web.config file...) for both web services so the connection
> strings should be the same.
>
> Hit exception when making Web Service call
> System.Web.Services.Protocols.SoapException: Server was unable to
> process request. ---> System.Data.SqlClient.SqlException: Login failed
> for user 'DOMAIN\MACHINENAME$'.

Well, the error message is fairly clear to me. What is not clear to me is
why you disagree with it. Do you think DOMAIN\MACHINE$ should be able to
login, and in such case why? Or did you expect it to connect with a
different login?

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Dave

unread,
Feb 3, 2010, 6:10:55 PM2/3/10
to
On Feb 3, 3:03 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:

Yeah indeed i expected to login with my currently logged in user, but
instead of seeing domain\CurrentUser i saw domain\machine$. i have no
idea why. recall that if i switch the C# application to pointing to
the other web service (on a different machine) it works fine,
retrieving the data from SS no problem.

Dave

unread,
Feb 3, 2010, 6:31:59 PM2/3/10
to

oh digging further into the SS logs, i see the following:

2010-02-03 11:11:03.12 Logon Error: 18456, Severity: 14, State:
11.
2010-02-03 11:11:03.12 Logon Login failed for user 'DOMAIN
\MACHINE$'. Reason: Token-based server access validation failed with
an infrastructure error. Check for previous errors. [CLIENT:
10.10.0.74]

and this blog http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
indicates that state 11 is a "server access failure". not sure what
that means but still researching, hoping you have ideas...

Dave

unread,
Feb 3, 2010, 8:56:23 PM2/3/10
to
> and this bloghttp://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx

> indicates that state 11 is a "server access failure".  not sure what
> that means but still researching, hoping you have ideas...

I figured the issue out, the web service application pool (advanced)
settings were set as NetworkService, but I had neglected to add the
user / login for DOMAIN\MACHINENAME$ in SS (with appropriate access
levels).

Thanks, dave

0 new messages