Sage 100

Sage 100 Advanced running on terminal server in the cloud occasionally throws a Windows error when launching. You then either have to kill the pvxwin32.exe and cross your fingers or log out and back in, again with those fingers crossed. OS in Windows Server 2008 R2 Datacenter SP1. I have attached a PDF of the error and the wonderful Windows detail.

launcher.old.exe???

Yes, @ThereseLogeais, that's the beast!

I suppose you could try replacing it with launcher. new.exe?? :wink:

Try excluding it from DEP. Right click on my computer Go to properties Click on advanced system settings Under performance, click settings Click the Data Execution Prevention tab, and then click Turn on DEP for all programs and services except those I select. Click Add, browse to the executable file for the program and add it.

Doug, we think your solution works. Customer will verify today and forward. - Do you (or anybody) know why this exclusion is necessary? - Is it documented by Sage anywhere? (We couldn't find it.) - Any idea why this error would only occur sometimes? Seems to me like something that should all or nothing.

The first I recall seeing the reports was from Jim Woodhead who posted about this maybe 1-2 years ago. Sage has a couple mentions of it online - one is [here](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=17853&sliceId=1&cmd=displayKC&dialogID=58047&docType=kc&isLoadPublishedVer=&stateId=58049&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl).

We had something similar this week that was caused by someone changing the Windows Firewall Settings. We had to add an Inbound rule in the Windows Firewall Settings to allow access to PVXWIN32.EXE and LAUNCH.EXE. We added IB rules on both the Sage Server and Terminal Server.

@JerryNorman I dont't know exactly why the exclusion is necessary, however, the BEX is a Buffer Overflow Exception. A BEX is memory related, and DEP performs memory checks. https://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx?f=255&MSPPError=-2147217396 I don't know if it is documented by Sage. Because it is a memory error, the frequency of occurrence may depend on memory usage or otherwise memory related, such as configuration or hardware issues.

Does the terminal server have the latest .NET and MS Visual Studio Updates and/or have Webroot Secure Anywhere?

It could also be AV related.

Chuck excluded DEP as Doug showed. This fixed their issue. The problem had been present also with the v4.5 they had before the upgrade (that was before our time with them). The servers (db & TS) are both W2008. Thanks all!