Sage 100

I have a client that fired me this morning but calling me for support this afternoon. They have a 3.71 install. One user is having an issue where any ALE will cause a APPCRASH pvxwin32 error. They are using a shared application through citrix. When we RDP directly to the server we are not having issue. I have tried reducing the screen resolution (without a reboot as I remember high resolution monitors being an issue). Any suggestions?

Get a credit card and a signed ""no refund"" agreement.

Besides firing yourself again?

Try - In Windows Explorer, go to ..\Mas90\Soa. Rename SY1Q01, SY1Q02, SY1Q03, SY1Q04, and SY1QDD. Restore these files from the last good backup.

Taking the high road on this one. Found out only on this workstation. Turns out this workstation login into a new domain. They have a 3.71 install that will not do ALE but the 4.3 install (don't ask) will.

Perhaps ""run as administrator""?

Do these have a custom lookup that might be triggering it?

In case it's relevant, I don't remember which one but in 3.x there was a 3rd party handicapped accessibility tool, some type of screen magnifier that was incompatible with ALE lookups. It would also cause pvxwin32 exception error / APPCRASH. Disable it and ALE would be fine. It may have been the Magnifier accessibility tool built into the o/s but I think it was a 3rd party just can't remember the name. It was obviously a Windows-user specific issue. It was written up as a defect and fixed in 4.00. In case it could be relevant.

Same user works from a different computer. We have narrowed to a specific computer.

@AlnoorCassim , I believe what you are referencing is the narrator tool. That was my case all those years ago. I was working with an association that hires and represents the blind. They all use a program called Jaws as the narrator is not as appreciated. Sage indicated they would not touch the issue. So... I tested narrator and found out it did not work with narrator as well. Called Sage back and told them the product was not Windows compatible. They fixed it in days for narrator which solved it for Jaws.

Yes it was Jaws! And I was thinking about the narrator tool in Windows. But if remember correctly, the Narrator fix (which worked for Jaws too) was for a specific partner and I guess that was you, but if memory serves (which is not reliable) the fix wasn't included in general release until later. However, since same user works from a different computer here, it doesn't matter here obviously. If you have an old 3.7x system lying around, as a test you could with everyone out of the system, rename their SY1Q*.soa files, copy yours in, verify you can login then try the user who hasn't been working.