Sage 100

 View Only
  • 1.  Summit Hosting migrating providex to SQL

    Posted 10-16-2025 17:54

    We have a handful of clients on Summit Hosting.  This is the first one with SQL.

    We are migrating from v2022 Standard/Providex to v2025 SQL.

    Installing base Sage 2025 with PU1 with Scanforce and DSD multicurrency works without issue.

    The challenge is when we migrate.  After entering the SQL server (same machine that Sage is installed on) and entering the SA password, immediately we get a message that it can't find MAS_System database in SQL  The command that it's typing works without issue when we try it manually in SQL. I've attached the first screen shot of the error.  The next two error messages all stem from this.  This is very early on in the migration wizard ... we don't get a chance to pick the source system or the companies to migrate.

    Sage support spent a couple of hours on this.  I've spent about 3 before they got involved.  

    So, my question is, has anyone migrated Providex to SQL in Summit Hosting environment yet?  If so, did you have any issues.

    Thanks in advance, Robert



    ------------------------------
    Robert White
    Munjal White Consulting Corp
    Toronto ON
    ------------------------------


  • 2.  RE: Summit Hosting migrating providex to SQL

    Posted 10-16-2025 18:16

    We did a similar migration two weeks ago.  Client was on Azure.  It was nip and tuck for a bit because the primary company's data did not migrate initially,  It did finally and we are able to go live Monday AM.  Only complaint is GL upload processing speed (normally import 30K lines into GL every morning.  Do you think it is a Summit issue or a SQL issue?  Could sharing the server be the root cause?  Permissions?  Just thoughts from the recent experience.  I know less than Sgt Shultz did back in the day,



    ------------------------------
    Jeff Schwenk
    Owner
    Bottomline Software, Inc.
    Waynesboro VA
    (540) 221-4444

    Improving bottom lines for over 25 years!
    ------------------------------



  • 3.  RE: Summit Hosting migrating providex to SQL

    Posted 10-16-2025 19:04

    Current theory: the generated hard password (provided by Summit) included at least one super weird character ("`"), and when I created a new SQL login (with sysadmin permission) without the funky character, I was able to get past the migration wizard's error.

    *fingers crossed that was it*



    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------