Sage 100

Sage 100 Advanced v4.5, Remote users accessing via terminal services. Last week started encountering the following error message immediately after logging into the session. User will try to connect numerous times before finally locking into a session. Looks like a memory error. Will try reinstalling the workstation once IT gives me access. Any other thoughts? The error details state: Problem signature: Problem Event Name: BEX Application Name: Launch32.exe Application Version: 4.3.1.7402 Application Timestamp: 2a425e19 Fault Module Name: RpcRtRemote.dll Fault Module Version: 6.1.7601.17514 Fault Module Timestamp: 4ce7992f Exception Offset: 000018f3 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.16.7 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

I ran into this (or a variant) and nothing really worked save for the regedit trick to expand available server memory. It was a real PITA too because everything worked fine before their upgrade.

Oops - https://90minds-com.socialcast.com/messages/17828841

Switch Sage to run as a desktop application. Still getting this BEX issue. NO redirected printers on TS.

Any of the usual suspects? - invalid printers, etc - the weird stuff that can bring down Sage quickly.

Jeff, does the server have a firewall and did you make a exception for the port Sage is running on? I think we even had to on the Sage Icon Properties tab check on to run this application as Administrator. I also had an anti-virus software update cause launch32,exe issue and I had to add that file to my list of exclusions.

Does it work running MAS 90 style from the TS? If so in the past a typical cause of Launcher errors is registry permissions when it tries to load up the Information Center page. You could ask IT to run the Microsoft Procmon.exe utility - http://technet.microsoft.com/en-us/sysinternals/bb896645 They would start the ProcMon trace when you click the MAS icon on the TS and stop it once BEX error appears. The log is easier to look at in Excel. They could export the log to tab delimited file then open that in Excel then look for ACCESS DENIED errors. That will tell them the registry or file that is inaccessible.

Have you tried turning off DEP?

Nicolas, great suggestion we have had to do that on all 2008 TS Servers.

Wayne what is the registry hack to increase the server memory? The other thread's links to Evernote go no where.

@NicholasWebb - I think this is the one Wayne is referring to.

@JeffSchwenk Thanks.

What is hard to get my head wrapped around is that Life has been good for the year and then wham, this comes out of the blue.... I'll check the DEP as the TS is running on WIN 8

Couple questions on DEP. I used this link that @JimWoodhead posted about a year ago. http://dsdtips.com/how-do-you-resolve-mas90-or-mas200-force-close-errors-when-you-are-running-mas-on-a-terminal-server-on-a-win-2008-r2-64-bit-server/ The situation is as described on the link (WIN 8 TS, 64 OS). The question I have is that the article doesn't exactly specify whether the launch32.exe is on the TS Sage client folder or on the network launcher folder. I linked it to the TS server version. Let me know if it is supposed to be on the network install but I am surmising that I have the correct one.

I performed it on the application server not the terminal server.

I do it on both and if IT doesn't allow me to turn down DEP to ""all essential Windows programs and services"" (the better setting) then make sure both pvxwin32.exe and Launch32.exe are listed as exclusions. Here's a screenshot I sent to a client once. One more thing even if doesn't say so DEP changes requires server reboot to take effect.

Yikes, there are a lot....

Better to turn it down to the ""low"" setting, reboot, and try. At least temporarily

@AlnoorCassim - those are my thoughts....