|
| If the AD group is not configured properly for access on the SQL server then
you could get this problem. For instance, if the ad group has system
administrator access at root level, but not for individual databases.
"DC Gringo" wrote:
> Using latest SP Win2k and .NET versions, I have a .NET application running
> on server1 with a SQL Server database running on server2. I have the
> Windows user account passwords sync'd for server1\aspnet (installed by .NET
> Framework and server2\aspnet (created by me--this machine has no .NET
> Framework on it). The aspnet user on the database server (server2) has
> access to the database.
>
> I still get: Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection.
>
> IIS is set to Windows Integrated Authentication...although same result with
> Anonymous, with and without IIS controlling password that I enter.
>
> -----------------------------------
> Here's my connection string:
>
> Me.SqlConnection1.ConnectionString = "workstation id=""CIL-094"";packet
> size=4096;integrated security=SSPI;data source=""myserver"";persist security
> info=False;initial catalog=mydb;"
>
>
> -----------------------------------
> Here's my web.config:
>
> <?xml version="1.0" encoding="utf-8" ?>
> <configuration>
> <system.web>
>
> <compilation defaultLanguage="vb" debug="true" />
> <customErrors mode="Off" >
> <error statusCode="404" redirect="~/errors/missingPage.aspx" />
> </customErrors>
> <authentication mode="Windows" />
>
> <authorization>
> <allow users="*" /> </authorization>
>
> <trace enabled="true" requestLimit="10" pageOutput="true"
> traceMode="SortByTime" localOnly="true"/>
>
> <sessionState
> mode="InProc"
> stateConnectionString="tcpip=127.0.0.1:42424"
> sqlConnectionString="data source=127.0.0.1;"
> cookieless="false"
> timeout="20"
> />
>
> <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
> </system.web>
> </configuration>
>
> --
> _____
> DC G
>
>
>
|
|