Sage 100

Anyone familiar with this solution? We are getting this exact error.

Is SU 17 the level where they enabled the 64 BIT OS (why am I thinking 23) -- anyhow I had similar with a customer who could get into MAS but it crashed if they went to try to print a report (they were on paperless) and when I threw the latest SU in there it fixed it -- re-ran WKSETUP.

They are on su 22

Thought it might be the SEP but it still has the seem problems anfter putting in the exclusion. I am letting SAGE review. Sage says that this version is compatible with what I have but it looks like the late SU broke it. :( I have reinstalled WKsetup a couple times.

I had one user crashing on 4.30 (yes this is correct version) when processing a receipt of goods variance register. That's the only time, though.

Well it turn out the the client's Terminal server is running on 2008 R2 64 bit and 4.3 is still not compatible the ""R2"" part of it. ""Egads"" . (BTW 4.40 is) Sage is talking to engineering to determine have big an issue this is.

My customer's server is Windows Server 2008 R2 32-bit.

These compatilities matrixes are DEADLY!!!

Unfortunately the ASP used 64 bit!!

Well we found the issue. It was the DEP on the 2008 server. You might ask what DEP is. (I didn't know) What is Data Execution Prevention? Data Execution Prevention (DEP) is a security feature that can help prevent damage to your computer from viruses and other security threats. Harmful programs can try to attack Windows by attempting to run (also known as execute) code from your computer's memory reserved for Windows and other authorized programs. These types of attacks can harm your programs and files. DEP can help protect your computer by monitoring your programs to make sure that they use computer memory safely. If DEP notices a program on your computer using memory incorrectly, it closes the program and notifies you. Turns out that I needed to exclude the Launcher32.exe program from the DEP testing. #forcecloseError #WIN2008 Look like WIN2008 R2 64 BIT works!!!

#DEP

We excluded launcher32.exe and pvxwin32.exe on both the server and the terminal server and it did not solve the issue for our customer on that one report. We believe that it's resolved on version 4.40 as PO is then in the framework.