When you reinstalled, did you completely delete all files in the install folder before reinstalling?

Check the contents of the sota.ini file in the launcher folder.  It will take the form:

[SQL]
DSN=MASSQL
[Servers]
1=servername;9455;APS=BEST;APPLICATION=MAS 200;Path=\\servername\serverpath\MAS90\

[Active Server]
servername;9455;\\servername\serverpath\MAS90\

Note in my case, I call out a different port than standard. You should know which port you are using. You can also use the IP directly in the ini.

[SQL]
DSN=MASSQL
[Servers]
1=10.3.2.3;9455;APS=BEST;APPLICATION=MAS 200;Path=\\servername\serverpath\MAS90\

[Active Server]
10.3.2.3;9455;\\servername\serverpath\MAS90\

The first time I reinstalled I did not delete all of the files in the install folder. Have done that on two more uninstall/reinstall attempts since.

Have compared contents of the sota.ini file with other workstations that have no problems.  Can find no differences.

Thanks for your suggestions.

Question, how many users? How is MAS being run, service or application? On the work station are you using the server name or IP address during work station setup?

Around 30 users.  I'm very new in supporting this system so I'm not sure how to answer the service or application question.  It is setup like a client/server application to the best of my knowledge.  The server name is being used in the workstation setup.

For MAS200 it is best if you run it as an application on the server. Less connection problems. Also when running work station setup you should be using the IP address and NOT the server name. Again less connection problems.On how to run as an application should be in the documentation or you can contact your reseller.