Re: Problem with SQL Server 2005 Express Edition

Here are the instructions for changing it.
http://msdn2.microsoft.com/en-us/library/ms188670.aspx


--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Preben Zacho" <post@xxxxxxxxxxxx> wrote in message news:%23F%23hPh$lHHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
Hi Roger

How can I determine this? And how do I change it if that is the case?

/PZ

"Roger Wolter[MSFT]" <rwolter@xxxxxxxxxxxxxxxxxxxx> wrote in message news:1105D112-C515-42E4-924D-85184144DC2A@xxxxxxxxxxxxxxxx
Since you are specifying the user name and password in the connection string I assume you are using SQL Server authentication for your logins rather than Windows authentication. One cause for that error is trying to use a SQL Server login on a database server that is configured to only accept Windows logins.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Preben Zacho" <post@xxxxxxxxxxxx> wrote in message news:OKXT6f4lHHA.1776@xxxxxxxxxxxxxxxxxxxxxxx
Ok, I've read almost a million ng postings on this, still I can't solve it. This place is my final hope.

I'll start from the beginning: I have a Windows application developed in C#. It uses a SQL Server 2005 Express Edition database to store data. Now I have created a deployment of this app and database, and I try to install it on my own machine. No problems, works without errors.

Now, I put this deployment project on the network and a user downloads it to his Vista machine and runs the setup. When he starts the app he gets the following error message:

"Login failed for user "MyUser". The user is not associated with a thrusted
server connection".

The connection string I use in my application is this:

Server=.\SQLEXPRESS;Database=MyDB;User ID=MyUser;Password=thissucks

Since I have no control over the Vista machine, I can't force him/her to create a new account that is thrusted. All I want is to deploy my app and database, without having to worry about authorization and stuff. If possible, it should allow for ALL users to connect and use it.

I have already tried alot of the suggestions I've found, but lets start all over so it will be right. What should I do to remove this error? How can I deploy my database without having to think about authorization/security stuff?

TIA

PZ







.

Relevant Pages

  • Re: Help Ive been an idiot
    ... You need to make sure that you readd any logins that were mapped to database ... Jasper Smith (SQL Server MVP) ... > connectionString, CommandType commandType, String commandText, ...
    (microsoft.public.sqlserver.setup)
  • Re: Master database must never be the default database for any login
    ... let's say that I want TEMPDB as my default database for all logins ... Is it possible I configure SQL Server to set a default database other ... MASTER to any logins created automatically? ...
    (microsoft.public.sqlserver.security)
  • Re: Managing SQL database rights using AD
    ... logins to SQL Server. ... You would add these two logins you ... just added as users in the database. ... the Windows group that you just added as logins (and then ...
    (microsoft.public.sqlserver.security)
  • Re: How to move schedule jobs from one box to another during upgrade
    ... User information is stored in each database, so when you restore the databse ... possibility (for SQL logins which are NOT NT logins) is that the new SQL ... I support the Professional Association of SQL Server and it's community of SQL Server professionals. ...
    (microsoft.public.sqlserver.server)
  • Re: Resynching DB Users after Restore
    ... accidental security breach due to a cross-server restore. ... this semi-automagically, especially if you have a small, known set of logins ... Senior Database Administrator ... I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.security)