Error 105 in SOWMBA

[jimpin]

Our sever locked up the other day and afterwards we received an Error 105 in SOWMBA. The problem was that one batch was not accessible, couldn't process or delete. I rebuilt key and sort files in all modules, trying to access the bad data between without success. Then we pushed the updates through, and ended up processing it but with the G/L being out of balance, and had to manually find the files with the incorrect figures and edit them. So I think we worked it out, but it was a two day process.

My question is...What are the temp files created for batches, is it safe to delete them, or is there some easier way to fix a problem like this.

 

[mas90guru]

Technical Reference & Support Guide for MAS90 and MAS200 has complete file layouts. You can access it here:

http://support.bestsoftwareinc.com/mas/Trsg/trsg.cfm

You may need a login - which you can obtain here:

http://shop.bestsoftwareinc.com/BOSS/Main/frmRegister.aspx

Regards,

Wayne Schulz
Schulz Consulting, LLC

http://www.s-consult.com

 

[PgmrChris]

An error 105 (actually any error over 100) can be translated into a corrupt file. It typically happens under one of two scenarios: abrupt power intruption (or users routinely doing a ctl-alt-del or power-off), or network/hardware issues.

The key to correcting this is to identify the program name (SOWMBA), the error no. (105) and the line no. (not specified).

Once you have those in hand, you'll need to contact the people that sold you MAS90 (or Best). They'll take that information and lookup exactly which file is corrupt. They can then walk you through repairing it (which is very quick and simple). A responsible MD/Best support person would also inquire into the reasons on why this happened (power outage, network setup, etc), so that this situation can be prevented in the future.

It is EXREMELY LIKELY that all of your data is okay. I can tell you from experience that the SOWMBA program is the program responsible for S/O invoice batch selection -- so the file most likely corrupt is either SOO (the batch file that simply contains a record for each batch & the date & user that setup the batch), SO5 (your invoice data entry header file--contains invoice header-level info for all invoices in your system, regardless of invoice batch), or SO5XXXXX (the invoice data entry file containing the header-info for just the invoices in that batch).

MAS90/200 comes with a utility to repair these files -- and like I've said, it's quite good. The >100 errors typically indicate a "bad index" or "key".. so the actual data is in good shape -- the system just doesn't have a good way of accessing it. The repair utility guts the data out and rebuilds it into a new file, thereby repairing the index/key-table.

Best of luck! Let us know how it all turns out!