Sage 100

Sage 100 v2015 Advanced - Installed workstation client two months ago, it worked fine. Now when I launch Sage advanced, a providex window pops up and system freezes. I launch in 100 Std mode and everything runs fine. Of course the KB is down for ""enhancement"". I have uninstalled the workstation, rebooted and reinstalled. Still same outcome, the PVX window freezes. Help!!!!

A couple of config changes to try: 1. Right click on the shortcut and ""run as administrator"". If that works then right click on the shortcut and change the properties to always run as administrator. 2. Right click on the shortcut and change the properties to run in XP SP3 compatibility mode.

Also check the server and port in the shortcut and in sota.ini on the local workstation. If there is a DNS issue the server name may not resolve. You may try entering the server IP in the shortcut and in sota.ini.

Great ideas but double goose eggs resulted.

- Try temporarily disabling AV. Boot the workstation in safe mode and see if it runs.

Is there any error message on the server ?

Good Question. Will look tomorrow

If it runs in Standard mode, maybe the port is blocked by the WS firewall? Is the user configured to use the C/S ODBC driver? Does it work if you log into that ws as a different network user?

@MarkKotyla I don't even get to the login screen. A PVX window opens, there is a ""+"" in top left corner, then the cursor and process freezes.

How are you running Advanced - app or svc? Try it as an app if you were running as svc. Also the usual suspects -- ..\mas90\home\lib\_appserv folder and rename sessions.pvk and locate.pvk files. Can other users get in?

All others can get in. Just this workstation. Running as a service. When I was onsite a few months ago during the initial install, it worked.

Does it work with different network user ID on that ws? Must narrow down whether this is a ws issue or user issue.

Jeff I have seen that before. There is a locked file on the server. Get everyone out and either kill all the open files or easier to just re boot the server.

(white screen appears with a single ASCII character in the top left), the solution provided by Sage support was as follows: 1) All users out of MAS 2) Stop the MAS Application that runs on the server 3) On the server, rename the following files (they will get recreated) a. e:\accounting\mas430\mas90\mas_system\sy_console.m4t b. e:\accounting\mas430\mas90\mas_system\sy_workstation.m4t c. e:\accounting\mas430\mas90\home\lib\_appserv\locate.pvk d. e:\accounting\mas430\mas90\home\lib\_appserv\sessions.pvk 4) If you cannot rename the files, then the file is in use and is most likely causing the corruption 5) Restart the server, if needed 6) When server restarts, you need to make sure that MAS Application is not running 7) Rename the file(s) that you couldn't before the restart 8) From the Start List, select Sage Software | MAS Application Server Configuration (this will recreate the sessions.pvk file), then close this screen 9) From the Start List | Startup, run Application Server Startup 10) Go into MAS 200 Desktop to ensure that you can get into MAS, then close out of MAS S11) Disconnect (do not log off) from the Server

Oh, and I'd check the Master Console first to see if there is an orphaned process for the user / workstation. Sometimes killing that will allow the login.

Sorry for the tardy response. The solution was a server reboot. Thanks to all for the great suggestions.