x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 108 subscribers
  • Views 4567 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
NetworkAdmin

MAS 200 Parallel Migration Fails !

SUGGESTED
Posted By

I am planning to move MAS 200 to a new server.  A few weeks ago, as a test, I installed MAS 200 on the new server using the original Sage CD..  I then did a parallel migration, and had no problems.  I could log in to MAS, work in the various modules, etc.

Our financial people wanted me to do another migration to the new server so that they had a fresh set of company files on the new server, for further acceptance testing.  I completely uninstalled MAS 200 from the new server, reinstalled it, and tried to do another parallel migration from the old server.

The migration wizard is failing with the following error: "FAILED TO CREATE SOURCE SY_MIGRATION OBJECT"..  The last few lines in the migration.log file are...

     Source PVX script object created

     Source PVX init passed ok

     Source SY_Migration object created

     The server threw an exception

I have plenty of free disk space on the server, I've checked folder permissions, I've reinstalled MAS 200 and tried the migration again, but it fails in exactly the same fashion.  Any suggestions as to what the problem is ?


Thank you !

  • 0
    SUGGESTED

    I have seen this when installing 4.5.4.  Make sure to download and install on the server the latest service pack of the version you installed and then try the migration again.

  • 0

    Try running workstation setup. What version of MAS are you installing?

  • 0
    SUGGESTED

    @ VanMan

    @ G Ulrich

    Thank you for your input.  I think I stumbled across the solution...

    BTW, it's MAS 200 v4.40 (yes, I know that 4.40 is two versions old)

    Prior to running the migration, I copied the entire Sage Software folder from the root of our old server, to a folder with a descriptive name that I created on the new server.  The path to the SOURCE mas90 folder on the new server which I was migrating FROM was something like...

    C:\SAGE SOFTWARE\MAS440\FOLDERS COPIED FROM OLD SERVER ON 8-20-2013 @

    12:30 PM\MAS440\MAS90\

    I'm guessing that although it didn't complain about the path name I provided, the parallel migration wizard was choking on this path name (which probably isn't a valid UNC pathname ???), because when I renamed one folder in the path so that the path looked like this...

    C:\SAGE SOFTWARE\MAS440\OLDSERVER-8-20-2013\MAS440\MAS90\

    ...the migration ran successfully.

    My best guess is that when I had done my first successful migration a few weeks back, the path name to the source mas90 folder was simpler, and didn't offend the migration wizard.


    I will be rerunning the migration wizard with a fresh copy of the source mas90 folder later this week.  If I can reproduce a successful migration at that time, I'll feel confident that I solved my problem.

*Community Hub is the new name for Sage City