SQLBase Linked Server

  • Hello,
    I'm trying to export data from a SQLBase database to SQL Express 2014.  The driver I'm using is Unify SQLBase 11.6 (Provider in SQL shows as Unify SQLBase OLE DB Provider).  Both SQLBase and SQL Server are 32 bit.  I can't seem to get the configuration correct when trying to create a linked server, or when trying to use SSIS Export/Import Wizard.  In both cases I get a message that says "No configuration file".  I do have a configuration file and I'm specifying it, but I must not be putting it in the right place. 

    My linked server setup page looks like this:
    Provider:  Unify SQLBase OLE DB Provider
    Product name: PT (this is the SQLBase database name)
    Data source: GREG-THINK (this is the machine name which the SQLBase database resides)
    Provider string: C:\Program Files (x86)\Unify\SQLBase116\sql.ini (location of my configuration file)
    Error Message - "The OLE DB provider "SQLBASEOLEDB" for linked server "Name" reported an error.  Authentication failed.  OLE DB Provider "SQLBASEOLEDB for linked server "Name" returned message "No configuration file". (Microsoft SQL Server, Error 7399)

    When using the Import/Export Wizard, my Data Link Properties look like this:
    Data Source: PT (this is the SQLBase database name)
    User name: SYSADM
    Password: Password
    Extended Properties: (under the "All" tab) - C:\Program Files (x86)\Unify\SQLBase116\sql.ini (location of my configuration file)
    Error Message when clicking "Test Connection" button - Test connection failed because of an error in initializing provider.  No configuration file.

    I'm really hoping somebody can tell me what I'm doing wrong.  This is for a big client that is starting to lose faith that we can complete the project.  Thank you!

  • lina_weiss - Thursday, June 7, 2018 8:26 PM

    Hello,
    I'm trying to export data from a SQLBase database to SQL Express 2014.  The driver I'm using is Unify SQLBase 11.6 (Provider in SQL shows as Unify SQLBase OLE DB Provider).  Both SQLBase and SQL Server are 32 bit.  I can't seem to get the configuration correct when trying to create a linked server, or when trying to use SSIS Export/Import Wizard.  In both cases I get a message that says "No configuration file".  I do have a configuration file and I'm specifying it, but I must not be putting it in the right place. 

    My linked server setup page looks like this:
    Provider:  Unify SQLBase OLE DB Provider
    Product name: PT (this is the SQLBase database name)
    Data source: GREG-THINK (this is the machine name which the SQLBase database resides)
    Provider string: C:\Program Files (x86)\Unify\SQLBase116\sql.ini (location of my configuration file)
    Error Message - "The OLE DB provider "SQLBASEOLEDB" for linked server "Name" reported an error.  Authentication failed.  OLE DB Provider "SQLBASEOLEDB for linked server "Name" returned message "No configuration file". (Microsoft SQL Server, Error 7399)

    When using the Import/Export Wizard, my Data Link Properties look like this:
    Data Source: PT (this is the SQLBase database name)
    User name: SYSADM
    Password: Password
    Extended Properties: (under the "All" tab) - C:\Program Files (x86)\Unify\SQLBase116\sql.ini (location of my configuration file)
    Error Message when clicking "Test Connection" button - Test connection failed because of an error in initializing provider.  No configuration file.

    I'm really hoping somebody can tell me what I'm doing wrong.  This is for a big client that is starting to lose faith that we can complete the project.  Thank you!

    I only remember bits and pieces but with the data access, the ODBC drivers used to allow specifying the path to the ini file but the OLE DB provider did not. I don't know if that changed at all. But I would check the PATH system variable and make sure the path to the ini file there. It used to look in the SQLBase directory or search the locations in the PATH system variable. Not sure if that is still the case but might be worth a try.

    Sue

  • Thanks for the response Sue. I actually upgraded my SQL installation from Express to Standard and was able to get the connection working with no problem.  Now I just have to pay for it!  Thanks.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply