Sage 100

Have Sage 100 Advanced 4.40.0.5 customer who cannot update the SO Daily Sales Journal since for yesterday. It scrolls through Calculating Costs and Commissions then hangs at Processing Sales Journal. I have rebuilt files, recalculated sales taxes, looked at most suspect fields in Crystal (sales/cost GL accounts, u/m conversion factor, etc.) and cannot find anything out of whack. I have also turned off the printing of recap reports, purged sales history (files weren't that huge) but I can't think of anything else to look at!!! Ideas??

Date? Customer No?

Dates look good. They are retaining deleted invoices so there are two without a customer number. Should that matter???

I'd get rid of them.

@MarkKotyla agree !

Now it's stuck on this.

Have you checked to make sure it hasn't posted to some of the files?

Which one(s) would you start with @DianeRuth ?

I would start with AR Open and AR Invoice Header/Detail. I think those are still the first tables that get updated, then inventory.

But they have never gotten to the ""Do you want to update?"" question. It has never printed the journal itself.

Should the SO_DailyPostingWork be empty? I see old records from 1/7/2013 plus some from today.

Try running in 90Mode? A different workstation even though it is advanced.

Try backing it up and re-initializing it? Those old records don't seem like they should be there.

Ok then I would rename the so_daily posting wk and take off retain deleted invoice . Then make sure you can go in all invoice header and line with out a error. They try again... How many invoices?

What is the Anti-Virus? I had a client using Microsoft Security Essentials (which is not supported by Sage), and had a similiar problem. Adding the Sage file extension exclusions (on all workstations) or using a different Anti-virus resolved the problem.

isn't Tuesday night AV update night? Good thought @KennethPhillips . Maybe take a look at the server to see what was installed last night and do a roll back?? All extreme.

NOW we're getting somewhere... They post CC's on SO's as deposits but sometimes, they don't ship the entire amount so the invoice shows as a negative balance (invoice total less deposit amount). There was one invoice where they had Pay balance by credit card selected but the authorization had expired. Clicked Fix and unchecked the Pay bal. by cc. NOW I get the sales journal... WHY couldn't it tell me there was an unauthorized invoice or something????

Sounds like it ""Moosehead"" time in Minnesota..........

Yay! The invoices have posted and they are happy that I am no longer sending broadcast messages asking people to GET OUT OF SALES ORDER! (I didn't really yell at them.....) Thanks all, for your thoughts. @DianeRuth it was your suggestion to scroll through the invoices when I found the expired authorization with the negative invoice balance. (May have to talk about how to handle credit cards, etc. with them at some point.)

Let's see, what WAS I planning on doing today before this phone call???

Buy an emergency case of Moosehead???

LOL just a normal day !

The most frustrating thing about this one was that for EVERY invoice, the customer was on credit hold so as I'm scrolling through, the credit warnings popped up, then the ""credit card already processed"" message, then - for most - there was just the odd memo. So a lot of clicking....

This actually brings up an interesting (to me at least) question. When do we report the problem to Sage? Or do we just fix it and keep the knowledge within the group. Could Sage have resolved this in less time than Therese and the SC KB? This was a very weird issue but how many times in the Sage universe has it occured? An error message should have popped up. Even more to the point, even if Therese takes the time to report the bug, what are the chances of it getting fixed, in a timely manner or at all. I understand (but don't agree) that a flaw in logic from 20 years ago will NOT be fixed but this is a module enhancement that is relatively new and one that Sage is relying on a great deal of recurring revenues for. It SHOULD be fixed. Sad that Sages reluctance to fix issues prevents new ones from being reported to them.

I think we should report it, otherwise there's zero chance of a fix from Sage. Additionally, we should note the issue on 90 Minds, but not disclose the solution. Customers can call a 90 Minds member for assistance.

Just posted it on LinkedIn. http://www.linkedin.com/groupItem?view=&gid=3253582&type=member&item=251656635&qid=32eb5c3e-254d-439f-aa1a-e6efaab210fe&trk=group_most_recent_rich-0-b-ttl&goback=%2Egmr_3253582