The PVX Object init failed or Object ProvideX.Script is invalid when installing Sage 100 Standard Workstation Setup

Description

Error: “Object ProvideX.Scriptis invalid” and/or “The PVX Object init failed” during Workstation Setup client install for Sage 100 (or a third-party software, such as StarShip Link)

Cause

  • Permissions on the server where Sage 100 is installed
  • Local permissions on the workstation
  • Multiple Sage 100 Workstation Setup client installations exist on the same workstation, and one of the “..\MAS90” folder for the workstation (not the server) was deleted instead of un-installed
  • Pvxcom.exe is not running
  • Anti-Virus blocking
  • A File Group setting in Windows File Server Resource Manager, on the Sage 100 Server, is preventing a temp file with a “.zzz” file extension from being created under …\MAS90\HOME\LIB\ folder

Resolution

Windows security/permissions:

  1. Check permissions on the Sage 100 server for the Windows user logged into workstation
    • Confirm permissions on the Sage 100 shared folder and the security on that folder itself
      • Note: Test by granting the Windows user rights to the share point above the “MAS90” directory on the Sage 100 server, and to all folders and files below, including “MAS90”. (In one instance, it turned out the Windows user was removed from the Everyone group, and that was the cause of the error.). Can also test by verifying the user can create a new file or folder in…\MAS90\HOME\LIB\ folder
    • See the Related Resource “How to configure network security for Sage 100 Advanced ERP” and the Sage 100 ERP Installation and System Administrator’s Guide for more information on security
  2. Attempt to launch Sage 100 ERP in Standard or MAS90 mode directly by browsing to the Sage 100 ERP server and launching PVXWIN32.EXE (see Related Resource “How to run Sage 100 ERP Advanced or Premium in Standard mode”)
    1. In Windows Explorer, browse to the server’s ..\MAS90\Home folder
    2. Double-click Pvxwin32.exe
    3. At the Providex prompt, type RUN “STARTUP.M4P”
    4. Press ENTER
    5. Log into Sage 100 ERP
  3. If you receive errors setting permissions on folders or share or launching Pvxwin32.exe, troubleshoot those errors
  4. Once permissions and errors resolved, re-run the workstation setup again (see Related Resource “How to install Workstation Setup for Sage 100 ERP”)

Possible Antivirus interference:

If you have any sort of anti-virus or anti-malware software, temporarily disable it or add an exception to the software so that it does not scan the MAS90 directory. If you need help with this, please contact your IT administrator or team.

Multiple Workstation installations:

  • Remove other unneeded workstation installations that might be interfering
  • Reinstall the correct Sage 100 ERP Workstations

Run PVXCOM prior to installing Sage 100 ERP Workstation:

  1. Via Windows Explorer, browse to the folder containing the executable file:
    • For 64-bit operating systems: C:\Program Files(x86)\Common Files\Sage\Common Components
    • For 32-bit operating systems: C:\Program Files\Common Files\Sage\Common Components
    • Note: If pvxcom.exe cannot be found on the workstation, the Sage 100 server’s com.exe file can be accessed and run from the workstation.
  2. Right-click the pvxcom.exe, select “Run as Administrator”
    • Note: There should be no response when running this Pvxcom.exe program
  3. Run the Sage 100 ERP Workstation installation program again
    • Note: For more information on proper installation steps, see the Related Resources section below.

Remove ‘zzz’ file type from File Group in File Resource Manager on the Sage 100 server

  • Contact your Network Administrator for assistance with temporarily allowing “.good” file types under the …\MAS90\folder
    NOTE: Look for ‘*.zzz’ in one or more of the File Groups in File Server Resources Manager on the Server. If found, temporarily remove from list until installation is complete

Support

If necessary, seek the assistance of Acute Data Systems to help provide assistance with this process.