Sage 100

 View Only

  • 1.  Error when converting data to Sage 100c Premium (SQL)

    Posted 03-14-2019 09:03
    Migrated data from 2016 Standard to 2018 Premium. Now when converting company data, the error File "[sql]DB2016;;User=MAS_User;" not found pops up and the conversion dies. Ideas anyone?

    What has been done.

    1. Tested Sage 100 Premium 2018 SQL Setting (MAS_Reports and MAS_User). Both accounts tested successfully.
    2. Can access ABX company and run reports, enter transactions for this company.
    3. Upgrading to Payroll 2.19 from legacy. Conversion does prompt for Tax Groups and Tax profiles. Dies after clicking Finish on the payroll conversion wizard.
    4. Can't find anything on Sage support, Sage City or 90 Minds.


    ------------------------------
    Myron Stevenson
    Consultant
    Clearis Consulting, Inc
    Duluth, MN
    218-525-6720
    ------------------------------


  • 2.  RE: Error when converting data to Sage 100c Premium (SQL)

    Posted 03-14-2019 09:19
    Migrate using the SA login for SQL authentication, not Windows / integrated.

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



  • 3.  RE: Error when converting data to Sage 100c Premium (SQL)

    Posted 03-14-2019 09:23
    Thank was done. We always use the sa credentials to migrate. Can you migrate a second time without reinstalling? I checked the SQL Server and no compansy databases were created. Are these created in the migration of the conversion?

    ------------------------------
    Myron Stevenson
    Consultant
    Clearis Consulting, Inc
    Duluth, MN
    218-525-6720
    ------------------------------

    Original Message


  • 4.  RE: Error when converting data to Sage 100c Premium (SQL)

    Posted 03-14-2019 09:29
    I believe the company SQL databases are created during company conversion. 
    I always create a backup of MAS90 and MAS_System before migrating a first time, to avoid reinstalling (in case something goes wrong during the migration). Since it seems like your migration wizard didn't finish nicely, I'd err on the side of caution and reinstall.

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

    Original Message


Related Content