Sage 100

Does anyone do this anymore?  I did it quite frequently back in the day but when Sage started using server specific keys, I stopped.  Is it still possible to do?

------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

I think by server-specific keys you mean the encryption key that is in later versions of Sage 100 and can cause issues if you try to copy in a MAS_XXX that was not originally migrated to the test site?

The way I do this: 
1. Migrate to new Sage 100
2. Setup/convert data in the new Sage 100
3. Upon final go-live copy/paste MAS_XXX from old ( which is the copy I migrated from ) to new

Where I think you can run into trouble is if you try to copy/paste a MAS_XXX from a system that was not the one you migrated to the new Sage 100
 In those cases, I think people get around it by manually copy/paste the encryption key into SY_Company however your mileage may vary on whether this works with payroll. 

I don't ever try to copy/paste a MAS_XXX into a new Sage 100 if that MAS_XX wasn't part of the original migration so I can't tell you for sure what workarounds may or may not exist to make it work ( aside from thinking copying the encryption key might ).


------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

Thanks.  CPA has "Sage".  Wants me to send him the pertinent MAS_XXX folders so they can do some PR tax credit analysis.  I think they are confusing Sage 100 with Sage 50.  Waiting for a screen shot of their version of "Sage".  I haven't tried this since the early (pre encryption key) v4.x days

------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 10-06-2021 10:18
From: Wayne Schulz
Subject: Moving MAS_XXX folders to different Sage 100 server install

I think by server-specific keys you mean the encryption key that is in later versions of Sage 100 and can cause issues if you try to copy in a MAS_XXX that was not originally migrated to the test site?

The way I do this:
1. Migrate to new Sage 100
2. Setup/convert data in the new Sage 100
3. Upon final go-live copy/paste MAS_XXX from old ( which is the copy I migrated from ) to new

Where I think you can run into trouble is if you try to copy/paste a MAS_XXX from a system that was not the one you migrated to the new Sage 100
 In those cases, I think people get around it by manually copy/paste the encryption key into SY_Company however your mileage may vary on whether this works with payroll.

I don't ever try to copy/paste a MAS_XXX into a new Sage 100 if that MAS_XX wasn't part of the original migration so I can't tell you for sure what workarounds may or may not exist to make it work ( aside from thinking copying the encryption key might ).


------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990
------------------------------

As suspected, CPA was in a state of "Sage" confusion.  Their "Sage" was 50.........

------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 10-06-2021 10:52
From: Jeff Schwenk
Subject: Moving MAS_XXX folders to different Sage 100 server install

Thanks.  CPA has "Sage".  Wants me to send him the pertinent MAS_XXX folders so they can do some PR tax credit analysis.  I think they are confusing Sage 100 with Sage 50.  Waiting for a screen shot of their version of "Sage".  I haven't tried this since the early (pre encryption key) v4.x days

------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 10-06-2021 10:18
From: Wayne Schulz
Subject: Moving MAS_XXX folders to different Sage 100 server install

I think by server-specific keys you mean the encryption key that is in later versions of Sage 100 and can cause issues if you try to copy in a MAS_XXX that was not originally migrated to the test site?

The way I do this:
1. Migrate to new Sage 100
2. Setup/convert data in the new Sage 100
3. Upon final go-live copy/paste MAS_XXX from old ( which is the copy I migrated from ) to new

Where I think you can run into trouble is if you try to copy/paste a MAS_XXX from a system that was not the one you migrated to the new Sage 100
 In those cases, I think people get around it by manually copy/paste the encryption key into SY_Company however your mileage may vary on whether this works with payroll.

I don't ever try to copy/paste a MAS_XXX into a new Sage 100 if that MAS_XX wasn't part of the original migration so I can't tell you for sure what workarounds may or may not exist to make it work ( aside from thinking copying the encryption key might ).


------------------------------
Wayne Schulz
Schulz Consulting
860-516-8990