hello,
I'm trying to create a linked server from an SQL2000 to a Unify ELS
(very old, odbc is version 1) database on SCO unix.
The odbc driver is old but it works fine when used by applications for
creating reports.
What I want to do is make a linked server from the SCO box to the win2k
box. So, I'm using enterprise manager to create the linked server.
The DSN of the unify database is CORE_OFFICE1

I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
Datasource name not found and no default driver specified.

When I create the linked server I chose the OLE DB for ODBC drivers.
I put 'CORE_OFFICE1' for the Data Source name. I also setup the
security with the name of a unix account for login/password.
What else should I have?

I'm new at this linked server stuff!

Product Name:
Data Source:
Provider String:
Location:
Catalog:

Thanks,

Oskar

Did you install the ODBC driver on the SQL Server box - not
just your PC - and create a system DSN on the SQL Server
box?

-Sue

On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
<nothing@nothing.gone> wrote:

>hello,
>I'm trying to create a linked server from an SQL2000 to a Unify ELS
>(very old, odbc is version 1) database on SCO unix.
>The odbc driver is old but it works fine when used by applications for
>creating reports.
>What I want to do is make a linked server from the SCO box to the win2k
>box. So, I'm using enterprise manager to create the linked server.
>The DSN of the unify database is CORE_OFFICE1
>
>I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
>Datasource name not found and no default driver specified.
>
>When I create the linked server I chose the OLE DB for ODBC drivers.
>I put 'CORE_OFFICE1' for the Data Source name. I also setup the
>security with the name of a unix account for login/password.
>What else should I have?
>
>I'm new at this linked server stuff!
>
>Product Name:
>Data Source:
>Provider String:
>Location:
>Catalog:
>
>Thanks,
>
>Oskar

Sue Hoegemeier wrote:
> Did you install the ODBC driver on the SQL Server box - not
> just your PC - and create a system DSN on the SQL Server
> box?
Yes, the odbc driver is installed on the sql server box. However, I had
it as a User DSN instead of a System DSN. I changed that and now I get
this error:
Error 7399, authentication failed. Data source rejected connection attempt.

I put the 'sa' user as the local account on the linked server security
tab and I put the unix user/password as the remote account.
I think this is getting closer, but it's still not there!

Thanks,

Oskar

>
> -Sue
>
> On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
> <nothing@nothing.gone> wrote:
>
>
>>hello,
>>I'm trying to create a linked server from an SQL2000 to a Unify ELS
>>(very old, odbc is version 1) database on SCO unix.
>>The odbc driver is old but it works fine when used by applications for
>>creating reports.
>>What I want to do is make a linked server from the SCO box to the win2k
>>box. So, I'm using enterprise manager to create the linked server.
>>The DSN of the unify database is CORE_OFFICE1
>>
>>I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
>>Datasource name not found and no default driver specified.
>>
>>When I create the linked server I chose the OLE DB for ODBC drivers.
>>I put 'CORE_OFFICE1' for the Data Source name. I also setup the
>>security with the name of a unix account for login/password.
>>What else should I have?
>>
>>I'm new at this linked server stuff!
>>
>>Product Name:
>>Data Source:
>>Provider String:
>>Location:
>>Catalog:
>>
>>Thanks,
>>
>>Oskar
>
>

Yeah...it's closer. Your just stuck on the authentication from SQL to
Unify. You may want to try first by just setting the security context
so that anyone accessing the linked server uses the same login - that
will at least eliminate who you are logging in as for now.
As you are doing this in enterprise manger, on the security tab,
remove the stuff you put in. Then select the last option "Be made
using this security context" and then enter the login and password
needed to access Unify.

-Sue

On Mon, 16 Aug 2004 09:00:08 -0500, pheonix1t <nothing@nothing.gone>
wrote:

>Sue Hoegemeier wrote:
>> Did you install the ODBC driver on the SQL Server box - not
>> just your PC - and create a system DSN on the SQL Server
>> box?
>Yes, the odbc driver is installed on the sql server box. However, I had
>it as a User DSN instead of a System DSN. I changed that and now I get
>this error:
>Error 7399, authentication failed. Data source rejected connection attempt.
>
>I put the 'sa' user as the local account on the linked server security
>tab and I put the unix user/password as the remote account.
>I think this is getting closer, but it's still not there!
>
>Thanks,
>
>Oskar
>
>>
>> -Sue
>>
>> On Sun, 15 Aug 2004 22:03:00 -0500, pheonix1t
>> <nothing@nothing.gone> wrote:
>>
>>
>>>hello,
>>>I'm trying to create a linked server from an SQL2000 to a Unify ELS
>>>(very old, odbc is version 1) database on SCO unix.
>>>The odbc driver is old but it works fine when used by applications for
>>>creating reports.
>>>What I want to do is make a linked server from the SCO box to the win2k
>>>box. So, I'm using enterprise manager to create the linked server.
>>>The DSN of the unify database is CORE_OFFICE1
>>>
>>>I'm getting 'Error 7399: OLE DB provider 'MSDASQL' reported an error.
>>>Datasource name not found and no default driver specified.
>>>
>>>When I create the linked server I chose the OLE DB for ODBC drivers.
>>>I put 'CORE_OFFICE1' for the Data Source name. I also setup the
>>>security with the name of a unix account for login/password.
>>>What else should I have?
>>>
>>>I'm new at this linked server stuff!
>>>
>>>Product Name:
>>>Data Source:
>>>Provider String:
>>>Location:
>>>Catalog:
>>>
>>>Thanks,
>>>
>>>Oskar
>>
>>

update
I found out that the unify driver only works in the USER DSN, not the
SYSTEM DSN. So, after a bit of research I've found that it's possible
to do a kluge by using an Access MDB file to connect to the Unify
database via linked table manager. Then, make the linked server using
the Access driver on the SYSTEM DSN.

How does this sound to you? Kinda wild, huh?

Now, I'm in the process of trying to make it work.

Ah, job security!!


Oskar

ps. Any and all advice welcome