Sage 100

 View Only

  • 1.  Sage 100 2020 Premium - Error 15 Operating system command failed

    Posted 08-19-2022 16:40
    End user is having a rash of Error 15 Operating system command failed errors. Prior to moving the virtual servers used for Remote Desktop, SQL Server, and Sage 100 Application Server, there were no such errors. In June 2022, the VMs were moved to corporate HQ and unto different hosts. Since that time, there have been frequent occurrences of the error below. 

    Operating system command failed
    My response has been as follows.

    This is an issue of the Microsoft SQL client communicating with SQL Server. Microsoft states this is a network issue and not SQL Server. Sage utilizes the SQL client. The error isn't an error generated by the Sage application. The application is providing the error message returned by the Microsoft SQL Client. That is why it is labeled an OS error. It is an error from the operating system (SQL Client). The question to ask is, Why are Microsoft SQL clients having issues reliably communicating with the SQL Server? 
     
    The intermittent nature of the error further indicates it is an infrastructure issue. If Sage 100 was having an issue communicating with the Microsoft SQL client, Sage 100 wouldn't be able to run. Sage is able to communicate with the SQL Client evidenced by the OS error. Sage 100 and the SQL Client are still talking to each other.
     
    1. Is my reasoning correct or could it be something in Sage 100?
    2. Has anyone experienced this situation and have a solution?

    Is this a Sage 100 Premium issue or a network one?



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


  • 2.  RE: Sage 100 2020 Premium - Error 15 Operating system command failed

    Posted 08-19-2022 16:53
    Definitely environmental.
    For errors during normal operation in Sage 100 (opening panels, data entry...) this is an issue with commutation between the Sage service and the SQL service.
    If it only happens during printing it would be communication between the workstation (CR print engine, where the Sage client is running) and the SQL service.

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



Related Content