Sage 100

I have a recurring issue at a client with Sage Advanced 5.0.4 where a user will attempt to log in to Sage, and the launcher opens then closes. This ends up corrupting the user account so mgmt has to create a brand new user login for them in order to continue working. The ""BroadcastShutdown"" in SY_System is not showing ""Y"". I've asked them to try to disable DEP for the pvxwin32.exe but something about their Windows security will not allow them to. We have also checked to make sure both the server and workstation Sage directories have full control permissions for the Domain Users group. Any other thoughts as to what I can look at in either Sage or Windows? Thanks in advance!

First run them quick and dirty as standalone and see if they still flash in and out

Are you talking about MAS90-mode?

FWIW - DEP instructions - https://www.evernote.com/shard/s270/sh/363a3e7c-0683-4346-a13a-dc8275cc5880/d469cc50d1dbb2e4ecafd4577768f697

Yes - also what's the version of AV? I know in the past there was this problem but it's from a while ago https://www.evernote.com/shard/s270/sh/aebdbec5-a497-4e5f-ac7d-69c708ce8bf0/6c9fc5efa8cc0a63d05a8b9e7dc25b3d

Apparently, they completely disabled DEP and it didn't prevent 4 logins from becoming corrupted this morning. Wayne, what would successfully logging into Sage via MAS90 mode indicate?

I'm wondering if they have to create a new user because they haven't killed the orphaned pvxwin32 task that is still running. See the attached article.

If logins get corrupted in Advanced you should rename the Locate and Sessions pvk files - you're familiar with that procedure, right? You should also do SY_Console and _Workstation while you're at it. You also want to make sure you have your Inbound rule set for the port on the server. If they have done something to corrupt DEP there may be larger issues with the O/S that you won't be able to work through.

If you can login via MAS90 mode then I typically start looking at application vs service, potential problems on the server.

check that launcher32.exe is under the local drive MAS90\Launcher directory - check antivirus has not deleted

Thanks all! Cullen, as I was working on replacing the four files you referenced again last night, I noticed that Sage was running as a service, even though I had asked IT to disable it and start Sage as an app instead...I believe there may be a conflict with concurrent server processes, since the Application Server Startup is added to the Windows Startup menu AND the Service is running. We're going to switch back to just Service again, so we'll see what happens over the next few days, I guess.

I had that happen to me and it was due to Automatic Logoff in user preferences. If the server and workstation times are different it thinks the user should be logged off and it appears to never start.