Sage 100

 View Only

  • 1.  Vendor Code: 18

    Posted 09-16-2019 18:12
      |   view attached
    Client has Sage 2016 Premium with Application Server on one server (A), and SQL Server on another Server (B). Users access Sage workstations through a different terminal server (C). We can print just fine from bservers A & B, but the TS (server C) gets a Vendor Code 18 error. 

    we have updated the SQL Setting utility, change the MAS_User and MAS_Reports passwords and tested the utility more times than I can count, everything validates fine. I have checked permissions to the local workstation, the MAS90 folder and still we cannot print from JUST server C. 

    What settings can I check that I may have missed?

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------


  • 2.  RE: Vendor Code: 18

    Posted 09-16-2019 18:16
    Perhaps a DNS or firewall problem?  From server C, run an Excel query of SQL data using the same server name / instance name as used in the Sage settings...

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



  • 3.  RE: Vendor Code: 18

    Posted 09-16-2019 18:23
    Are you printing a custom report?

    https://www.sagecity.com/support_communities/sage100_erp/f/sage-100-personalization-customization-and-productivity-tools/38753/ado-error-crw-report-for-mas200-sql-4-50



    ------------------------------
    Dan Burleson
    Software Consultant
    Connex Software
    Corvallis OR
    541-224-6642
    ------------------------------

    Original Message


  • 4.  RE: Vendor Code: 18

    Posted 09-16-2019 18:24
    Client seems to think it is TLS? Why would that affect Printing?

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 5.  RE: Vendor Code: 18
    Best Answer

    Posted 09-16-2019 18:26
    Yes it would.

    If TLS 1.0 and TLS 1.1 are disabled on the SQL Server (which is a good security practice), you might need to disable it on your client machine.

    In the registry: 

    HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\ ...  \TLS1.0\Client (and Server): set DisabledByDefault = 1, Enabled = 0  \TLS1.1\Client (and Server): set DisabledByDefault = 1, Enabled = 0

    You probably have to restart your machine for the settings to take effect.




    ------Original Message------

    Client seems to think it is TLS? Why would that affect Printing?

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------


  • 6.  RE: Vendor Code: 18

    Posted 09-16-2019 18:35
    That did it! RESOLVED by one Nicholas Webb! thank you!!!

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 7.  RE: Vendor Code: 18

    Posted 09-16-2019 18:38



    ------Original Message------

    That did it! RESOLVED by one Nicholas Webb! thank you!!!

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------


Related Content