Re: 'MSDASQL' headache



Just in case anyone else has a similar issue, I resolved this with
authentication. The DSN used to create the linked server on SQL
connected using credentials on the Progress database. We added a new
user on SQL Server to mirror these credentials and used that in the
ASP.NET connection string. Pretty obvious I guess but it's all a
learning curve. Anyway, works great now. Thanks for your help, though -
much appreciated.

.



Relevant Pages

  • MS SQL 2005 to Sybase via Linked server
    ... I'm having an issue setting up a linked server connection on a new SQL 2005 ... The connection is working on the existing sql 2000 box. ... I enter all the sybase server info and use the "Test ...
    (microsoft.public.sqlserver.odbc)
  • Re: Windows authentication in domain
    ... The way I understand the Integrated Security setting on a connection string, ... setting it to true or SSPI will cause SQL to use the credentials of the ... My question really is why doesn't SQL attempt to use credman ...
    (microsoft.public.sqlserver.security)
  • Re: Windows authentication in domain
    ... "When using SSPI for authentication for connectivity, if the connection ... why doesn't SQL Server use other credentials such as those that may ... security, since realistically we would only want the current user ... credentials passed and authenticated. ...
    (microsoft.public.sqlserver.security)
  • Re: Link Server
    ... I was trying to use a connection is the DTS packages, ... But it sounds like I have to write out the sql code in order to connect. ... >> I'm not sure what connection to use and how to set it up. ... > do you mean a linked server is defined on your SQL Server? ...
    (microsoft.public.sqlserver.dts)
  • Re: Windows authentication in domain
    ... the domain user must be explicitly listed a SQL login. ... > "When using SSPI for authentication for connectivity, if the connection ... why doesn't SQL Server use other credentials such as those that may ... > security, since realistically we would only want the current user ...
    (microsoft.public.sqlserver.security)