Sage 100

 View Only

  • 1.  Error '429' when using VBA to open Sage

    Posted 10-17-2019 12:13

    We often automate the running of a V/I job in Sage by setting up a macro in the client's related workbook that will open Sage  and run the specified V/I job for them. The current client is using Sage 2019 Advanced, but the code opens Sage in standard mode, as below:

    Dim CompCode As String
    CompCode = InputBox("What company would you like to import to?", "Sage 100 Company Code")

    Dim objShell As Object
    Set objShell = CreateObject("WScript.Shell")

    objShell.CurrentDirectory = "\\server\sage\version2019\mas90\home"
    objShell.Run "\\server\sage\version2019\mas90\home\pvxwin32.exe -hd ..\launcher\sota.ini ..\soa\startup.m4p -arg direct uion odbc cbdo " & CompCode & " viwi01 Manual"

     We have been successful with this operation in 32-bit and 64-bit environments.  It works now on my computer, which is 64-bit OS with Excel for Office 365 MSO 64-bit, but not on the client's computer, with the same specs.  The error below occurs  at the point of Set objShell = CreateObject("WScript.Shell")

    The error  "Run-time error '429':

    ActiveX component can't create object" pops up when it gets to this section of vba code



    ------------------------------
    Nina Getchell
    Accounting Technology, LLC
    ------------------------------


  • 2.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 12:19
    What version and build of Windows on your computer and on the customer's computer?  ie Win 10 Pro Build 1803, Win 10 Pro Build 1809, Win 10 Pro Build 1903, etc.

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



  • 3.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 12:30
    There is a known compatibility issue with the pvxwin32.exe providex interpreter when using Win 10 Pro build 1809 or higher.

    The below information may serve as a workaround:

    As a temporary workaround rename ..\MAS90\Home\xmllite.dll to \MAS90\Home\xmllite.old
    *Caveat* If the customer has development partner modifications that include the interpreter utilizing XML functionality renaming the file above will cause an error in the development partner functionality."

    You will have to do the rename workaround on both the server and the workstation.

    The interpreter is hard coded to load this library from the home folder (MAS90\Home\xmllite.dll). This version of xmllite.dll (shipping with Sage 100) is incompatible with current versions of Windows 10 and the Interpreter is incompatible with the current Windows version of the file (…\Windows\SysWOW64\ xmllite.dll)

    A fix is planned for the Sage 100 version 2020 release.

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



  • 4.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 12:59

     

    The client is using Windows 10 Pro Build 18362, and they have Kissinger Certified Payroll.  How can I determine if this enhancement uses the xmllite.dll that you referenced as the problem?

     

    My own Windows 10 Pro build is 17763, which according to your response, explains why it works on my system and not on the client's, correct?



    ------Original Message------

    There is a known compatibility issue with the pvxwin32.exe providex interpreter when using Win 10 Pro build 1809 or higher.

    The below information may serve as a workaround:

    As a temporary workaround rename ..\MAS90\Home\xmllite.dll to \MAS90\Home\xmllite.old
    *Caveat* If the customer has development partner modifications that include the interpreter utilizing XML functionality renaming the file above will cause an error in the development partner functionality."

    You will have to do the rename workaround on both the server and the workstation.

    The interpreter is hard coded to load this library from the home folder (MAS90\Home\xmllite.dll). This version of xmllite.dll (shipping with Sage 100) is incompatible with current versions of Windows 10 and the Interpreter is incompatible with the current Windows version of the file (…\Windows\SysWOW64\ xmllite.dll)

    A fix is planned for the Sage 100 version 2020 release.

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


  • 5.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 13:11
    This is only a theory but it is worth exploring.  I would ask Kissinger if they use the xmllite.dll for anything.

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

    Original Message


  • 6.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 16:30

    I have tried renaming \MAS90\Home\xmllite.dll and xmllite64.dll on the workstation and the server but receive the same error at the same spot in the vba code.  Do you have any other suggestions?



    ------Original Message------

    This is only a theory but it is worth exploring.  I would ask Kissinger if they use the xmllite.dll for anything.

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


  • 7.  RE: Error '429' when using VBA to open Sage

    Posted 10-17-2019 13:38
    Does the VI job work if you use a batch file?  Perhaps use VBA to create a batch file and call it (or to simply run a pre-configured batch file)... then you won't have issues with Excel DLL conflicts.

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



Related Content