The PVX Object Init Failed during workstation setup on Server

SOLVED

I have installed Sage 2021 on the clients server along with Product Update 2.  The client is currently running Sage 2015.  When I try to run workstation setup I get the error that The PVX Object Init Failed and it does not properly install the workstation setup.  I have check permissions and they are fine.  I have also run the pvxcom file in the ProgramData folder on their C: drive.  We have been having issues with this recently on workstations with this message, but I haven't had it on a server while doing the migration.  I can run the pvxwin32.exe and get into Sage that way, but I'm uncomfortable with not being able to complete the workstation setup.

Any suggestions would be appreciated.

Thanks

Sue

Parents
  • +1
    verified answer

    I seem to be ok now.  My bad...figured out that they had Sentinel1 loaded on the server during my installation.  I reinstalled the software, rebooted the server and now I have a workstation setup.  I should have made sure the antivirus software was off first. 

  • 0 in reply to sued2

    I have the same problem.  So did you need to reinstall sage on the SERVER (with sentinelOne off) before you could get the workstation install to work properly?  Or just turn off SentinelOne on the workstation?

  • 0 in reply to plbcpa

    I reinstalled the software just incase Sentinel1 blocked any files from loading.  I had another issue just the other day when installed Product Update 4 on a server with Sentinel1 turned on.  It blocked pvxsec32.dll during the installation and then striped all the permissions from the existing file.  Had to reboot the server to get the permissions back.

Reply
  • 0 in reply to plbcpa

    I reinstalled the software just incase Sentinel1 blocked any files from loading.  I had another issue just the other day when installed Product Update 4 on a server with Sentinel1 turned on.  It blocked pvxsec32.dll during the installation and then striped all the permissions from the existing file.  Had to reboot the server to get the permissions back.

Children
No Data