Sage 100

I have a MAS customer (MAS 200 4.4.0.6) who a few times a week receives the ""A customer number was found that was not on file"" on the Sales Journal Error Log report during SO Daily Sales updates. It is fairly easy to fix by just going back into the batch and deleting the record that is only an invoice (not other data in the entry other than the invoice number). They are able to continue to post after doing that. However, they are frustrated because they have to continue doing it. We are trying to figure out what is causing the issue. Has anyone see that or know why it happens? In other words how do I get a blank invoice record in SO Invoice Data Entry? Thanks

I have (as I'm sure others do) people putting heavy data entry into 4.4 and if they're receiving this they're not calling. I usually tell people that fixing the issue is going to be trial and error -- reinitialize the data files (usually rename them / create from scratch). Sometimes I get lucky and that works. If it doesn't I start trying to narrow down people on the network who may receive (but not report) errors in their daily MAS processing.

Thanks Wayne, do you mean reinitialize the data entry files for SO Invoice Entry? I am always hesitant to do that in the new framework as I am not sure what other hooks it may break. I have already tried to see if is a procedural issue that someone is doing but I will interrogate their warehouse users to see if anyone is closing out of an error and not reporting it (time to put bad cop hat on and get out bright light). Thanks for your suggestion.

Look for error 41 in the Activity Log. Had a client call a couple weeks ago, where some shipments were generating errors in Shipping Data Entry, and created a stray invoice in Invoice Data Entry. Ended up installing program fix. Wish I could provide more info, but can't access their server now.

We have also seen it where it was isolated to a single workstation that was causing data corruption. The last instance was a homemade patch cable between the wall and workstation. Convinced the client to replace all of the patch cables on the network. About 50....

Thanks @MarkKotyla I will check that out. These transactions are originating from Shipping Data Entry so you may be onto something. Is this the program fix you were referring to? ======================= Date: 1/26/2012 Product Line: MAS 90 and MAS 200 Application: Sales Order Application Level: 4.40.0.8 Number: SO4082-T Symptom Error 41 SO_InvoiceDetail_bus.pvc 501 occurs in Shipping Data Entry when a fractional number is entered in the Shipped Quantity field when the Allow Changes to Backordered Quantity on lines is selected in Shipper ID Maintenance. Resolution The following program version will correct the problem. SO_InvoiceDetail_bus.pvc 511 ==========================

@BrianBuck Yes, that's it.

Thanks @ScottHickman did you see errors in the System Activity Log related to that to discover the data corruption?

No - this was happening at order entry. All of the orders causing the problems were from one sales person. I went out to check the workstation and it was extremely slow and they were gettng other errors such as Email/MS Exchange. We thought it was cabling oriented and started down that path. I am not sure if I saw it in the event logs or I just saw the bad cable as we can recognize the homemade ones. I make the clients replace them as soon as I see them.

Thanks Scott. Very helpful information. I will look for those homemade cables...that is a good first, easy check.

Brian - it would be the whole network cabling food chain. Ie., look at the cables to switch. Make sure there are no switches daisy chained. Make sure there at least 100Mbs swtiches, etc. We also had an issue that was caused by an auto negotiate between the workstation and the server. We had to force the switch to 100mb as the NIC in the workstation would not support 1GB, but the switch would not step down by default.

Back in the day, I had a Peachtree user contact me for a system upgrade. They had contacted Sage and was urged to upgrade to MAS due to data corruption issues. Too many users in Peachtree. They backed off when they heard the sticker price. A year later, they called again. Same problem. Same sticker shock. This time I recommended that I send out my HW guru to take a look at their cabling. EVERYTHING was wired incorrectly! After they fixed that problem, I never heard from them again........