Sage 100

Client on 4.1 (unknown SU) receiving Error 121 APWUBA Line 8730 when printing AP checks (he actually appears to be doing a reversal). Appears to happen after printing a check register. Nothing in the KB and a search for error 121 shows all sorts of different issues -- from integration to data. Any experience or thoughts?

Is it possible this is similar? http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=486762 Resolution ID 486762 Resolution Details TITLE : Error 12 PRWUBA 8730 in Payroll Check Register of Sage MAS 90 and 200 DETAILS : Error 12 PRWUBA 8730 in Payroll Check Register Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP Application: General Ledger Version Reported: 4.20.08 Subject: Error 12 PRWUBA 8730 occurs in Payroll Check Register. Possible Resolution: Activate and set up the Bank Reconciliation module. If Bank Reconciliation is not being used, do not integrate the Payroll and Bank Reconciliation modules. Expand Payroll and Setup. Double-click Payroll Options. Click the Integrate tab. In the Integrate Payroll with the following area, clear the Bank Reconciliation check box.

Wayne, the program is trying to open a file. The code is: E1$=F0$+C0$+"".soa""; E1=F0; OPEN (E1) E1$ look at info to get the key and channel or DEBUG andprint E1$ (for file) E1 for channel. this will tell you the file it is having a problem reading. File may be busy or locked.

Woooo

Do you know if SP1 is installed and which SU? I've seen a 121 on an OPEN twice. Once it was because the Start In for the MAS90 shortcut pointed to a HOME directory for a different install of MAS. The other dealt with an alternate directory accidentally being set in MAS. IOW, if not using alternate directories DFDM sy_company, Fields 13 and 14 should be blank.

I'm not sure -- they are using BR already. I was puzzled because there was nothing directly on point in the KB.

Thanks - I'll check this out. Client has been processing ok for a while (albeit on 4.2) so I'm not thinking it's some quirky initial setup type thing. I'll try to find what data file it's having an issue with.