Sage 100

Workstation unable to start MAS 200 - I am having several clients over recent weeks where one user for whatever reason cannot start MAS200. They click the icon and they just get a white screen with a + Any Ideas? To fix I am stopping the host. What house cleaning items do you guys do to a MAS 200 install to keep it running optimally?

I think the resolution to that white screen issue is to rename 1 or more files (e.g., sy_workstation, sy_session, sy_console).

That sounds like what happens when the work station Windows firewall is turned on.

Is this that problem with antivirus from a week or two ago? There was an issue of a false positive impacting multiple sites. I'm mobile so don't have the details. I think it is posted in socialcast

http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=483617 And: http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=520854

I have run into a similar situation in the past and it all came down to permissions. What is the workstation and server os?

I have a client experiencing this on a regular basis, but all users access MAS 200 via TS. For them, it appears to be a lost connection to the TS that shuts down the users' session but leaves the pvxwin32.exe process running on that user's profile. It also causes an error on the application server to the effect of ""MAS has stopped working and needs to be shut down."" Closing that error has no effect on the application server. Client is running server as an appliation, but this occurred when running as a service as well.

I do not think permissions as killing all pvxwin32 on server and restarting the application host seems to be resolution. It is just getting old as it seems to be happening more often and it appears to bounce to a different workstation each time. @EdWlodarczyk I see your scenario alot also. This one is different.

it seems in 4.4 the SY_Console does not recreate itself automatically. So I manually deleted bogus records.