Sage 100

Users locked out of TS Sage 100 Advanced v2015, does this look like a DEP fix? Worked fine last week after upgrade, but not today. Guess this has happened before on prior versions. Troubleshooting, no history for myself with client.

Check for invalid printers and duplicate pdf converters.

Here's some text from an old Sage KB article on this: Follow the steps below to prevent Windows from monitoring MAS 90/200 program. Right click Computer and select Properties. Click Advanced system settings from right panel Select Advanced tab. Select Data Execution Prevention tab. Click Add and browse to the ...mas90\launcher\ folder. Select Launch32.exe click Open and Apply settings. May need to reboot server for setting to take effect.

Would assume since this is TS I would need to do as an admin.

Yes, more than likely.

If on terminal server, the inherited Sage PDF printers will cause issues. General policy for us is to always the printers on RDP session.

On the TS you can also set the properties for the shortcut to the Sage 100 Desktop to run as administrator.

Tried the DEP fix, both TS and Mas server rebooted, same screen pops up not allowing anyone in. Can't be pvxwin32 running or locked files if server rebooted. CRM is integrated, could that be an issue?

On the error click on ""View Problem Details"".

Hope you can see this @AlnoorCassim . Client was in Friday and yesterday fine, today first thing they have no access

Kelly this does in fact look like DEP. The first thing to do is not mess around with adding exceptions. Ask IT to temporarily set DEP option on both App Server and TS like this: ""Essential Windows Programs and Services"". A reboot is required for it take effect. If it still doesn't work a hardware based DEP setting may be present that prevents Windows from overriding it. There is a tool called BCDEdit.exe for this purpose to modify the server's BOOT.INI file for DEP and PAE setttings. I had to do this a few months ago to I have to run right now but I'll send the info for your IT guy / gal later today or they can research themself. Do not run BCDEdit yourself.

Kelly, if Option 1 doesn't work here is what you can send to IT as Option 2. It applies to both MAS server and TS. ------------------------------------------------------------------------ ** Please note the following steps should only be performed by the company's IT department ** Hardware based DEP may have been set to a level higher than the default value and by design it prevents o/s DEP override in Windows via Control Panel / System. The nx option of BCDEdit tool can be used to restore the DEP level to default or completely disable it: https://msdn.microsoft.com/en-us/library/windows/hardware/ff542202(v=vs.85).aspx Using this tool will edit the server's BOOT.INI file. The persistent BEX module error in Sage 100 that is not affected by DEP override in Control Panel / System likely indicates the current setting is equivalent to: bcdedit.exe /set nx AlwaysOn Any DEP changes made in Windows are ignored with the AlwaysOn switch. You can change it to use one of the following: 1) Restore DEP to hardware default: bcdedit.exe /set nx OptOut This means you can now override in Windows via Control Panel / System. Now exceptions for Launch32.exe, pvxwin32.exe, pvxiosvr.exe, masapsvr.exe, etc will be honored. Don't forget to reboot after making the changes. 2a) Disable DEP completely: bcdedit.exe /set nx AlwaysOff This means DEP is set to Off at hardware level AND you cannot even override via Control Panel / System either. The radio buttons will be grayed out. Note this will also auto- disable Physical Address Extensions (PAE) except on Server 2003 SP1. I normally stop here and use this as a baseline to verify DEP errors no longer occur with Sage 100. IT can also determine if now or at a later point they want to re-enable PAE. 2b) Re-enable PAE bcdedit.exe /set pae ForceEnable To keep PAE enabled, you must explicitly run the 2nd command using ""/set pae ForceEnable

Thanks for sharing that @AlnoorCassim

Thanks @AlnoorCassim and everyone else who contributed suggestions, Had their IT handle the DEP changes, but also ended up finding there were 2 application servers setup going to same Sage path and same port. One would allow you to login to Sage the other gave this message ""stopped working"" once I removed one of the app servers and reran WKSETUP pointing to the correct service, all was good.