Sage 100

Client's system started bogging down yesterday morning, making it unusable. Launch MAS90 4.5 (Distribution bundle with MAPADOC), even when stand-alone on the server, the desktop appears, but each task launched hangs, displaying only a small frame in the top left corner. After workstation and server restarts, problem persists. Disabled AV. Disconnect from network/internet. No changes to environment. All was working fine as of EOD 12/31. Rebuilt SY0CTL, created new SY_Workstation and SY_Console files. Restored backup set from multiple days - same result. Moved everything to a separate computer - same result. Opened a case with Sage. Next step is to rename Links folder and create new to disengage MAPADOC. Any ideas, tips?

I had a similar issue with a customer. They're not using Trend Micro AV are they? In this case the customer was sure it wasn't the AV. Remember these programs can scan both the server and locally. And in my experience most IT staff have no clue how to configure them correctly or judge their impact on performance beyond opening Microsoft Office and observing that Word seems ok (as it sits dormant on the desktop).

Oh man, this is the stuff of my nightmares. Something changes to a client's environment and only Sage 100 seems to be affected - and now it's your problem. I'm with Wayne. Get them to totally remove the AV for a short period to permit ruling it out.

I's scan the server logs for any new updates and configuration changes. What's the response time when pinging server from workstation? Any difference when using server name vs. IP address? Also, ensure Shadow Copy (or some other backup/archive program) is not running in background.

Renaming Links folder is a good quick test for start up. Also on the workstation have you tried running Regcom.bat from C:\Program Files (x86)\Common Files\Sage\Common Components - Or you could individually run pvxcom.exe and manually register pvxdax.dll

I have not. What do each of these steps do?

Check that the workstations have dotnet. If you install visual C++ that may fix the issue.

@BobPfahnl - Those steps are things that are normally done by Wkstn Setup but may have not have happened due to permissions or whatever. Manually running Regcom.bat (via Run as Administrator options) or manually registering DLLs may be successful alternative. In this case I like @KathrynScofield's Visual C++ idea. I've had to manually run that to get past startup issues on 4.50 PU2 (they fixed in PU3 or PU4). I found the Microsoft download for the VCRedist_x86.exe file was newer than the one under the Mas90\Wksetup folder - http://goo.gl/dVN1AA