Sage 100

I need assistance with upgrading MAS 90 v3.23 to v3.31. I have rebuilt all files in v3.23, installed v3.31 on top and when I run the data conversion for the AR module I get the following error: 47 AR_17002.SOA Channel 1 Key: "" B"" (file attached) AR_17 does not exist in v3.23 and is being created when I start the conversion for 3.31. I am stuck and can not continue at this point. My understanding is important to perform a step upgrade from v3.23 to v3.31 to 3.51 to 3.71 then to v2014 due to sales tax changes. If anyone has ideas on how to get past this error I would appreciate it!

Amy, The conversion path that I have when I did my 3.21 upgrade is 3.2x steps to 3.51 -> 3.71->4.3 or higher. If stuck in error - I would try to manually create (copy in ) the file the program is looking for. AR_17. There is obviously nothing in there to rebuild but if the file copy doesn't resolve then I rebuild sort files for this error type. Good luck.

The record that the screen shot is referring to looks like a bad record. See what the other records look like. i do not see why you cannot go to 3.71 directly.

Thanks! I just tried to upgrade from v3.23 to v3.51 and received the same error. I will try to going straight to v3.71. Will that affect AR, IM or SO in any way?

Of course, rebuild the AR files in the source system first in case of bad records. AR Invoice History header & line files are crucial.

I don't have 3.23 available, but If you click debug, get a screen and enter: ? ARN$ it should show you the invoice with the error.

it is likely a bad records that the rebuild isnt fixing. I would look at the ar_17 file and I bet there are some short records that will need to be manually deleted.

If it's READING tax summary, then debug: ? AR_17$ would show you the invoice. Earlier versions read ARN and created AR_17 recs.

Thanks All - the bad record was in ARN. I have deleted it and the data conversion has been running for 2 1/1 hours. I jumped to v3.51 so I will have to do this again to upgrade to v3.71, however it should go much smoother. I appreciate all the feedback!

FYI, in the cases I brought data from the 3.21 and 3.41 there was new data corruption found at each step point. So don't be too surprised if that happens in your case as well. But I hope you get lucky and it's smooth going from here on out. Good luck.