Re: SQL open error

anonymous_at_discussions.microsoft.com
Date: 10/24/04


Date: Sun, 24 Oct 2004 15:03:23 -0700

I wish to use Windows authentication rather than supplying
a password like I used to using Integrated Security=SSPI in
my connection string. What do I need to do to get it to
accept that string? I am the systemes administrator on my
box and have no need for passwords. The name of my server
in Enterprise Manager reads as (LOCAL) (Windows NT).
However, it refers to the server as XP when I do the
install which is the name of my computer. Is that
appropriate? If I use Integrated Security=SSPI and Data
Source=localhost in my connection string I get the error
"SQL server does not exist or access denied". If I use
Data Source=XP I get the error "Login failed for user
'XP\\ASPNET'. What options need I take when re-installing
the SQL server in order to use Integrated Security=SSPI in
my connection string?
Dave
>-----Original Message-----
>You must use the user ID and password you used when you
reinstalled SQL
>Server. What user account id the MSSQLServer Windows
service running under?
>If not LocalSystem, perhaps that might help you (provided
you know the
>password of course ;-)).
>
>--
>Carsten Thomsen
>Enterprise Development with VS .NET, UML, and MSF
>http://www.apress.com/book/bookDisplay.html?bID=105
><anonymous@discussions.microsoft.com> wrote in message
>news:098e01c4b9f0$7d1d5360$a601280a@phx.gbl...
>> Carsten;
>> Thanks for your reply. I can access the SQL server
>> database thru the SQL Server Enterprise Manager. I don't
>> understand why the first connection string doesn't work in
>> my program. I tried to change the Server registration to
>> include SQL Server authentication in Enterprise Manager but
>> it keeps telling me that my user name is not associated
>> with a trusted SQL server connection, the same message I
>> get programmtically. How do I get my Windows ID to become
>> associated with a trusted SQL server connection?
>> Dave
>>>-----Original Message-----
>>>Have you checked that the user account used for running
>> your application can
>>>still access the SQL Server database? It seems that SQL
>> Server
>>>authentication is disabled and only Windows authentication
>> is enabled, which
>>>makes sense from a security perspective. However, that
>> means the second
>>>connection string you present, won't work.
>>>
>>>--
>>>Carsten Thomsen
>>>Enterprise Development with VS .NET, UML, and MSF
>>>http://www.apress.com/book/bookDisplay.html?bID=105
>>>"Dave" <anonymous@discussions.microsoft.com> wrote in
message
>>>news:083801c4b94a$badc8870$a501280a@phx.gbl...
>>>>I reinstalled SQL 2000 server after reformatting my drive.
>>>> Now I cannot open a database in my C## program as before.
>>>> If I use "Provider=SQLOLEDB;Data Source=localhost; Initial
>>>> Catalog=master;Integrated Security=SSPI"; I
>>>> get an Invalid login error. If I use "Provider=SQLOLEDB;
>>>> Data Source=localhost; Initial Catalog=master;User
>>>> ID=Dave;Password=midn1te"; I get the following error,
"User
>>>> no associated with a trusted SQL server connection." What
>>>> did I do wrong on my installation? Anyone know what these
>>>> errors mean? I sure can't find the answers in the Help.
>>>> Dave
>>>
>>>
>>>.
>>>
>
>
>.
>



Relevant Pages

  • Re: Why do I have to enable File and Printer sharing to connect through the XP firewall?
    ... the connection string. ... IS the client connecting using a Windows account or using a SQL Server account? ... the user is me and I'm a domain/olap admin. ...
    (microsoft.public.sqlserver.clients)
  • Re: Connecting using Windows Authentication
    ... You would use the following to authenticate using Windows NT integrated ... > Dirk - the connection string looks like this: ... > the SQL Server provider is expecting something to let it know how to log ...
    (microsoft.public.access.modulesdaovba)
  • Re: One Connection String for Multiple Users (SQL)
    ... Hitchhiker’s Guide to Visual Studio and SQL Server ... "William Vaughn" wrote: ... This uses the> same connection string for all instances of the application. ...
    (microsoft.public.sqlserver.connect)
  • Deployment issue - Error 26
    ... The target environment is a dedicated server running SQL Server 2005 Standard ... and client machines running the VS2005-developed code on Windows XP. ... testing looked OK after changing the connection string in the app config file. ... It built a connection string and stored it in the Project settings for the data ...
    (microsoft.public.dotnet.framework.adonet)
  • Connecting to SQLServer 2000 from ASP.NET
    ... I have an ASP.NET application that connects to a SQL Server database. ... Windows XP SP2 on development PCs which host the ASP.NET application. ... I managed to add MyDomain\AUser as a SQL user in Enterprise Manager. ... Computer: MachineName ...
    (microsoft.public.sqlserver.server)