The error 0x8009030c is SEC_E_LOGON_DENIED. I would guess
you enabled remote connections? I thought that was a
different error. Is the PC and the server in the same
domain? You can check the default trace around the time of
the login failure to find what login is actually failing. Is
that windows account setup as a login in SQL Server?
-Sue
On Wed, 22 Feb 2006 02:58:26 -0800, Andris
<Andris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi, im traying to connect to MSSQL 2005 server from Computer With Windows XP
Home with all patchs. Before I upgrade my sqlserver 7 to sql 2005 all works
fine. I can connect to server shares without problems. Application uses OLE
DB provider.
Error in SQL 2005 event viewer:
SSPI handshake failed with error code 0x8009030c while establishing a
connection with integrated security; the connection has been closed. [CLIENT:
10.10.10.111]
Re: Connection issues between .Net framwok and SQl Express 2005 ... You will no longer need the database MDF file name in the connection string.... simply attach the ASPNETDB.mdf to SQL Server permenantly,... as USER INSTANCE on existing SQL Server Express, ... (microsoft.public.dotnet.framework.aspnet)
Re: Performance of ODBC ... if you have a software firewall; forward 1433/1434 to your server... I've now created my own server with SQL Server 2005 Express, ... glitch concerns the Upsizing Wizard.... I originally set up my ODBC connection via ... (microsoft.public.access.adp.sqlserver)
RE: Getting Challenged when using SQL connection on .aspx page ... What would happen if i removed integrated security=sspi from the connection... Just want the login token to be passed, ... Have webpage with following connection in the ... I have account to the database on the SQL server.... (microsoft.public.dotnet.framework.aspnet)
Re: SQL User SID format? ... When you move databases to another server, you can remap users to logins ... capability to remap a user to a login with new ALTER USER syntax - I ... The new ALTER USER syntax works for remapping both SQL and Windows ... this means you already have access to a SID from the syslogins catalog; ... (microsoft.public.sqlserver.security)
SQL 2005 Express and VS .Net 2003 wizard error More options ... Open the server explorer panel... Go to the Provider tab and select SQL NAtive Client (DON'T use oledb ... Go back to the Connection tab and carry on setting up the connection ... I have installed Visual Studio 2005 Professional and then Visual Studio ... (microsoft.public.sqlserver)
