Re: Invalid authorization specification
From: Dan C. (danc@nospam.com)
Date: 02/05/03
- Next message: hy: "Re: Security for Jobs"
- Previous message: Brian K.: "Re: Security for Jobs"
- In reply to: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Next in thread: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Reply: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Dan C." <danc@nospam.com> Date: Wed, 5 Feb 2003 10:22:06 -0800
Roger,
Thanks, for the info.
However, after reading the information, is sound like
cross-database
ownership chaining has to do with accessing a database on
on server from a database on another server. I am not sure
how this would prevent my ability to directly access a
remote SQL Server 6.5 that is completely independent of my
local SQL Server 2000, which is not used at all by this
particular application (it is also stopped). Furthermore,
Query Analyzer works fine. It's just my application that
can't connect. I would think the connection would be
prevented for both applications. I am not fully convinced
that having a copy of SQL Server 2000 locally has anything
to do with this issue.
Does SP3 somehow affect the OleDb drivers to prevent
accessing remote databases from applications? Does SQL SP3
also apply to SQL 6.5?
Any additional thoughts?
Dan
>-----Original Message-----
>One possibility is that you were using cross-database
ownership chaining
>which SP3 disables by default because it's a security
hole. Look at both
>the sp3 readme.txt and the updated books online
for "cross-database
>ownership chaining"
>
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Dan C." <danc@nospam.com> wrote in message
>news:0a3f01c2cca1$6286fd50$8af82ecf@TK2MSFTNGXA03...
>> This used to work but something happened (perhaps SQL SP
>> 3)...
>>
>> I have an application (.NET/C#) that accesses a remote
SQL
>> Server 6.5 using OleDbConnection. Whenever it tries to
>> open a connection I get an exception:
>>
>> System.Data.OleDb.OleDbException: Invalid authorization
>> specification
>>
>> However, I can use Query Analyzer and connect to the
>> database just fine using the same account. Here is my
>> connection string:
>>
>> Provider=SQLOLEDB;Server=myserver;Initial
>> Catalog=mydatabase
>>
>> Some other facts:
>> 1) Using Windows authentication
>> 2) I have SQL Server 2000 running on my local machine
and
>> I recently upgraded it SP 3. However the app is not
using
>> it (6.5 is on another server).
>>
>> Any idea what is wrong?
>>
>> Thanks in advance.
>>
>> Dan
>>
>
>
>.
>
- Next message: hy: "Re: Security for Jobs"
- Previous message: Brian K.: "Re: Security for Jobs"
- In reply to: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Next in thread: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Reply: Roger Wolter[MSFT]: "Re: Invalid authorization specification"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|