MAS200 4.5 - Update Interrupted and 107 errors

Hey Everyone,

We recently upgraded from 4.3 to 4.5.  Since upgrading, we have experienced interrupted update errors and "107 Keyed file error (Wrong key block addr)" errors.  From what I understand, interrupted updates can cause data corruption, which is what may be leading us to the 107 errors.  Is that right?  We have been able to correct these issues on a case by case basis by working with Sage support, but I wondering why we are seeing this issue in the first place.  We never experienced this issue in 4.3.

I have heard users say that updating and running reports is considerably slower in 4.5, but I cannot see why.  From what I understand, the errors above are generally caused by system crashes or network issues.  Maybe we didn't see these issues before because the processing time was so much faster in 4.3 and therefore minimized the chances of a network issue affecting processing.  If we go that route, why is 4.5 so much slower?

Our server is on a virtual Windows 2008 setup with 4 gb of ram and an Intel Xeon 2.9GHz processor.  We probably have anywhere from 7-10 users on the system during our busiest hours.  We looked at CPU utilization and we average below 10 percent usage with no considerable spikes.  There are no issues with our network connection and none of the users who have had this interrupted update issue have reproted MAS200 or their PC crashing.  All users are on Windows 7 with 4-8gb of RAM and 8 cores.  I have been running ping tests from different client machines to and from the server, experiencing no packet loss and response times are always less than 1ms.

Does anyone have any ideas of what might be causing our issue.  The first thing that our reseller asked is what kind of network cards we are using on the client machines.  He said that realtek cards have been known to cause this kind of an issue.  All of our users are using Intel cards, so this is out. 

  • 0

    Also, we are on 4.50.6.0.  We purchased some add-ons that we have not implemented in our production environment yet.  Our reseller recommended that we use PU6 instead of 7 since 7 is not tested with the add-ons yet.

  • 0

    You had mentioned add-ons. Did you have them in your previous version?  Also were these imported orders?

  • 0 in reply to BigLouie

    Thanks for the reply.  

    The add-ons were not in our previous version, and we are currently not importing orders.  Using VI to eliminate some of the manual entry is definitely on my list fo things to do though.  

    I only mentioned the add-ons in the case that someone might question why we upgraded to 4.5 instead of the latest version or why we are not on the latest service pack.  Both are to make sure that the add-ons are compatible.  We are trying to get this figured out before we potentially gum up the process more by implementing these add-ons.

  • 0 in reply to willHyland

    You need to rebuild your key files.  I had asked about imports because short keys are some times caused by bad imports and I asked about add-ons because sometimes add ones will change the key and if you upgrade without them you get this. That being said, something you are doing is causing a short key to be created when entering data. Something is definately wrong, I would work with Sage tech support and your reseller to go through all steps of the upgrade and see if some thing was skipped.

  • 0 in reply to BigLouie

    Thanks, Louie.  We are working with Sage support now in an attempt to identify the issue.  Luckily, we have not seen a 107 error in about 3 weeks after rebuilding the affected key files.