Sage 100

I am experiencing an APPCRASH issue on a W7 wkstn with MAS 200 v 4.30.18. It starts with a MAS has stopped working error and this is the details: Problem signature: Problem Event Name: APPCRASH Application Name: pvxwin32.exe Application Version: 8.10.0.0 Application Timestamp: 47b36116 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.17725 Fault Module Timestamp: 4ec49b8f Exception Code: c0000005 Exception Offset: 00036a5f OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 71b8 Additional Information 2: 71b88ad1368c8cc1ac4b9567b9e99d6c Additional Information 3: 4466 Additional Information 4: 446680cffddda22cf0e482cdda29d6a6 This appears to be happening during different printing tasks. Any assistance would be greatly appreciated.

Have you tried changing the printer that you are printing to as a test to rule in/out a printer driver? Are you printing to Paperless Office? I always suspect user rights - maybe uninstall and reinstall workstation using ""run as administrator

When there are printing issues the first thing I check is to see if all printers listed in the Printers/Faxes folder are actually physically on the network. Invalid printers is the most common cause of problems.

This from the Sage Community (is this an HP printer with Terminal Services by any chance?) ""I was able to resolve this problem. In my case it was a combination of some workstations not having .Net 3.5 installed and the Terminal Server not liking the print drivers for our networked HP printers. I Installed the drivers locally on the client workstations and made sure they had .Net 3.5 installed. TS 2008 needs .Net installed on the client workstation in order to properly redirect printing to the client. This is a fairly common issue with redirected printers. Redirected meaning: A printer that locally connected to a computer but is being printed to from a program run through a terminal server / Citrix connection. The terminal server and the workstation have to have the same drivers. If they become out of sync you can see a variety of different issues in our program and other programs as well. Simple text printing will often be ok. This will lead some users to believe it is a MAS 90 or 200 issue. If you are unfamiliar with TS or Citrix and you don't know how to sync the drivers you can always add the local printer to the Terminal Server computer as a network printer then print to it from there instead of using redirection.

@Wayne - no to paperless, can print to this printer sometimes, I will try uninstall/reinstall. @Louis - did this @Kenneth - not TS local connection

I vote for uninstall and reinstall as the first choice, and maybe restore/repair ntdll.dll. From what I read, it's usually third party software than causes issues with ntdll.dll.