Sage 100

Customer on Sage 100 Advanced with remote users logging onto terminal server (2008 I believe but can't log in at the moment to verify). When they try printing custom reports, they get the ""MAS has stopped working"" error. I think it is related to redirected printers but can't be sure. Thoughts?

Do you know the version? In 4.40 PU6 there was a fix that expanded the key in Sy_ReportSetting and Sy_LastFormUsed to include the (remote) WorkstationName. This is what allows users from different remote sites to share a common form code or report. Otherwise you risk inheriting the last printer used by the last user when you pull up a form code or report. If that last printer is not fully accessible to the current user (because it is a user from a different location) that's when this problem occurs.

You could have them try and not re-direct the printers. In the Remote Desktop Connection panel click on show options and then on the local resources tab uncheck Printers. Then have them reconnect and see if this still happens.

If it is related to redirected printers, @JohnLeonard is right on. That's a great way to know for sure.

I have had this and had to open the form code and remove the printer in order for it to work.

It is 4.50.4 and I went in to the reports and set them to No Printer selected. Even if they select a non-redirected printer and click preview, they get the error. This is with custom reports only, I think.

I have had situations where redirected printers didn't disappear on their own. I had to clean up printers manually after getting everyone to fix their RDP client. If there was a redirected clone of a server printer on the terminal server, that the server printer had issues with MAS. Also have had to remove printers that did not exist anymore to relieve print issues.

We have a client who is currently experiencing this also. They are on 4.50.4 and it is happening when they try to access the help files. Their environment is Sage 100 Advanced on Server 2008 with a TS server.

@ThereseLogeais Did you get this resolved?. I ran across this last year 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/

No, I did not - Thanks for the info @JimWoodhead !!!

You can turn off the DEP for pvxwin32.exe

if it is due to the printer issue that @AlnoorCassim mentioned I have had success by removing the printer name from the appropriate record in SY_ReportSetting.