Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Damien <Damien_The_Unbeliever@xxxxxxxxxxx>
- Date: Thu, 20 Mar 2008 04:57:36 -0700 (PDT)
On Mar 20, 12:06 am, Benzine <bfau...@xxxxxxxxx> wrote:
On Mar 20, 1:18 am, Tom van Stiphout <no.spam.tom7...@xxxxxxx> wrote:
On Wed, 19 Mar 2008 04:45:50 -0700 (PDT), Benzine <bfau...@xxxxxxxxx>
wrote:
Probably a bad connection string. "Integrated Security=SSPI" means
that it uses Windows Authentication rather than SQL Server
Authentication. For that to work the user of the IIS process would
have to have access to the db, and it most likely does not.
Create a new user (e.g. MyWebAppUser), give it access to the database,
and put this username/password in the connection string, and take the
Integrated Security out.
Details of the connection string:www.connectionstrings.com
-Tom.
This is the connection string on line 8
Conn.Open "Provider=sqloledb;Data Source=SUS-DB01;Initial
Catalog=iCom;Integrated Security=SSPI;"
On Mar 19, 3:13 pm, Tom van Stiphout <no.spam.tom7...@xxxxxxx> wrote:
On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@xxxxxxxxx>
wrote:
What's the content of this line:
/CMS/include/conniCom.inc, line 8
Linked servers don't come into play here, because there is only one
SqlServer: ServerB.
-Tom.
I am getting the below error message from my asp application:
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.
/CMS/include/conniCom.inc, line 8
Details:
SQL Server 2005
ASP Script
IIS 6.0
I have seen posts about this error many times but in this case it is a
little different.
The error is not related to SQL Mixed Mode authentication not being
setup on the server as this has been done, nor is it to do with
Integrated Windows Security on the IIS server as this has been done
aswell.
Its a little different because my application is hosted on Server A
(IIS Server) and is trying to connect to Server B (SQL Server).
I have tried adding a linked server to Server A from Server B but I
still get the same error.
Can anyone give me some insight on what needs to be done here.
Regards,
Ben- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
This is not an option as the Windows user is used to log changes made
to the asp application.
Just a bit of other information the application I have built is
running on a companies intranet site thus all users are setup to
access the db.
Also the error message has only appeared due to the change of
enviornment, orignally the IIS and SQL server were running on the same
box. Now that the sql server has been moved to a separate box I am
getting this error. (Note: The 2 servers are still under the same
domain)
Ben
http://groups.google.com/group/microsoft.public.sqlserver.connect/browse_frm/thread/bdeef084725c34d4/e8e73517ca3f3c9e?lnk=st&q=double+hop+damien#e8e73517ca3f3c9e
Not that I'm lazy :-)
Damien
.
- References:
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Benzine
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Tom van Stiphout
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Benzine
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Tom van Stiphout
- Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- From: Benzine
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Prev by Date: Re: job died but why?
- Next by Date: Inserting nothing takes a long time
- Previous by thread: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Next by thread: Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Index(es):
Relevant Pages
|
