Sage 100

Upgrade from MAS90 3.4 to 3.71 on the way to 2014 issue I have 3.71 installed on several XP machines. When I try to open any of them I immediately get the message "" ProvideX for Windows has encountered a problem and needs to close."" I found one laptop where 3.71 worked and did the overwrite conversion of 3.4 to 3.71. Now it is getting the same error. I have looked everywhere for a solution but nothing seems to work. Can anyone help me with this?

Invalid printer?

No, none

I am with Wayne on this. These errors are almost always a problem of some sort with a printer name or settings.

Any anti-malware programs? Have you tried disabling anti-virus?

So are you saying that the data files have been converted to v3.71 or you are not to that step yet?? If the files have been converted, I would reinstall v3.71 somewhere and just copy the APxxx, ARxxx files over to the clean version of v3.71 and go from there. Unless you have some legacy apps, EVERYTHING is gong to need to be rewritten or reconfigured. No sense in bringing the old configuration files over to clutter v2013. And since it is v3.4, I doubt that you have many UDF's to worry about,..... Doing this will bypass the hiccup and actually reduce the amount of scrubbing you have to do......

The problem has been solved in a manner of speaking. To be clear as to what the problem was, any time in 3.71 that you clicked on a Lookup button (the magnifying glass), the above error occurred and the screen closed. Solution 1 was to replace the ALE files from a good installation..\MAS90\SOA\ Sy1Q01, SY1Q02, SY1Q03, SY1Q04, SY1QDD This did not work for me. Solution 2 was to reboot into safe mode. In safe Mode, the error does not occur. That is an indication that one or more programs is running in the background on my system that is causing this error. One or more of the programs that could be the cause are Microsoft Windows Accessibility programs. I can continue to run the 3.71 upgrade utilities in safe mode. Once i get the monkey off my back, I will investigate to find out what program is causing the problem and report back

Full steam ahead..... I had something nearly as ugly. Upgraded user from v4.4 to v2014. Paperless off stopped working, PR paperless remittance advices stopped and vendor ACH file would not generate. Turned out to be unknown conflicts installed on the workstations and server. Client ended up virtualizing a new server and buy three new workstations (existing ones were getting on in age). After getting new clean machines, v2014 is working now. Sage spent five weeks with it and are still stumped.....