Sage 100

Sage 100 advanced 2015.04 on Windows 8.1. Uninstall/reinstall workstation setup after power failure and get a white screen with a plus sign in it instead of the expected workstation synchronization. Deleting the record from SY_Workstation for that computer did not solve. Other computers are running Sage 100 fine. Any ideas?

Is there a pvxwin32 session running on the workstation?

Yes, and it has to be killed via task manager - it does not respond to clicks

is there a stranded process on the server?

Are they running as an application or a service?

From Sage KB: System files may be damaged Have all users log out of Sage 100 ERP (and for the Advanced or Premium editions, stop the Sage 100 ERP Service or Application) In Windows Explorer, go to the \MAS90\MAS_System folder where Sage 100 ERP is installed Rename the following files: SY_Console.m4t SY_Workstation.m4t For Sage 100 ERP Advanced or Premium editions only: Go to the \MAS90\Home\Lib\_Appserv folder also rename the following files: Locate.pvk Sessions.pvk Restart the Application Server Configuration and have someone log in. This will automatically generate the Sessions.pvk and Locate.pvk If Sage 100 ERP Advanced or Premium is normally run as a Service: Stop the Application Exit Application Server Configuration Start the Service

Rename SY_Console, then try again

If they are running as an application there will be an error to clear if they are running as a service you will have to restart either way you will see an app crash entry in the event log.

Did you try stopping and restarting the Sage service/Application Server. There could still be a rogue pvxwin32.exe task from that workstation running on the server.

Reboot the server. There is likely a hung process onthe server. T

Got everyone out (amazing how that can happen in the middle of the day when it's the owner's computer acting up), stopped the service and cleared a bunch of stuck processes. Thanks to all!

Sometimes terminating the extra threads using Master Console is sufficient, if you can identify them (by workstation / user).

These were there even after the service was shut down. They did not show in master console

In that case, when you can't get users out, it is possible to add PID to the Windows Task Scheduler (View - Select Columns) and look for the extra threads that way. I always add the Command Line to the list too, so I am sure to be looking at client threads and not the service.