Sage 100

Client upgraded to Sage 100 2013 PU 2 from 4.3 and every time they try and print AP checks they get a Sage 100 has encountered a problem MS error followed by an access violation at address 65117316 in module PVXIO.DLL at address 00CAAC44. Anyone seen this or have any ideas of how to correct? This appears to be happening on only one computer (the AP person, of course).

WAG: Is the PVXIO.dll the correct version, or still left from 4.3?

Completely uninstall the workstation client, reboot, then reinstall? Admin rights? What type of workstation OS? What happens if you use a clean form? Are you running Crystal at the server using the CS ODBC?

We are getting this at a 2013 Adv client, consistently. The AP check printing has been having issues at other 2013 clients, too. As a matter of fact, every client on 2013 (and that's only 3) is having issues with AP check printing. The only solution we had for this client was to run it on the server for now.

Workstation is Windows 7 32-bit. I have uninstalled and reinstalled the client and did check that the PVXIO.DLL is correct (dated June, 2012), so I think that is OK. Have not tried a clean form so that is a thought. @BethBowers for your clients that are having the issue is the error a similar error message. I have also tried to print to different printers from the same workstation, but no luck.

Mine is pvxwin32. And it happens on more than one workstation.

Hmmm, I'm up to 7 2013 upgrades (only one is Advanced), and slowness is the only issue any of them are having. Did you replace the formulas in the AP check form? Are all the right DLLS in the right place?

Just had to do the DLLS at one place, oddly enough. And they are still having issues locking up there, for no good reason. They are Std. The Adv started with the locking up and progressed to the error messages.

@BarbaraGoldstein I did not make any changes to the formulas. Is this required on all installs? Have not seen this before.

@JohnLeonard, I've had to replace the formulas on every check form I've done so far. Sage is supposed to fix this. We'll see if it gets into PU3.

I haven't had to do anything with any formulas.... Is it the MICR? I don't have anyone using that on 2013 yet.

They are not using MICR. I suspect it has something to do with the DLL's

I have had the exact same issue at 4 different clients as well. But only at clients that have upgraded, my new installs have not seemed to have this issue. My clients tell me that it is a little more random (sometimes they don't have the error other times they do). I'm starting to think it may be related to extended stub although I'm in the early stages of trying to prove/disprove that; however, the last several instances have all been when the client (2 different clients) were printing a check run where extended stubs were required. . early on I did not think to ask about extended stub but now I'm asking people if they have an extended stub when they get the error. I created a new crystal check form and extended stub form from scratch at 2 clients and it seems to have resolved their issue (but I'm still crossing my fingers every day that they don't call me back about this). One client had 6 companies with heavily modified check form and I opened each in crystal and did verify database and changed the page setting to ""NO PRINTER"" on both the check form and the extended stub for all 6 companies. That was several weeks ago and they have not called back since. Hope maybe this helps someone else out there . at some clients when I do ""verify database"" I find that there are formulas that won't compile - these formulas deal with the g/l accounts. I know my client does not print the GL account on the stub so I simply Remarked them out so they don't cause problems.

Side note - I've also uninstalled/re-installed so many times with this issue that I can't count them; but it never seemed to help

@BarbaraGoldstein Can you elaborate on what formulas you changed? I'm making notes on this since it seems widespread. The image you attached appears to be for DLLs (which I'm assuming also work for AP checks)

I believe (@BarbaraGoldstein please confirm) that you are OK if you start with the check form that comes with 2013. It is upgrading older forms where the problem happens as neither verify database nor mascrw catch theses issues with the formulas.

I think you didn't see the other file I attached - with the formulas. Here are a couple screenshots of the formulas you need to change. And @PhilMcIntosh , you are correct.

I have a call into the client to find out if there were extended stubs in this check run. I have also set the printer to ""No Printer"" and will report back if this seems to resolve the issue.

I just upgraded one from v4.3 to v2013. Will be interesting to see how next week goes for them.....

v2013 upgrade lesson - get paid in advance as they may not be able to pay you afterwards...

Good point @PhilMcIntosh . Maybe their ATM card will still work!

FYI - Just spoke with the client and they did not have any extended stubs on their check run.

Sage just released a hot fix to address some of the v2013 printing issues. From Sage Hotfix for LM5004-T has been released. See attachments. It is to address the following. Multipart printing doesn't work Custom Report user defined parameters don't work. *General Report Performance. R&D is still working with SAP on issues that we believe are related to the changes to the new version of Crystal Reports. Please provide feedback after installation as to whether this has shown improvement out in the field. Kind Regards, Carmen Cruz Sr. Technnical Tools Support, Sage 100 ERP Sage Mid-Market Solutions

Interesting! Thanks @JimWoodhead. Any idea if this is included in the upcoming PU3? Hopefully, we don't have to install it separately for the next four months.

More