The Ultimate MAS90/200 Catch-22 - Can we get answer please

Posted By BigLouie over 13 years ago

Ok what's it going to be. Sage has issued conflicting instructions on PU1.

To install the Product Update, note the following:

We highly recommend that you back up your system before installing any updates or version upgrades. Otherwise, data may be lost if the update fails.
Install this Product Update from the same computer that was used to install Sage MAS 90 or 200.
Apply this Product Update before data conversion.
Note: As mentioned in the Release Notes, this Product Update fixes the issue of General Ledger account balances not being recalculated during conversion from Version 3.71 directly to 4.30. However, if you apply this Product Update after converting from version 3.71, you must manually run the Recalculate Account Balances utility (on the Utilities menu in General Ledger). Converting the data again is not necessary.

Panel Processing Error, Error #42: Subscript out of range/Invalid subscript. An error has occurred while processing the screen in ...\MAS90\SY\ SY_CompanyConver sion.M4L[ 7135] and then error 42 _winproc 15540 when converting data to 4.40.0.1

Entry Type: Program Issue

Product:
Sage MAS 90 ERP
Sage MAS 200 ERP

Application: Library Master

Version Reported: 4.40.0.1

Status:

For current information on this issue, please click the Engineering Status link above. To record the occurrence of this issue, respond Yes to the question, "Did this answer help you?"

Subject:

Steps to Duplicate:

In [TST] company:

1. Install a new 4.40.0.1 of MAS90

2. Use Parallel migration to migrate customer 3.71 TST data that is in \\tradewind\ Public\DRC\ MAS 90\SWATT\Attach\ Tools\4500223

3. Log in to 4.40.0.1 and convert the data.

Notice that you would receive the error after the conversion finishes and you click on Ok.

Expected Behavior:

The error should not happen,

Possible Workaround:

Migrate to 4.40.0.0 and convert data and then install PU1

thebottomline over 13 years ago

BL,

I am shocked, simply shocked that you are wondering!!!!!

But what a coincidence that I ran into this VERY same issue yesterday doing a migration from v3.71 to v4.4. Yes, I do have one or two 3.71 migrations left to do.

All I can surmise is that the Web site needs to be updated (or a revised PU be released - 1.C?). After spending considerable time converting the 3.71 data, the process blew up in my face. Thankfully, Sage has started posting issues that have not been verified by engineering or else the day would have been a complete waste! I renamed the MAS 90 folder, reinstalled from the CD. Migrated and converted the data, then installed the PU. 2nd time was the charm!

Now I am on to helping a client who installed the v4.30.18 SU earlier in the month (they have the SO module) who is dead in the water due to trying to close their AR for March. And the AR hotfix is not working.

Never a dull moment in upgrade land!!!!!!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
BigLouie over 13 years ago

It's always something.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
mas90guru over 13 years ago

I received the exact same error on a 3.7 to 4.4 test migration.

I find this wholly unacceptable.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
TheOtherGuy over 13 years ago

Hey Louis,

The suggestion to install the Product Update first is a time saving measure not a requirement.

Product Update 1 goes through it's own conversion and we didn't want people sitting through the conversion process multiple times if it was not needed.

This issue only occurs in 3.71 migration / conversions and Sage was unaware of it when the suggestion to convert after the Product Update installation was posted.

The update page will be changed to reflect this issue.

Thanks for posting and letting other users and us know.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Sage 100

The Ultimate MAS90/200 Catch-22 - Can we get answer please

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING