Problems with sql server 2005 linked servers

I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
I have set up several linked servers to our AS400 and they work
correctly as long as I am connected to the database as "sa" via Sql
Server security.
For example I can run queries against the AS400 tables with no problem.
If I connect to the database using Windows Authentication and try to
run the exact same query I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "HiTOLEDB400"
for linked server "AS400".
My Windows login is setup the same as the "sa" login as far as I can
tell.What is the configuration for the security mappings on the
linked server?
-Sue
On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>I have set up several linked servers to our AS400 and they work
>correctly as long as I am connected to the database as "sa" via Sql
>Server security.
>For example I can run queries against the AS400 tables with no problem.
>If I connect to the database using Windows Authentication and try to
>run the exact same query I get the following error:
>Msg 7399, Level 16, State 1, Line 1
>The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>error. Access denied.
>Msg 7350, Level 16, State 2, Line 1
>Cannot get the column information from OLE DB provider "HiTOLEDB400"
>for linked server "AS400".
>
>My Windows login is setup the same as the "sa" login as far as I can
>tell.|||The linked server is set to use an as400 userid/password for every
connection.
Sue Hoegemeier wrote:
> What is the configuration for the security mappings on the
> linked server?
> -Sue
> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
> wrote:
> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
> >I have set up several linked servers to our AS400 and they work
> >correctly as long as I am connected to the database as "sa" via Sql
> >Server security.
> >For example I can run queries against the AS400 tables with no problem.
> >If I connect to the database using Windows Authentication and try to
> >run the exact same query I get the following error:
> >
> >Msg 7399, Level 16, State 1, Line 1
> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
> >error. Access denied.
> >Msg 7350, Level 16, State 2, Line 1
> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
> >for linked server "AS400".
> >
> >
> >My Windows login is setup the same as the "sa" login as far as I can
> >tell.|||Okay...the first thing you'd want to try is to make sure you
have Allow In Process option enabled for the provider.
That may not do it though. The other thing to try after that
would be to enable delegation for the Windows domain
account.
-Sue
On 14 Sep 2006 12:42:22 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>The linked server is set to use an as400 userid/password for every
>connection.
>Sue Hoegemeier wrote:
>> What is the configuration for the security mappings on the
>> linked server?
>> -Sue
>> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
>> wrote:
>> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>> >I have set up several linked servers to our AS400 and they work
>> >correctly as long as I am connected to the database as "sa" via Sql
>> >Server security.
>> >For example I can run queries against the AS400 tables with no problem.
>> >If I connect to the database using Windows Authentication and try to
>> >run the exact same query I get the following error:
>> >
>> >Msg 7399, Level 16, State 1, Line 1
>> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>> >error. Access denied.
>> >Msg 7350, Level 16, State 2, Line 1
>> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
>> >for linked server "AS400".
>> >
>> >
>> >My Windows login is setup the same as the "sa" login as far as I can
>> >tell.