My issue is below. The pvxwin32.exe task does not respond when started up by the host. Please note that VT is the external program that links w/Sage 100 Premium 4.50 through BOI. Any suggestions would be appreciated. Thank you.

The current issue is described as follows:

1. When VT needs to interface with MAS, the Sage app pvxcom.exe is automatically launched by VT. When VT is done using the MAS, the interface is closed, which causes the pvxcom.exe program to exit normally.
2. VT interfaces with MAS normally throughout the day, about every 4 minutes. No problems are experienced.
3. At 11pm, VT stops interfacing with MAS so that backups, etc. can run. This is a normal, planned and expected suspension of interface activity.
4. At 3am the next morning, VT attempts to interface with MAS. Pvxcom.exe is automatically launched by VT, however it “hangs” or “locks up”. This causes the VT Host app to suspend, forever waiting for pvxcom.exe to finish, yet it never does. So the MAS interface is “down”, resulting in pick slips not printing, fixed weight labels not printing, and order fulfillment to not appear in MAS.
5. When someone notices that things are not printing or flowing back to MAS, they go to server and kill the VT Host. The action of killing the Host causes the pvxcom.exe program that the Host is waiting for to stay running in the background forever.
6. The user then starts the VT Host app again. VT host immediately attempts to interface with MAS. Usually, the interface starts and works normally for the rest of the day. Sometimes the Host is killed and restarted multiple times. Whether this is necessary, or if the user is just impatient is unknown (it can take 2 minutes or more for the Host to complete its interface with MAS and begin printing, depending upon the backlog of pending orders, etc.)
7. As far as I am aware, there are no displays, popups or error messages on server when the user goes to kill the VT Host app. The only indication of a problem is that things aren’t printing.