If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Pervasive.SQL > SQL Server: Linked Server to Pervasive.SQL 2000i error

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-13-05, 23:26
_msd_ _msd_ is offline
Registered User
 
Join Date: Aug 2004
Posts: 20
SQL Server: Linked Server to Pervasive.SQL 2000i error

Hi,

This is like a 'Part II' to my older thread Pervasive DB as Linked Server to SQL Server

In light of Windows NT end-of-life, we are moving all applications from NT boxes to new boxes -- some to existing Windows 2000 and others to new Windows 2003. With that comes my problem because I have to redefine my Linked Servers...

Here's my new config:
1. My PC (TheClient)
OS: Win XP Pro
Pervasive: 2000i Client
SQL Server: 2000 Client

2. SQL Server Machine (SQLServe)
OS: Windows 2000
Pervasive: No Installation
SQL Server: SQL Server Enterprise (one instance)

3. Pervasive Server Machine (PervasiveServe)
OS: Windows 2000
Pervasive: 2000i Server

Connection:
o TheClient connects to SQLServe through SQL Enterprise Manager
o Defines Linked Server:
Linked_Perv_Serv
Product Name: MS OLE DB for ODBC Drivers
Data Source: PERVASIVE_DB
Location: PervasiveServe
Catalog: PERVASIVE_DB
Security: Login's current security context

When I try to click Tables on the Linked Server, Liked_Perv_Serv, I get the following error: Error 7399: OLEDB provider 'MSDASQL' reported an error.
Data source name not found and no default driver specified]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005:]


Other Info: Even though I change the Security of the Linked_Perv_Serv to force a valid user id to PervasiveServe machine, I still get the same error.

Q: Aside from the microsoft's explanation of Error 7399 , should I look for other cause of this error like defining ODBC DSN's on SQLServe machine? Is that a requirement in my case?

Thanks in advance for your input.

_msd_
Reply With Quote
  #2 (permalink)  
Old 02-09-05, 01:49
Dilyias Dilyias is offline
Registered User
 
Join Date: Feb 2004
Posts: 78
Yes, you need to define system odbc's on your new sql server.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On