Sage 100

Shannon,

Do you have a backup of the MAS90 folder and the MAS_System database from before the migration?  If so you should be able to restore those and try again.

Phil

Echo @Phil McIntosh for anyone reading this in the future - it is important on premium upgrades to take backups of the SQL databases at various points along the upgrade.

I've found that if MAS_SYSTEM gets damaged, you have few workarounds should MAS_SYSTEM become unreadable.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Echo @Phil McIntosh for anyone reading this in the future - it is important on premium upgrades to take backups of the SQL databases at various points along the upgrade.

I've found that if MAS_SYSTEM gets damaged, you have few workarounds should MAS_SYSTEM become unreadable.

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Echo @Phil McIntosh for anyone reading this in the future - it is important on premium upgrades to take backups of the SQL databases at various points along the upgrade.

I've found that if MAS_SYSTEM gets damaged, you have few workarounds should MAS_SYSTEM become unreadable.

@Rebekah Veuger  I just ran into the same issue.  I received the ALTER DATABASE error.  I copied the new migration folder and was able to get the data to migrate.  Then I received the sy_registration error when trying to enter Sage 100 v2022 premium.  I restored the MAS_SYSTEM db that I had backed up prior to trying the migration.  Works fine now.

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Echo @Phil McIntosh for anyone reading this in the future - it is important on premium upgrades to take backups of the SQL databases at various points along the upgrade.

I've found that if MAS_SYSTEM gets damaged, you have few workarounds should MAS_SYSTEM become unreadable.

Also reinstalled the v2022 programs using the "repair" option and then also reinstalled PU2.

@Rebekah Veuger  I just ran into the same issue.  I received the ALTER DATABASE error.  I copied the new migration folder and was able to get the data to migrate.  Then I received the sy_registration error when trying to enter Sage 100 v2022 premium.  I restored the MAS_SYSTEM db that I had backed up prior to trying the migration.  Works fine now.

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Just so you know, because I just went through this as well if you have Custom Office fields, guess when they move over, yes during the migration that fails.  All your custom office stuff has to be back in place before you begin any conversions.  It gets much bigger if custom office fields exist.   But that is a book of extra steps it took to get what was needed in the new version.  You have custom office, data dictionaries, and master files that come from MAS_SYSTEM.  Not everything you need is on the MAS_SYSTEM DB itself.  There is stuff on the MAS90 side that you must have.  Then there is an import export method CM process that would be needed for custom office.  Everything must be in place correctly and then you will fool the source to make the Parallel Migration complete successfully for the first time.   It is a beast but I was able to pull it off and got everything I needed from the source to avoid a whole other crap load of stuff that it would have had to be redone had I not tricked Sage into working.  You have my number.  Call me tomorrow if you would like.  Have a great day everyone. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Also reinstalled the v2022 programs using the "repair" option and then also reinstalled PU2.

@Rebekah Veuger  I just ran into the same issue.  I received the ALTER DATABASE error.  I copied the new migration folder and was able to get the data to migrate.  Then I received the sy_registration error when trying to enter Sage 100 v2022 premium.  I restored the MAS_SYSTEM db that I had backed up prior to trying the migration.  Works fine now.

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Echo @Phil McIntosh for anyone reading this in the future - it is important on premium upgrades to take backups of the SQL databases at various points along the upgrade.

I've found that if MAS_SYSTEM gets damaged, you have few workarounds should MAS_SYSTEM become unreadable.

Thank you @Carmen Cruz .  My customer is going live on 2022 Premium tomorrow morning, so I hope any issues will shake out quickly.  Thanks for offering your assistance if we need it!

Just so you know, because I just went through this as well if you have Custom Office fields, guess when they move over, yes during the migration that fails.  All your custom office stuff has to be back in place before you begin any conversions.  It gets much bigger if custom office fields exist.   But that is a book of extra steps it took to get what was needed in the new version.  You have custom office, data dictionaries, and master files that come from MAS_SYSTEM.  Not everything you need is on the MAS_SYSTEM DB itself.  There is stuff on the MAS90 side that you must have.  Then there is an import export method CM process that would be needed for custom office.  Everything must be in place correctly and then you will fool the source to make the Parallel Migration complete successfully for the first time.   It is a beast but I was able to pull it off and got everything I needed from the source to avoid a whole other crap load of stuff that it would have had to be redone had I not tricked Sage into working.  You have my number.  Call me tomorrow if you would like.  Have a great day everyone. 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Also reinstalled the v2022 programs using the "repair" option and then also reinstalled PU2.

@Rebekah Veuger  I just ran into the same issue.  I received the ALTER DATABASE error.  I copied the new migration folder and was able to get the data to migrate.  Then I received the sy_registration error when trying to enter Sage 100 v2022 premium.  I restored the MAS_SYSTEM db that I had backed up prior to trying the migration.  Works fine now.

Hi Shannon, 

I am wondering how you eventually got past the SY_registration issue?   I am working on a 2019 Premium with PM to 2022 Premium with PM.  Using the replacement Migration folder from Sage, I am able to get past that ALTER DB error and the migration seems to move through MAS_SYSTEM and the three company DB moves.  Then when it starts to copy the system files, it pops and error (XCopyFile returned the following error - "The system cannot find the file specified." I click OK and then get "Paperless Office merge file failed to copy.  Migration will now exit."  Migration exits and I am left in limbo. If I try to start up Sage, I get the SY_Registration errors.    TIA  for any insight.

Sad to say you are looking at having to reinstall the entire program.  Remember to create a backup of the new MAS90 directory and the MAS_SYSTEM DB in SQL.  Then move forward with migration.  Sorry to say you will have to start over.  There is no recovery once that core is damaged.

 

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106