Moving Premium to a new server (not just the database, the service too) without migration

v2018.3

Customer is changing hosting providers and their current data center is unwilling to provide a server image, so running a proper migration to the new server is not possible.

I've installed the same version on the new server (including enhancements) so the program files are where they should be (in Windows), then swapped in a copy of MAS90, restored the databases (MAS_System and MAS_###), fixed database permissions, SQL Server link... and can log in, but most things I try are giving me errors. 

Customer Maintenance.

Customer Listing.

Yet I can get into the Paperless Customer Viewer / see previous forms listed, and Bank Code Maintenance opens OK, so the data is accessible... it just seems the programs are broken.

I'm going to try and run repair / reinstall PU / PR / enhancements to see if that helps.  Has anyone attempted this kind of server move before?  Any tips?

  • Probably no help, but when I move our Sage 100 providex stuff, I copy a MAS90 folder backup to a separate folder on the server; then point to

    it during migration. That works well. After that some read/write issues need to be set for the client install folders.

    Possible .net updates needed??

    Geez man good luck

  • in reply to sevendogzero

    That works great for Advanced / Standard as a source, but Premium data (system and company) is in SQL... so a folder copy doesn't have everything.

    I found some instructions for a "Merge" method, and am trying that next.  (The repair attempt failed with a nonsense error).

  • in reply to Kevin M

    Hey Kevin,

    You probably already know all this, but in case it helps I recall one of the big issues when moving databases is the DB owner needs to be MAS_User. There was a pretty good article somewhere, let's see...

    Just checked, it's still there: KB 85470 - "How to move Sage 100 Premium SQL databases to new SQL Server or Named Instance on existing SQL Server"

    From a Windows perspective, remember that the ..\MAS90\Uninstall Information folder keeps track of server info so if you replace the MAS90 directory you need to put back the "new" Uninstall Information folder (good old KB 18040).

    Otherwise, I'm sure you already found this, in the "Sage 100 2015 Release Notes":
    Errors XX BC_UNATTENDEDIMPORT_UI or Error 90 MDENH line 0120 in Unattended Bar Code Transaction Import no longer occur. DE 103327

  • in reply to rclowe

    Thanks for the thoughts rclowe. Tracking down the individual errors would be too much work, but I appreciate the link.

    I know all about the database permissions (and it's mentioned in the Merge method instructions I'm working through).  I haven't spent too much time testing afterwards but I've gotten much further, and the biggest issue I've encountered is the data dictionary (custom office UDF / UDT) needs to be updated manually (Customizer Export / Import).

    (I can't post details of the Merge method, because it came to me through 90Minds and that group has strict rules about sharing... but I will say it originates from an ex-Sage-employee, so I suspect Sage support knows what I'm referring to).

  • in reply to Kevin M

    Hi Kevin,

    I figured it was old news for you, sorry I couldn't be more help.

    Say "hi" to Alnoor and all my old 90 Minds buddies Nerd

  • in reply to rclowe

    No worries.  Attempts to help are always appreciated.  Slight smile