Hmm. That's a simple SEC_E_LOGON_DENIED. Simply meaning usedname/password is incorrect. The security eventlog on the server (or domain controller) might have more information around it. If not, I'm not sure what's wrong there - if it happens only in npgsql it must be related to that. Or perhaps - based on your reproduction - the .net app is running with a different user than you think? //Magnus On Mon, Nov 22, 2010 at 13:31, Reto Schöning <reto.schoening@xxxxxxxxx> wrote: > Here's the log output for a failed connection: > 2010-11-22 13:25:54 CET FATAL: could not accept SSPI security context > 2010-11-22 13:25:54 CET DETAIL: The logon attempt failed > (8009030c) > > 2010/11/22 Magnus Hagander <magnus@xxxxxxxxxxxx> >> >> Plase don't drop the mailinglist from the thread. >> >> >> On Mon, Nov 22, 2010 at 11:57, Reto Schöning <reto.schoening@xxxxxxxxx> >> wrote: >> > Thanks for the hint. The full error message from npgsql including that >> > detail row is >> > Npgsql.NpgsqlException was unhandled >> > Message="FATAL: XX000: could not accept SSPI security context" >> > Source="Npgsql" >> > ErrorCode=-2147467259 >> > BaseMessage="could not accept SSPI security context" >> > Code="XX000" >> > Detail="The logon attempt failed\r\n (8009030c)" >> > ErrorSql="" >> > File=".\\src\\backend\\libpq\\auth.c" >> > Hint="" >> > Line="648" >> > Position="" >> > Routine="pg_SSPI_error" >> > Severity="FATAL" >> > Where="" >> > StackTrace: >> > at >> > Npgsql.NpgsqlState.<ProcessBackendResponses_Ver_3>d__a.MoveNext() >> > in C:\projects\Npgsql2\src\Npgsql\NpgsqlState.cs:line 686 >> > at Npgsql.NpgsqlState.IterateThroughAllResponses(IEnumerable`1 >> > ienum) >> > in C:\projects\Npgsql2\src\Npgsql\NpgsqlState.cs:line 319 >> > at Npgsql.NpgsqlState.ProcessBackendResponses(NpgsqlConnector >> > context) in C:\projects\Npgsql2\src\Npgsql\NpgsqlState.cs:line 314 >> > at Npgsql.NpgsqlConnectedState.Startup(NpgsqlConnector context) >> > in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnectedState.cs:line 52 >> > at Npgsql.NpgsqlConnector.Open() in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnector.cs:line 656 >> > at Npgsql.NpgsqlConnectorPool.GetPooledConnector(NpgsqlConnection >> > Connection) in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnectorPool.cs:line >> > 423 >> > at >> > >> > Npgsql.NpgsqlConnectorPool.RequestPooledConnectorInternal(NpgsqlConnection >> > Connection) in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnectorPool.cs:line >> > 226 >> > at >> > Npgsql.NpgsqlConnectorPool.RequestPooledConnector(NpgsqlConnection >> > Connection) in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnectorPool.cs:line >> > 178 >> > at Npgsql.NpgsqlConnectorPool.RequestConnector(NpgsqlConnection >> > Connection) in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnectorPool.cs:line >> > 158 >> > at Npgsql.NpgsqlConnection.Open() in >> > C:\projects\Npgsql2\src\Npgsql\NpgsqlConnection.cs:line 543 >> > at NpgsqlTest.Program.Main(String[] args) in C:\Documents and >> > Settings\rsc\My Documents\Visual Studio >> > 2005\Projects\NpgsqlTest\NpgsqlTest\Program.cs:line 17 >> > I found a way to reproduce the same message in psql: when creating a >> > local >> > user with the same name as a domain user, the connection attempt when >> > logged >> > in as that user fails with the same message (rightly so, of course). >> > I've posted that in the npgsql forum also, no response yet. >> >> The details row you're looking for is in the *server* side log. >> >> -- >> Magnus Hagander >> Me: http://www.hagander.net/ >> Work: http://www.redpill-linpro.com/ > > -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
