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

On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfausti@gmail.com>
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

Benzine (bfausti@gmail.com) writes:
> 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
>...
>
> 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).

To start with, what is your connection string?

> I have tried adding a linked server to Server A from Server B but I
> still get the same error.

As Tom said, that has nothing to do with it.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

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:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
> 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 -

On Mar 19, 3:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
> 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 -

This is my connection string.

Conn.Open "Provider=sqloledb;Data Source=SUS-DB01;Initial
Catalog=iCom;Integrated Security=SSPI;"

Ben

On Wed, 19 Mar 2008 04:45:50 -0700 (PDT), Benzine <bfausti@gmail.com>
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:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
>> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
>> 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 -

Benzine (bfausti@gmail.com) writes:
> This is the connection string on line 8
>
> Conn.Open "Provider=sqloledb;Data Source=SUS-DB01;Initial
> Catalog=iCom;Integrated Security=SSPI;"

And the service account for IIS is?

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Mar 20, 1:18am, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> On Wed, 19 Mar 2008 04:45:50 -0700 (PDT), Benzine <bfau...@gmail.com>
> 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:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> >> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
> >> 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

On Wed, 19 Mar 2008 22:27:10 +0000 (UTC), Erland Sommarskog
<esquel@sommarskog.se> wrote:

IUSR_<machinename> for IIS5 (Win2000), and for IIS6 (Win2003) the
situation is a bit murkier. See this article:
http://www.microsoft.com/technet/pro....mspx?mfr=true

-Tom.


>Benzine (bfausti@gmail.com) writes:
>> This is the connection string on line 8
>>
>> Conn.Open "Provider=sqloledb;Data Source=SUS-DB01;Initial
>> Catalog=iCom;Integrated Security=SSPI;"
>
>And the service account for IIS is?

On Wed, 19 Mar 2008 17:06:04 -0700 (PDT), Benzine <bfausti@gmail.com>
wrote:

Seems like you left out a little tidbit of information that your
webapp is (most likely) running under Windows Authentication.
Sorry, I like the specs to be accurate the first time. Good day.

-Tom.


>On Mar 20, 1:18am, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
>> On Wed, 19 Mar 2008 04:45:50 -0700 (PDT), Benzine <bfau...@gmail.com>
>> 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:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
>> >> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
>> >> 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

Benzine (bfausti@gmail.com) writes:
> 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)

I would guess that the service account for IIS has to be a domain account.
But this seems more to be an issue with IIS than SQL Server, so you
may be better of asking in an IIS forum.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Mar 20, 12:06am, Benzine <bfau...@gmail.com> wrote:
> On Mar 20, 1:18am, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> > On Wed, 19 Mar 2008 04:45:50 -0700 (PDT), Benzine <bfau...@gmail.com>
> > 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:13pm, Tom van Stiphout <no.spam.tom7...@cox.net> wrote:
> > >> On Tue, 18 Mar 2008 16:56:56 -0700 (PDT), Benzine <bfau...@gmail.com>
> > >> 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 isa
> > >> >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/micro...e73517ca3f3c9e

Not that I'm lazy :-)

Damien