Sage 100

Customer on Windows SBS 2011 Standard - they're moving MAS200 from one server to another. I re-run the install on new server. Run Application Server Service Setup. Does not put a MAS200 Service into the services list. Rights issue? Compatibility? Other?

Run as Administrator"" seems to have fixed

Now I'm getting a ""Could not read port number"" when trying to create the service. Even when running as Admin. I changed the MAS200 server name to SAGE. Any ideas? Sage KB seems silent and I'm aware they are on an old unsupported MAS200 4.05

Looking at whether this is a firewall issue. Customer IT doesn't seem to have much of a clue. Probably on their end.

Are you a domain admin or the local admin? I seem to recall having issues creating a service unless you were the local administrator of the machine, though in those cases I did not get an error, just no service created.

I find that I have to run as Administrator in order to get the service created. But if I don't have the BEST server in there it's crapping out and telling me it cannot find the port # and to enter in through the setup (which naturally I've done).

I'm also getting ""Access Denied"" when trying to edit and save sota.ini locally so I'm presuming there's some configuration issue locally concerning user rights. EDIT: This was resolved by running notepad ""run as administrator"" then open the sota.ini. From there it would save provided I had ""run ad admin"" to get notepad going. <off topic> This is a huge reason I could see many small companies benefiting from SaaS. The complexity of some server setups for security is way over the typical IT persons head. </off topic>

Starting to think that MAS 200 v4.05 is not compatible somehow with SBS 2011 -- no amount of reasonably effort gets by the errors and ultimately I'm plopped out to ""MAS 200 is not setup properly please run workstation setup to configure this workstation

4.05 or 4.50? 4.05 would not be supported on SBS 2011.

Not sure what the core issue was. I tried to change default MAS200 name from BEST to SAGE and port from 10000 to 9200. That resulted in the above issues. When I just left it at the default of BEST/Port 10000 everything seemed to run. Also I had to make sure to install everything using ""Run as administrator