[AccessD] OT: MS SQL question

Hi All:

It worked after hard-coding the username and password directly into the
ASP.Net web.config file.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Monday, February 11, 2008 4:20 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] OT: MS SQL question

Hi Arthur and Robert:

Mixed mode is already set through the SQ Management Studio. Went through the
various services and changed them to "allow service to interact with
desktop" (Not sure what this will do or what it does.) A couple of the
service login settings were set to an account like
"AUTHORITY\NetworkService" and I did not change this as I am not sure of the
ramifications. 

Finally, I set the owner to the newly created database user and gave it
admin rights. That brute-force process seemed to initially work but....

The following error started coming up...
Login failed for user ''. The user is not associated with a trusted SQL
Server connection. 

...when working with ASP.Net.

I am not sure what should be adjusted next.

TIA
Jim 
  
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Sunday, February 10, 2008 7:08 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] OT: MS SQL question

Jim,

This (cribbed from my site artfulsoftware.com) may be of use:

Change authentication mode Change the Authentication mode on existing MSDE
Servers to 'mixed' (Windows Authentication and SQL Server) by modifying this
registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.x\MSSQLServer

If you are using SQL Server 2005, the above registry key stores the
authentication mode regardless of whether you installed a default instance
or a named instance. MSSQL.x is a placeholder for the corresponding value
for your system.

Set the value LoginMode to 2. This tells your server to accept SQL Server
AND Windows authentication methods.

Stop and restart the MSSQL service after making this change:

NET STOP MSSQLSERVER
NET START MSSQLSERVER

To accomplish the same for every server instance using the Windows GUI, log
in via Windows Authentication. If you can't log on via Windows Auth then
revise User Account privileges in Control Panel | User Accounts. Check to
see if you have Administrator Access on machine. If not, set it and continue
below.

1. Right click 'your server', choose 'properties'. Go to 'Security' and
select 'Mixed Mode'. Close SQL EMT.
2. In Start | Control Panel | Admin Tools | Services panel, scroll down to
view your SQL services and then one-at-a-time right click each and select
properties.
3. Click the 'Log On' tab and select 'Local System account' and 'Allow
service to interact..' check box (nothing else), then click 'OK'.
4. You should be back at the main Sevices panel. Using the cassette player
icons at the top of panel, simply stop, then start each SQL service (there's
a stop start button does both auto).
5. After restarting each, close window and try logging in using SQL Auth.
For the real beginners: username: sa pwd: leave blank.

hth,
Arthur

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com