Re: Invalid authorization specification

From: Roger Wolter[MSFT] (rwolter@online.microsoft.com)
Date: 02/06/03 

From: "Roger Wolter[MSFT]" <rwolter@online.microsoft.com>
Date: Wed, 5 Feb 2003 16:13:12 -0800

Sorry, I'm in over my head. You might want to try the
microsoft.public.sqlserver.connect group to see if they have more ideas
there. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan C." <danc@nospam.com> wrote in message
news:08fb01c2cd65$70e51ed0$8df82ecf@TK2MSFTNGXA02...
> Again, thanks for your input.
>
> The application runs just fine on our production machine,
> it's just on my development machine that it can no longer
> talk to the database.
>
> I also ran the code as a Windows EXE so that it would
> [automatically] use my personal Windows credentials (which
> are good enough for Query Analyzer) to no avail. Again,
> this used to work.
>
> I can't tell if the problem is in my computer, in the
> server, or in the connection in between (though if I
> assume that if it couldn't see the server the message
> would be different).
>
> Dan
>
> >-----Original Message-----
> >SP3 installs a new version of MDAC so I suppose it's
> possible that there's a
> >behavior change.  Does this app run anywhere?  SP3
> doesn't apply to SQL
> >6.5 - there haven't been and won't be any Service Packs
> for 6.5.  Query
> >Analyzer user ODBC and I assume your application uses
> OLEDB so there may be
> >a difference there.  I'm not an ASP.Net expert but the
> error you're getting
> >sound more like it doesn't like the authentication you're
> doing rather than
> >a permissions error.
> >
> >-- 
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"Dan C." <danc@nospam.com> wrote in message
> >news:01c901c2cd43$7cfc5610$d3f82ecf@TK2MSFTNGXA10...
> >> 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
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

Relevant Pages

  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: upsizing to sql 2005
    ... the word SERVER in it, ... You can access to the database by multiple means (Access, ... and how does it update the SQL database with the new records in Access? ... Query Name: Arcadia - ARC ...
    (microsoft.public.access.queries)
  • Re: Linked Tables in Access
    ... any use of SQL Passthru, Linked Tables or any other use of MDB / MDE ... server, or would I also need to convert *those* queries to passthrough ... I've been trying to understand why Access database files become corrupt. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Leveling by ID vs. "Standard"
    ... of this trade called Project Management. ... a database for the "Project Tables," ... to write reports on data from the server database. ... product supporting queries created with SQL. ...
    (microsoft.public.project)
  • Re: Trouble Getting VS.Net 2003 WalkThroughs MSDE Connection
    ... Config Tool of SQL Server? ... > link to download the PUBs database. ... >>> Setup and they directed me to install MSDE and they attached a ...
    (microsoft.public.sqlserver.msde)