Sage 100

 View Only

  • 1.  Connecting to the Business Object

    Posted 01-18-2021 21:50
    Not sure where to even begin.  
    Hosted environment for both App Server and Desktop
    Upgrading a customer from Providex to 2019 Premium.  Chose premium at request of a Third Party ADP Interface from BASPAY.  
    BASPAY Engineer indicated they connect directly to the SQL Database, not via an ODBC when using Premium
    I'm able to connect from the Application Server using the following (see attached ADP Interface - the scratched out area is the instance name)
    ODBC DSN Name:  SQL:Server\Instance
    User: we used MAS_User and we also set up MAS_User in Sage
    Path:  we used the UNC path to the Home Directory.
    I can 'Check' the Home Directory and I can 'Test Connection' successfully to the SQL DB (or at least I get Green Bars which indicates Success).
    We are able to process files in the ADP Interface from the Application Server.

    Next step was to move to the Desktop 
    I tried to Test the Connection at the Desktop and I get this (see Attahced SQL Error):
    I can't process files and guessing it's due to this error

    I'm not a SQL person and I'm not a BOI person.
    BASPAY is not being forthcoming in advising and at 1 point indicated he had to go back and watch the videos.  

    So reaching out to you guys hoping there is someone that can give me details about what to do and how to get a Desktop connected.
    I am an Admin on both machines.
    I shared out the ADP folder and it's at the root of C on the Application Server.
    Go Live is this weekend!

    Thanks
    N






    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------


  • 2.  RE: Connecting to the Business Object

    Posted 01-19-2021 01:14
    This sounds like some sort of connectivity issue. Here are a few things to check.

    • Check whether you are able to access the SQL port
      Powershell: test-netconnection <servername> -port 1433
    • Make sure the SQL Browser service is running
    • Try turning off the Firewall on the server to make sure that's not a factor
    • Make sure TCP/IP is enabled in SQL Configuration
    • If this is a named instance of SQL, make sure to enter the instance name i.e: <SERVER>\<INSTANCENAME> . Sometimes <SERVER>\<INSTANCENAME>,1433 also works.
    • On the desktop, check that you're using 32bit ODBC if you're on a 64bit system: c:\windows\SysWOW64\odbcad32.exe


    ------------------------------
    George Khairallah
    CTO | gotomyerp, LLC
    george.k@gotomyerp.com | 877-888-5525
    http://gotomyerp.com/
    ------------------------------



  • 3.  RE: Connecting to the Business Object

    Posted 01-19-2021 13:00
    I remember one upgrade had multiple SQL instances running, and that put the effective Port number for the new instance into a random range (not the expected 1433).  I had to play with things in SQL Configuration manager before remote connections could be made to SQL (but the Sage service to SQL was fine since it didn't need to go through the network / firewall).

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



  • 4.  RE: Connecting to the Business Object

    Posted 01-19-2021 19:46
    Thanks everyone.  Port 1433 was already opened, hosting company made an adjustment on the Router I believe and now I can connect.  

    This can be moved to General Sage 100.  Thanks
    Nancy

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


Related Content