Skip to content

x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 389 views
  • Users 0 members are here
Browse Forums
Announcements
328
topics
390
replies
Business Object Interface
1k
topics
8k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
13k
replies
Distribution, Manufacturing, and Applications
2k
topics
8k
replies
General Discussion
1k
topics
4k
replies
Partner Cloud
59
topics
118
replies
Payroll, Time Tracking, and Job Cost
838
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Sage CRM for Sage 100
171
topics
372
replies
Technical and Installation
2k
topics
10k
replies
Year-end Forum
95
topics
262
replies
sevendogzero

Sage upgrade - Error help

Posted By

We are running a migration test from Sage 2014 to Sage 100 2023.

We opened the new version of Sage and started the data conversion step.

We have 5 companies. Four of the companies converted with no problems.

One company had the below error display. Can anyone shed light on the message?

The following conversion returned failure SNJ:06.20.00.00:DATA:AR_CustomerShipToTaxExemptions:000000:000
Failed to create table AR_CustomerShipToTaxExemptions: Create Table failed for C:
Sage
Sage 100
MAS90
MAS_SNJ
ARSNJ
AR_CustomerShipToTaxExemptions
PHYSICAL UPDATE ABORT: AR_CustomerShipToTaxExemptions - 34888 of 34887 records copied with 0 duplicate keys.
View the Activity Log to locate a specific conversion log.

Is this a corrupted record?

If we re-run the conversion, the error does not repeat itself.

I have read that some of the 4 updates can correct this error.

Any feedback appreciated.

  • 0

    Most "PHYSICAL UPDATE ABORT" errors that occur during data conversion are resolved by rebuilding the file referenced in the error message in the Source (previous) installation. 

    1. Make note of the file referenced in the error message (i,e. AR_CustomerShipToTaxExemptions)
    2. Log into the Source installation
      NOTE: make sure you have a backup of the file
    3. Open Library Master, Utilites, Rebuild Key Files. Click 'OK' to warning message.
    4. Select the Company Code and Module
    5. Select the file (i.e. AR_CustomerShipToTaxExemptions) referenced in the error in the list
    6. Click Proceed.
    7. Exit Source installation
    8. Rename the file in the Target (New) installation (i.e. ...mas90\mas_xxx\arxxx\AR_CustomerShipToTaxExemptions.old. where xxx= company code)
    9. Copy the file (AR_CustomerShipToTaxExemptions.M4T) from the Source installation to your Target installation.  
    10. Log into Target installation and rerun the conversion

  • 0 in reply to NateSage100

    Very clear reply. Thanks. I will give that a shot. Love the time saving trick as well.

  • 0

    It is possible AR_CustomerShipToTaxExemptions.M4T is corrupt in Sage 100 2014. I suggest rebuilding AR_CustomerShipToTaxExemptions.M4T and try again. Also can verify the table opens in DFDM without getting an error.

  • 0 in reply to NateSage100

    Went back to Sage 2014. Rebuilt the table. The rebuild found a record with an illegal character.

    Zipped up the Sage 2014 MAS90 folder.

    Moved the zip file to the new server. Unzipped the Sage 2014 data into a local MAS90 folder, separate from the Sage 2023 MAS90

    folder.

    Ran migration on the Sage 2023 install and the migration brought all 5 companies into Sage 2023.

    Ran the conversion, and NO errors during conversion.

    So, we are good to go.

    Thanks for the responses.

*Community Hub is the new name for Sage City