Sage 100

 View Only

  • 1.  Outside program error when connecting with Sage 100

    Posted 05-29-2020 13:59
    Working on an outside program that calls Sage 100 tasks, i.e. Sales Order Entry, Purchase Order Entry, both entry and inquiry screens.  (Essentially a multi-program menu screen for Sage 100 and another system.)  Upgrading from 2016 Advanced to 2018 Premium, thus updating this working outside menu for the SQL-based system. 

    Receiving this message: Object Interface License not found for this MAS90/200 installation [workstation path].

    Online searches have provided many possible solutions, yet none are resolving.  

    Any ideas are greatly appreciated!  TIA

    ------------------------------
    Michelle Taylor
    ERP Consulting Manager, CS3 Technology
    918-388-9772
    ------------------------------


  • 2.  RE: Outside program error when connecting with Sage 100

    Posted 05-29-2020 20:22

    3 things come to mind. Hope this helps:

    1. Try running OITest.exe from \mas90\Home. Feed it the same Sage user, pswd, and company code that the outside app uses. I'm guessing that works.

    2. In developer's outside app code they have to pass the correct "INIT path" which must be the server's path to \mas90\home, NOT wkstn's \mas90\home. Using VBScript example you can fwd to them:

    strInitPath = "\\Server\Sage\v2019Std\MAS90\Home"  ' <-- should NOT be workstation path
    Set oSS = CreateObject("ProvideX.Script")
    oSS.Init(strInitPath)

    3. ** Driver mismatch. BOI connections will typically use the pvx.ini from \Home to get the DRIVER= value. Sometimes it's \Launcher\Sota.ini. But in either case, it will compare it with the Driver= portion of the CONNECT= line of the MasSql.Settings file. When they don't match you get trouble. Below is a scenario I've run into a bit and in this example I changed MasSql.Settings to "10.0" to match the 2 .ini files. It doesn't have to be fixed that way it just needs to be the same in all 3 places.

    ..\MAS90\Home\pvx.ini
     [MSSQL]
    DRIVER=SQL Server Native Client 10.0  


    ..\MAS90\Launcher\SOTA.INI
     [MSSQL]
    DRIVER=SQL Server Native Client 10.0  
      

    ..\MAS90\Home\MASSQL.Settings
    @Application
    CONNECT='Driver={SQL Server Native Client 11.0}';  <-- Change to 10.0 in this example



    ------------------------------
    Alnoor Cassim

    Accounting Systems, Inc. (ASI)
    Email: alnoor@asifocus.com
    Orange County, CA
    ------------------------------



  • 3.  RE: Outside program error when connecting with Sage 100

    Posted 06-02-2020 11:16
    Thank you @Alnoor Cassim  Making progress!​

    ------------------------------
    Michelle Taylor
    ERP Consulting Manager, CS3 Technology
    918-388-9772
    ------------------------------

    Original Message


Related Content