Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Error: "SQL is not enabled" when opening Sage 100 Premium with TLS 1.0 and 1.1 disabled on SQL Server

  • 1.  Error: "SQL is not enabled" when opening Sage 100 Premium with TLS 1.0 and 1.1 disabled on SQL Server

    Posted 09-28-2022 09:47
    Ran into this yesterday on a Sage 100 2020 Premium where the IT had done server maintenance and disabled TLS 1.0 and 1.1 ( which seems to be  a good solid best practice )

    Yet this makes it so that suddenly the Sage users are in a "system down" status as they receive "SQL is not enabled" upon attempting to login




    I note in this KB - Error: "SQL is not enabled" when opening Sage 100 Premium with TLS 1.0 and 1.1 disabled on SQL Server


    Cause

    <content>
    • TLS 1.0 and 1.1 are disabled on SQL Server
    </content>

    Resolution

    <content>
    • Sage Engineering is currently reviewing this issue

    Possible Workaround

    1. Verify Micrososft SQL Native 11.4.7001 is installed on Server and workstation(s) (NOTE: Use Program and Features)
    2. Modify ....\MAS90\HOME\massql.settings in Notepad
    3. Change 'SQLOLEDB' to 'SQLNCLI11' under @Reporting section
    • Example: Provider=SQLNCLI11;Data Source={dsn};User ID={username};Password={password};
    </content>



    Any idea what versions of Sage 100 Premium this applies to? 

    It's difficult to explain to a customer how/why Sage 100 doesn't use TLS 1.2 and requires TLS 1.0 and 1.1 to be enabled.

    It's also worth noting that I had issue connecting to SQL from a workstation purely through ODBC so it's possible this is more of a SQL issue? 

    Have you developed any best practices on this or should we now have a checklist to manually review/modify the massql.settings?



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Moodus, CT
    ------------------------------


  • 2.  RE: Error: "SQL is not enabled" when opening Sage 100 Premium with TLS 1.0 and 1.1 disabled on SQL Server

    Posted 09-29-2022 08:04
    Sage is correct that it's a consequence of using the old SQL OLE DB driver to connect. I'm not sure which versions are affected, but I know the 2022 I did recently was already using the SQLNCL11 driver and was good to go.

    https://stackoverflow.com/questions/57412826/sql-oledb-fails-with-tls-1-2

    ------------------------------
    Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
    ------------------------------



Related Content