Re: SQL Trust issue
- From: "jamie" <anonymous@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 23 Apr 2005 08:26:43 -0400
Steve,
What is the exact error that you are getting?
Understand that when you deal with trust you'll find there are both registry
items that regulate this as well as the actual account you use to open the
database. I am sure you are familiar with the installation setting - for
example, I always apply the settings from the setup.ini and it generally
looks like this:
[Options]
Disablenetworkprotocols=1
InstanceName=MyOwnNameWhatever
Sapwd=Kermit
Securitymode=SQL
UID=sa
This generally allows the installation to proceed smoothly. Once done,
because I need to avoid issues of trust, I use the application I am
distributing to tweak the LoginMode value in the MSSQLServer Key (its own
key if a default instance and a subkey of the instance name if using a named
instance). I want this value to be 1 because I don't want my users machine
to be hacked just because they appear on a public network somewhere. The
value of 1 changes the SecurityMode to use NT trust instead of MixedMode. I
also disable the network protocols for the same reason. If you read,
you'll see that SecurityMode=SQL does the opposite, but I have found this is
a better setting to use during the installation. You may want to try the
above in your setup.ini file before running the MSDE installation. Also,
remember to substitute your instance name and your password, because if you
do go to mixed mode and you haven't changed these, then I know how to break
into your Instance as soon as you set the TCP/IP and namedpipes protocols
into the on state.
Information for the above settings are here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
Here is a link for a workaround data directory that may also be useful.
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
I hope this helps you to understand a little more thoroughly how this
installation works and why you are having difficulties. I can never make
heads nor tails of the logs, but I read them anyway because it gives me a
chance to cool off a little when things don't go the way I expect them to.
Here are some error messages to help you.
Not installed - you get a message about shared space - something similar,
maybe someone can help me out here.
Installed but not started. SQL DMO message - does not tell you that the
machine has not been started, but the DMO is a big clue. Type in Net Start
MSSQL$ImynstanceName to start the instance.
Connection could not be established - either you are trying to reach a
server and you are not on the network (SQL Server) or MSDE - locally you are
logged in under an account without trust, and or you have tried to login to
the server under an account that doesn't have permission to use the server.
If so, go to MyComputer, Manage, Service Applications, Services and right
click the instance and set the logon (second tab) to use the local account
system.
Login failed for user 'sa': Not associated with a trusted account. Similar
to above, either you are running the server in Mixed Mode - set it using the
Manage account above or tweak the registry setting so that you are in Trust
mode. If you still can't get in, it is because you are not going in using
the local system account and/or the Security Mode is not set for Mixed mode
and the only way you can get in is to be member of the login security for
that server - therefore, in Trust mode, without a system account login, you
also are not in the list of logins listed for that machine.
There is a long list of the above errors because each situation requires its
own parameters. I haven't explored clustered SQL Servers, so I am sure
there are many more of this type of error, so I would advise that you look
at your situation to see if there aren't other complications that exist
(such as a network) and that you are trying to keep things simple (use the
setup.ini I have provided for the installation and run the tweaks later).
Jamie
"Steve Koon" <skoon@xxxxxxxxxxxxxxxx> wrote in message
news:%234EKEZdRFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
>I read online that this issue may have to do with service pack 2 being
>install on my XP Pro computer and that I needed to update my SQL service
>pack to level 3a which I have done and this still did not fix the trust
>issue.
>
> Steve
>
>
> "Microsoft News Group" <sekoon@xxxxxxxxxx> wrote in message
> news:u52GNifQFHA.3336@xxxxxxxxxxxxxxxxxxxxxxx
>>I have an application running on my desktop that access the SQL database
>>and as long as I am not running XP SP2 things run fine. As soon as I
>>install XP SP2 then I keeping getting this message "Database Error: Login
>>failed for the user. Reason:Not associated with a trusted SQL Server
>>connection". I have tried everything and change not get this problem
>>resolved, anyone have a clue as to where I should start looking at again
>>to get this fixed?
>>
>> Steve
>>
>>
>
>
.
- References:
- SQL Trust issue
- From: Microsoft News Group
- Re: SQL Trust issue
- From: Steve Koon
- SQL Trust issue
- Prev by Date: I could not set complete backup tag.
- Next by Date: Re: MSDE install faile (faile to configure server)
- Previous by thread: Re: SQL Trust issue
- Next by thread: Getting to the bottom of MSDE network connection problems ...
- Index(es):
Relevant Pages
|
