Sage 100

Found issue today relating to installing FAS on a computer on our network. FAS installed fine, the issue occurred when I tried to start FAS Service manager, It attempted to start and then gave an error stating that the Service parameters were wrong. To resolve the issue, I changed the name of the FAS engine from MASFIXEDASSETS to MASFIXEDASSETS2 (added a ""2"") and the service started. Turns out that when you start FAS, it looks over the entire network to check if any other FAS engines are running and won't start if it see the same engine name. Just a FYI....

Jim this is an example of what i think we should be putting into a 90 Minds KB that we could access via the Internet. To me this type of information is going to start to become a competitive advantage -- especially as Sage goes off on their tangents to re-brand, return to growth and possibly takes their eye off the technology side of the house. Sorry to go off topic. I really think we should chat about finding an online KB.