Sage 100

I have a customer on 4.05 (moving to another system soon, I hope!) but they are getting an error 105 in program SOWUAD in file GL_20XXX.soa. I think this is a history drill down file but it cannot be rebuilt (not in the listing) or reinitialized. I can't pull it up in DFDM (it locks up) so I am not sure what to do next. Didn't get the line number yet but besides restoring from a backup, are there any other utilities I could use to access this file/record? (It errors during Phase 3 - IM/GL History Files.)

Backup first (guessing you did that already ) Try: File >run >UFAR. I don't have full instructions on running that utility handy but you should be able to find them on sage knowledge base if you search on UFAR.

Sorry. Not file run Run UFAR"" from a providex command window

I was going to suggest UFAR also. It's the only thing I know of.

Copy file to a higher version and rebuild there assuming the layout is still the same. Perhaps?

look for files approaching or > 2GB ?

I have the GL_20 listed in Rebuild Application Key files in my 3.71 test system. Really need the line number to verify which file has the error. Can the file be restored from last nights backup?

SOWUAD Sales Journal Update - IV The attached has the list of files that this program interacts with. I looked it up Error 105 in TRSG since the version is older: Per TRSG : Error 105 Common causes may be: 1. A record or multiple records within a data file are damaged. 2. A data file is damaged. 3. Errors 112 & 114 are caused by Realtek drivers Possible solutions: 1. Rebuild the file with the appropriate utility. Valid records that are removed must be reentered. 2. Rebuild or Restore the file from backup. 3. Restore the file from backup. 4. For further suggestions, see Error 47. 5. Contact Best Software Customer Support Services for additional assistance. Error 47 Info. Error = 47 (Substring Out of Range) This data record is smaller than the program expects. MAS 90 Error Message: ERROR: 47 PROGRAM: XXXXXX LINE: #### Common causes may be: 1. A data record containing the information being processed is damaged. 2. If the data is part of a data entry function, the line detail file may be damaged. 3. An application data file conversion from one level to another may not have been completed. 4. A field in the data file record may be blank or missing.

4.05 General Ledger was in Business Framework, but GL_15, GL_20 and GL_21 still exist as .SOA files.

Sorry scrap that. You said GL_20 not SO_20. Definitely dont't reinitialize it. It could be locked / open. See if you can rename it. If not kill the session on the server or reboot the server then you should be able to rebuild. Open files don't appear in the rebuild utility.

Thanks all. Will be contacting the customer this AM.

So I could run the UFAC utility but now I can't run the UFAR utility. This is the correct path (I've rekeyed it several times). This is a copy of the original gl_20xxx.soa file. Thoughts?

Here are some of my ancient notes using UFAR. Sage Resellers E-mail dated 7/20/09 Of course. Since you have exhausted all your other options, use *UFAR. 1. Make a backup of GL5 2. Within MAS run SYZCON 3. Type at the prompt: RUN ""*UFAR"" 4. For the filename type ..\GLABC\GL5ABC.SOA (replace ABC with your company). Note the current number of records 5. When you get to the questions with the A-Wrong,B-Wrong,C-Wrong,D-Wrong,E-Wrong choices leave them unchanged as they are all true for GL5. If it was SY0CLT.SOA you would have arrowed over to D-Wrong and E-Wrong 6. Press Enter while you're highlighted on Yes When you're done note the current number of records again and compare. Hopefully you didn't lose too much. You're still not done: 7. In MAS do a regular rebuild Key Files on GL5 followed by Rebuild Sort Files for GL. 8. Using DFDM look at number of GL5 records again and compare. 9. Now you have to figure out how out of balance you are and take corrective measures for that. And another from 2001 Sometimes you may receive an error message while running the SVXBLD file that a file is corrupted, please restore from backup and rerun SVXBLD. (There is a known issue with SY0FIL). UFAR is an older DOS utility that may allow you to proceed. This must be activated from the Start, Run window that must include the directory path as part of the command line (e.g. g:\apps\mas90\home\pvxwin32 *ufar). Follow the prompts to rebuild the file in question. If program does not activate from the Start/Run window, then exit to DOS and run from there.

I just activated it via SYZcon. by typing run ""*ufar don't include the second double quote on the line.

Thanks @JeffSchwenk - it's rebuilding now. Kind of a slow process. I hope this fixes it!

Anytime. I am not sure if it is just me but I have found that the second double is never needed. BTW, why are they still on v4.05? Enhancements, off maintenance, won't give up their Novell server??? Hopefully, you have unsupported version support rates.....

This is the same guy who called me at 10:30pm on New Year's Eve two years ago. Yes, they get a higher rate. We have tried upgrading them several times, once for each new CFO. I am glad they are moving on, to be honest.

Well hopefully they are moving to a different program for the right reasons. With something that old, they may be comparing apples and oranges (Old MAS to new glamorous software) when the latest Sage will do the same thing. I have a client that moved to a Great Pains based system for the bells and whistles and even the CFO now says they made a mistake.........

I don't want them, they can go.... Want their number @JeffSchwenk ???

Hmmmmm. Do they have a sense of humor??? And what late model luxury car does the owner drive?? And did he pay your NY's Eve support invoice in full?

Wow, looking back at your first note Jeff, I hope I can rebuild the file - couldn't yesterday and the rebuild sorts did nothing. If not, I will give them your number!

Phew, got this error but the update continued and the GL is in balance. Next time, I WILL give him your number Jeff!

C'mon. As a long time reseller, you LOVE a challenge...