Cannot Start MAS200 Service

SUGGESTED

Last week, all users hung up in MAS200 (Version 4.5.0.5) at the same time.  IT rebooted the server, but the service did not start automatically as it was set to do.  When he tried to restart the service, the following error appeared:  Windows could not start the service.  Error 193: 0xC1.  If we tried running MAS200 as an application, the server showed Running in Application Server Configuration, but we received an "Unable to Connect to Server" message when trying to launch MAS200.  We have been working with Sage, but still do not have a resolution.  Here is what we have tried:

1.  Restored the _appserv directory from backup

2.  Uninstalled and reinstalled the service.

3.  Set up a new port & service for that port.

4.  Renamed SY_Sessions & SY_locate in the _appserv directory.

5.  Changed the user account in the Logon section of the Service to a different Admin. account.

6.  Disabled the Windows Firewall

7.  Reinstalled System Setup & Library Master (renamed the _appserv folder first) and the product update.

At this point (after reinstall of SS & LM) we can run MAS200 as an application.  However, they want to run this as a service and we still receive the same error 193 when trying to start the service.  I would appreciate any suggestions.  Thanks.

 

  • 0

    I would start by removing the service, If there are any other services starting with "MAS" remove those too.  

    If you installed the service from the Application Server, by accident or on purpose, the service will be called "ProvideX Application Server - SAGE" uninstall that too. I don't recommend installing the service that way.

    Then reinstall the service and make sure the path is correct.

    If you are still getting the error:

    1. You could have a a program or file  called "Program" on your system root (c:\)

    2. You could have a program or file called "Common" in the Program Files directory.

  • 0

    I always run MAS200 as an Application and never as a Service, lots less problems. It would be my suggestion to run as an App.

  • 0 in reply to BigLouie

    Thanks to both of you for your replies.  We tried your suggestions (TOG), but no luck.  Decided to just run it as an application.

  • 0
    SUGGESTED
    I know this is an older issue, but I have seen this before in the past and to resolve this issue, add quotation marks ( " ) around the ImagePath value in the Windows registry.

    Backup System Registry first.

    To add quotation marks to the ImagePath registry value:

    Click Start > Run.
    In the Open box, type regedit, and then click OK.
    Navigate to

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sage ERP MAS 200 SQL ##### (#####= Port) (usually says SQL even though it is not)

    In the right pane, double-click ImagePath.
    In the Value data box, add quotation marks ( " ) around the complete path of the executable file for the service.