Sage 100

 View Only

  • 1.  Sage 100 ADV to v2025 SQL

    Posted 10-04-2025 19:16
      |   view attached

    Having some issues with getting v2025 Premium functioning.  For the record, I know nothing about SQL.  I outsourced the migration to a reseller.  The first migration was fine.  I was able to access Sage post-migration, and users were able to reach a level of comfort (from the SAGE Server).  This weekend is go live.  The reseller performed the migration and the Crystal Reports migration.  Handed the project back to me.  I installed the client on the RDS and now encounter this message when launching Sage.

    From the Sage 100 server, I get this message when running a menu item.  Company maintenance shows the data is at 7.4

    I contacted the reseller.  He admitted he didn't run/test anything in Sage, just that the SQL data converted "fine".

    Need some direction as to what to look for and resolve.

    Thanks in advance.

    Jeff



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

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


  • 2.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-04-2025 22:02

    The SQL message happened to me not too long ago. After some digging around, we found that the SQL server was a Trial Version and the Trial had expired. Customer had to purchase SQL before we could get it to work again. You might want to backdate the System Date on the server to see if that is the issue. 

    As for the GL error, it must be related. It's not seeing the GL data in SQL so it's saying you must activate GL before you do anything else. I bet that if you proceeded to activate, it would throw some other error at you, or maybe the same SQL is not enabled error. 

    It might be something else in your case, but that was my experience with the SQL is not enabled error



    ------------------------------
    Kenny Daniel
    TechnoClarity, Inc.
    ------------------------------



  • 3.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-05-2025 02:21

    I've seen this and in my case it was either the service permission or SQL user mas_user permission.  See the article in this link.

    https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=223924250030176&page=1&position=1&q=sql%20not%20enabled%20



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------



  • 4.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-05-2025 12:10

    Did you get this resolved? I've had these a few times and it could be a few things. Usually its SQL permissions not synced. 



    ------------------------------
    Tina Leonard
    RKL eSolutions, LLC
    AZ
    ------------------------------



  • 5.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-05-2025 14:34

    Thanks to all who responded.

    Working with another reseller, it appears that the most important company conversion was not processed completely.  Only the GL tables appear in SQL.

    Extremely frustrating.



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

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

    Original Message


  • 6.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-05-2025 14:43

    Is it important that all of the tables migrate to the new version?



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 7.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-05-2025 14:59

    look at the conversion log to see if there is any indication of why the data didn't migrate.



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 8.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-06-2025 09:37

    Final recap,

    The RDS "SQL is not enabled" error was resolved by changing the sota.ini server line from the server name to the server IP address.

    I do not know why the main company's MAS_xxx folder did not migrate properly.  We re-migrated that company last night.  It finished early AM.  Client is now verifying their data.  Life is much better this AM

    This can be moved out of the urgent support forum



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

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

    Original Message


  • 9.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-06-2025 09:39

    That would be a DNS resolution issue.  Pass that one on to IT.



    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Chauffeur, Chef, and Personal Assistant to Sprinkles
    ------------------------------

    Original Message


  • 10.  RE: Sage 100 ADV to v2025 SQL

    Posted 10-06-2025 10:27

    They probably missed the "migrate companies already in the target system" checkbox option in the migration wizard...

    A migration from Providex to SQL doesn't create the the company SQL databases during the migration.  That happens during the company data conversion.

    As someone mentioned, check the SQL conversion log (txt file) to ensure nothing was thrown out during data translation.  It's normal to see numeric rounding errors.  I've seen text data truncation (with SQL enforcing field sizes much better than Providex).



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

    Original Message


Related Content