Sage 100

 View Only
Expand all | Collapse all

NewObject Error: 200

  • 1.  NewObject Error: 200

    Posted 03-08-2019 13:46
    Edited by Phil McIntosh 03-08-2019 14:28
    I copied the following code from  working BOI app to use in a BOI app for another customer:
    Private Function ValidateSageUser() As Boolean
    strModErr = "FrmLogin_ValidateSageUser"
    Dim oPVX As Object
    Dim oSS As Object
    Dim retVal As Integer = 0
    Try
    oPVX = New ProvideX.Script
    oPVX.Init(My.Settings.PVXPath)
    oSS = oPVX.NewObject("SY_SESSION") 'Error -2147352567 NewObject Error: 200 occurs here
    retVal = oSS.nSetUser(My.Settings.SageUser, My.Settings.SagePW)
    If retVal = 1 Then
    Return True
    Else
    Return False
    End If
    Catch ex As Exception
    WriteErrorToLog(Err.Number, strModErr + " - " + Err.Description)
    Return False
    End Try
    End Function

    NewObject Error: 200 occurs on the line creating the session.
    PVXPath is verified correct.
    Allow External Access is checked

    Any ideas?


    #scripting


    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------


  • 2.  RE: NewObject Error: 200

    Posted 03-09-2019 02:33
    Is the init path pointing to the server's MAS90\Home path instead of the workstation's (if Advanced)?

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 3.  RE: NewObject Error: 200

    Posted 03-09-2019 09:36
    Changed it to the workstation path (All this is happening on the server, and it is Premium) and the error changed to NewObject Error: 90

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------



  • 4.  RE: NewObject Error: 200

    Posted 03-09-2019 11:18
    I haven't had to deal with an external script on premium so I don't have much insight on it but the path should always point to the server path.

    Did you see Doug's post?

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 5.  RE: NewObject Error: 200

    Posted 03-09-2019 03:06
    Is this Premium?

    Error: "OI Access Failed"
    Products
     
    Sage 100
     

    Description
     
    Error: "OI Access Failed" when executing OITest.exe or Error: 200 when instatiating SY_Session.pvc via Business Objects Interface on a Sage 100 ERP Premium installation. 

    Cause
     
    The SQL Server Native Client designated into the SOTA.INI and MASSQL.Settings file do not exist on the workstation. 

    Resolution
     
    Edit the server's SOTA.INI and MASSQL.Settings file to match what driver is installed on the workstation client and on the server:

    At the workstation, Click on the Windows Start button the Search or Run and type
    ODBCAD32 and press ENTER.
    Click on ODBCAD32.exe
    At the ODBC Data Source Administrator screen click on Drivers
    Note what SQL Server Native Client drivers are listed and close the screen
    Repeat these steps on the server, again noting what SQL Server Native Client drivers are installed there.
    Go to the server's MAS90\HOME\ directory and edit the MASSQL.Settings file:
    Change the following line:
    CONNECT='Driver={SQL Server Native Client 10.0}';
    Enter the newest available SQL client used on both the server and the workstation.
    Exit the file and save changes.
    Go to the server's MAS90\Launcher directory and edit the SOTA.INI file:
    Change the following line:
    [MSSQL]
    DRIVER=SQL Server Native Client 11.0
    Enter the newest available SQL client used on both the server and the workstation.
    Exit the file and save changes.
    OI Test and Business Objects Interface should now run correctly.

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 6.  RE: NewObject Error: 200

    Posted 03-09-2019 09:35
    sota.ini had version 10 while everything else had version 11, but changing it did not fix the issue.

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------



  • 7.  RE: NewObject Error: 200

    Posted 03-09-2019 11:42
    Did you edit the MASSQL.Settings file in the server's MAS90\HOME\ directory?

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 8.  RE: NewObject Error: 200

    Posted 03-09-2019 12:19
    That one as correct - the sota.ini had version 10 instead of 11

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------



  • 9.  RE: NewObject Error: 200

    Posted 03-11-2019 08:52
    Any question of access rights to Mas90 folders?

    ------------------------------
    Lee Graham
    Friendly Systems, Inc.
    ------------------------------



  • 10.  RE: NewObject Error: 200

    Posted 03-11-2019 08:53
    all everyone full control

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------



  • 11.  RE: NewObject Error: 200

    Posted 03-12-2019 10:29
    Edited by Kevin Moyes 03-12-2019 18:46
    SOTAPGM.ini ?
    Edit: or PVX.ini ?

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 12.  RE: NewObject Error: 200

    Posted 03-13-2019 08:21
    PVX.ini also says version 11

    ------------------------------
    Phil McIntosh
    President
    Friendly Systems, Inc.
    Asheville NC
    678.273.4010 ext 5
    ------------------------------