|
Home > Archive > Microsoft SQL Server Desktop Engine > April 2005 > SQL Trust issue
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Microsoft News Group 2005-04-15, 8:23 pm |
| 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
| |
|
| One thing to try when you have a login error is to go to (MYComputer -
Manage - Services and Applications - Services) the services and check to see
what the login id is for that particular instance or if the primary
instance, that too. Sometimes the account gets confused on the SP2 install.
I can't tell you why, but I know when I installed the SP2, I had to make an
adjustment.
Right click - Slect Properties - Log On. Should say the Local System
account. (Provided that the local system account is an administrator).
There is also a registry setting you shouldn't need to mess with but if it
still doesn't work, check HKCU\SOFTWARE\Micros
oft\Microsoft SQL
Server\[instance name]\MSSQLServer and the value to change is LoginMode and
the value you want is 1 for integrated security or (0) 2 for integrated
security (which I assume you do not want since you are getting a trusted
server denial).
Jamie
"Microsoft News Group" <sekoon@excite.com> wrote in message
news:u52GNifQFHA.3336@TK2MSFTNGP10.phx.gbl...
>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
>
>
| |
|
| Correction... 2 or 0 for Mixed Mode. You want integrated which is 1.
Jamie
"jamie" <anonymous@nospam.somewhere.com> wrote in message
news:O8jhXdgQFHA.2520@tk2msftngp13.phx.gbl...
> One thing to try when you have a login error is to go to (MYComputer -
> Manage - Services and Applications - Services) the services and check to
> see what the login id is for that particular instance or if the primary
> instance, that too. Sometimes the account gets confused on the SP2
> install. I can't tell you why, but I know when I installed the SP2, I had
> to make an adjustment.
>
> Right click - Slect Properties - Log On. Should say the Local System
> account. (Provided that the local system account is an administrator).
> There is also a registry setting you shouldn't need to mess with but if it
> still doesn't work, check HKCU\SOFTWARE\Micros
oft\Microsoft SQL
> Server\[instance name]\MSSQLServer and the value to change is LoginMode
> and the value you want is 1 for integrated security or (0) 2 for
> integrated security (which I assume you do not want since you are getting
> a trusted server denial).
>
> Jamie
>
> "Microsoft News Group" <sekoon@excite.com> wrote in message
> news:u52GNifQFHA.3336@TK2MSFTNGP10.phx.gbl...
>
>
| |
| Microsoft News Group 2005-04-16, 3:23 am |
| I have tried your suggestions, The logged on user accout is the same as the
SQL instante log account. And the LoginMode is set correctly. This is
driving me crazy in that I can uninstall the SP2 and things start working
again, yet re-apply the SP2 and it break my SQL trust.
Steve
"jamie" <anonymous@nospam.somewhere.com> wrote in message
news:O8jhXdgQFHA.2520@tk2msftngp13.phx.gbl...
> One thing to try when you have a login error is to go to (MYComputer -
> Manage - Services and Applications - Services) the services and check to
> see what the login id is for that particular instance or if the primary
> instance, that too. Sometimes the account gets confused on the SP2
> install. I can't tell you why, but I know when I installed the SP2, I had
> to make an adjustment.
>
> Right click - Slect Properties - Log On. Should say the Local System
> account. (Provided that the local system account is an administrator).
> There is also a registry setting you shouldn't need to mess with but if it
> still doesn't work, check HKCU\SOFTWARE\Micros
oft\Microsoft SQL
> Server\[instance name]\MSSQLServer and the value to change is LoginMode
> and the value you want is 1 for integrated security or (0) 2 for
> integrated security (which I assume you do not want since you are getting
> a trusted server denial).
>
> Jamie
>
> "Microsoft News Group" <sekoon@excite.com> wrote in message
> news:u52GNifQFHA.3336@TK2MSFTNGP10.phx.gbl...
>
>
| |
|
| http://support.microsoft.com/?kbid=841249
Is my immediate thought... firewall, but it may not be the issue. Here is
the Microsoft troubleshooting site for SP2 and MSDE (SQL Server)
http://www.microsoft.com/sql/techin...winxpsp2faq.asp
"Microsoft News Group" <sekoon@excite.com> wrote in message
news:ej$q0wlQFHA.356@TK2MSFTNGP14.phx.gbl...
>I have tried your suggestions, The logged on user accout is the same as the
>SQL instante log account. And the LoginMode is set correctly. This is
>driving me crazy in that I can uninstall the SP2 and things start working
>again, yet re-apply the SP2 and it break my SQL trust.
>
> Steve
>
>
> "jamie" <anonymous@nospam.somewhere.com> wrote in message
> news:O8jhXdgQFHA.2520@tk2msftngp13.phx.gbl...
>
>
| |
| Andrea Montanari 2005-04-16, 7:23 am |
| hi Steve,
Microsoft News Group wrote:
> I have tried your suggestions, The logged on user accout is the same
> as the SQL instante log account. And the LoginMode is set correctly.
> This is driving me crazy in that I can uninstall the SP2 and things
> start working again, yet re-apply the SP2 and it break my SQL trust.
>
> Steve
please excuse my poor english, but I do not understand... did you solve your
problems with Jamie's hints?
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--------- remove DMO to reply
| |
| Microsoft News Group 2005-04-16, 8:23 pm |
| No the problem has not been resolved yet and I have the firewall turn
completely off at the moment since the computer is not connect to the
internet at the moment for testing.
Steve
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:3ccdhlF6l87vnU1
@individual.net...
> hi Steve,
> Microsoft News Group wrote:
>
> please excuse my poor english, but I do not understand... did you solve
> your problems with Jamie's hints?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
| |
| Steve Koon 2005-04-20, 1:23 pm |
| 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@excite.com> wrote in message
news:u52GNifQFHA.3336@TK2MSFTNGP10.phx.gbl...
>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
>
>
| |
|
|
Steve
I was fooling around yesterday, uninstalling my MSDE copy. I noted a few
surprises.
The network I am on prevented one installation from going through
completely. The SQL Agent from the company server was blocking the
installation. This was temporary only however. Once I rebooted, and went
through the routine of removing the Instance KEY from the registry and
removing any folders installed as part of that instance installation and
finally, reinstalling, the Agent message went away and the installation
proceeded fine. If I had expected it, I would have paid more attention and
gotten more specifics. I did keep my logs however.
The second thing I noted was that the log file that is generated when the
installation fails appears to have a special character - I'll need to check
again, I am not at work - but I would assume it is a carriage return. I
mention this is because those setup logs for (begin with msi*.log and match
the time of installation - generally in the temp folder of the local
settings) MSDE can be very lengthy and thus it become hard to pinpoint
exactly where the installation went south.
I have been attempting to add a project to my setup routine that auto
installs the MSDE when it is missing precisely because I can't imagine
walking a user through the kind of issues you are having now, and you are an
experience computer user and understand the intricacy of the MSDE.
There are a number of issues listed on the link I sent you regarding the SP2
for XP. I initially had my problems with XP SP2 and MSDE while the service
pack was still in beta, and I had to rollback to sp1 to fix things. Later
when I upgrades to SP2, the issues never surfaced, but at that time, I
already had the MSDE installed. Perhaps the way to approach this is to
rollback to sp1, install MSDE, and then reinstall sp2?
Hope this helps.
Jamie
"Microsoft News Group" <sekoon@excite.com> wrote in message
news:u%23skbUrQFHA.2384@tk2msftngp13.phx.gbl...
> No the problem has not been resolved yet and I have the firewall turn
> completely off at the moment since the computer is not connect to the
> internet at the moment for testing.
>
> Steve
>
>
> "Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
> news:3ccdhlF6l87vnU1
@individual.net...
>
>
| |
|
| 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]
Disablenetworkprotoc
ols=1
InstanceName=MyOwnNa
meWhatever
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/d...istsql_84xl.asp
Here is a link for a workaround data directory that may also be useful.
http://support.microsoft.com/defaul...499&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@video-mation.com> wrote in message
news:%234EKEZdRFHA.2132@TK2MSFTNGP14.phx.gbl...
>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@excite.com> wrote in message
> news:u52GNifQFHA.3336@TK2MSFTNGP10.phx.gbl...
>
>
|
|
|
|
|