Sage 100

I have a client that moved to Windows Small Business Server 2011 Standard. Installed MAS 200 version 4.40 on the server and migrated the data from the old server. Everything works fine as long as you are working on the server, but when you go to one of the workstations, MAS 200 ignores any requests from the workstation. For example, program won't change modules, change date, change company, or do anything else for that matter. Tried running MAS 200 both as an application and a service - didn't change anything. Turned off firewall and anitvirus - didn't change anything. Installed 4.50 and same thing. It is probably somehing on the server but I don't have any more ideas. Any ideas?

First be sure there's nothing strange going on -- run MAS200 as standalone. Get to the server \ HOME and Run ""Startup.M4P"" Verify that works properly Can you ping the server (though I thought this was no longer supposed to be an issue)

I have had issues with WIN 2008 Enterprise where the security rights did not propogate properly down through all the folders. Worked great at the server but faltered at the workstations. Once the security rights for the user/group was established, the problem disappeared. This had the IT guy stumped for several hours.

The SPM for MAS 200 version 4.5 explicitly states no version of SBS is supported. For version 4.4 the SPM states SBS 2008 SP2 is supported but it recommends not using any version of SBS. I had this discussion with a client a few months ago and they went with SBS 2008. No problems so far.

Also I always send the customer a copy of the current supported platforms (usually a link to the Sage PDF) rather than give into their questions about ""what should I buy"" for hardware/OS. Sure as heck if you give a ""it should work"" or ""I think my other customer has it working"" in the customer's ears they hear ""I guarantee this will work and if it doesn't we will cover you under support""...

Just because no version of SBS isn't supported doesn't mean that MAS shouldn't work on it. In the back of my mind I am thinking the reason they choose not to support it is because SBS usually means that Exchange is on the same box which will drastically reduce performance. My 2003 SBS runs MAS (both versions) just fine. But then again, I don't have Exchange running.

It's also because SBS is usually a domain controller.

@JeffSchwenk I think it's risky to go against the Sage supported platforms unless you want to become Sage's unpaid complaint department... .02

@JeffSchwenk you have SBS 2003 - which DID work but I agree with @WayneSchulz about not going against the SPM. Why take that on in addition to whatever bugs you might find in MAS??

Don't get me wrong. I certainly don't go looking for unpaid work. Sage sometimes takes the easy way out and if we can easily help out the client, then I'll do it. Like everyone else, if a client asks me AHEAD of time what to do, I give them the SPM and tell them to follow the guidelines.

SBS breaks Microsoft's OWN best practice rules and especially with the virtualization capabilities we have now is almost always a bad idea.

I did supply the SPM to the client's IT guy and pointed out that SBS 2011 wasn't supported. He did a search on the internet and found a SPM that said 2011 was supported. (I need to found out where he searched). So, against my advice, he purchased SBS 2011. Now I get to try to deal with it. Don't you love it!

Looks like it is time to start playing hard ball............................. Will be interesting to see the document that he based the decision on. I don't see on my SPM's any mentioning of 2011 being excluded (or included) from support.

If it's like the IT people I regularly encounter they'll claim that since Office 2003 is supported so should MAS90....

SBS 2011 is supported with MAS 90 4.5.

I would disable UAC if you haven't already