Sage 100

 View Only
  • 1.  I am trying to make a Visual Integrator Job run au

    Posted 08-08-2013 09:49
    I am trying to make a Visual Integrator Job run automatically as a scheduled task. I created a batch file to do this and put these commands in that file: E: CD \Sage Software\ERP Server\MAS90\Home Pvxwin32.exe ..\Launcher\Sota.Ini ..\SOA\Startup.M4P -ARG AUTO UIOFF user pwd ABC VIWI07 AUTO This batch file launches PVXWIN32.exe but doesn't run the VI Import. I have to go into Task Manager and kill it. If I substitute the last line with: Pvxwin32.exe ..\Launcher\Sota.Ini ..\SOA\Startup.M4P -ARG DIRECT UION user pwd ABC VIWI07 MANUAL then the VI job will launch and I need to select ""Accept"" then enter the Company, User and Password (even though they are on the command line) and the job performs properly. Am I missing something from the command line? the VI Job setup?


  • 2.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-08-2013 09:54
    I'm using this from @JimWoodhead on Sage 100 Premium 4.50, running from the server (please sub in your paths, company codes, user and pwd) c: cd ""\Flores Apps\Sage\v440\MAS90\Home"" PVXWIN32.EXE ..\LAUNCHER\SOTAPGM.INI ..\SOA\STARTUP.M4P -ARG DIRECT UION user password SFN VIWX0B AUTO


  • 3.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-08-2013 11:16
    The command line is slightly different, depending on the module - use SOTAPGM.INI or SOTA.INI For framework modules such as: Accounts Payable, Accounts Receivable, Bank Reconciliation, Common Information, e-Business Manager, General Ledger, Return Merchandise Authorization, and Sales Order modules, you would type: C:\MAS90\HOME\PVXWIN32.EXE ..\LAUNCHER\SOTAPGM.INI ..\SOA\STARTUP.M4P -ARG DIRECT UION JWSMITH PASSWORD ABC VIWI00 AUTO For all other modules, you would type: C:\MAS90\HOME\PVXWIN32.EXE ..\LAUNCHER\SOTA.INI ..\SOA\STARTUP.M4P -ARG DIRECT UION JWSMITH PASSWORD ABC VIWI00 AUTO


  • 4.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-08-2013 14:01
    OK. I tried substituting SOTAPGM.INI for the SOTA.INI and I made sure I had DIRECT, UION and AUTO in the proper places. As before, the PVXWIN32 process fires up but the VI job apparently never runs and the PVX process never ""shuts down."" Any idea what I am missing?


  • 5.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-08-2013 18:11
    @ChuckPeddy - Are you using the actual user code in place of ""user"" and the actual user password instead of ""password""? Here's one I know works on a 4.5 installation: PVXWIN32.EXE ..\launcher\sota.ini ..\soa\STARTUP.M4P -ARG DIRECT UIOFF JHF bananna ACS VIWX00 AUTO Try putting a ""pause"" in the batch file before and after the command. You may be able to see an error message or where it is hanging. Is it possible it is actually running and hasn't completed yet?


  • 6.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-09-2013 19:32
    Try modifying the ODBC setup, adding the company code, user name and password. Then run the job.


  • 7.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-10-2013 13:00
    @ChuckPeddy - These 2 lines here: E: CD \Sage Software\ERP Server\MAS90\Home Modify the 2nd line like this: E: CD ""E:\Sage Software\ERP Server\MAS90\Home"" or alternatively: E: CD E:\SageSo~1\ERPSer~1\MAS90\Home One of my MAS quotes since the early years has been spaces might be the root of all evil.


  • 8.  RE: I am trying to make a Visual Integrator Job run au

    Posted 08-11-2013 10:29
    @AlnoorCassim - I am sure you are correct as usual. DOS doesn't recognize spaces or more than 8 characters. Interesting though how Chuck says ProvideX is executing... possible if pvxwin32.exe was added to the path but not probable if not in the home directory. That's why I suggested putting the pauses in the batch file. I usually change one directory at a time when using a batch file so to insure the path to the executable is correct.