Sage 100

v2017 Adv Installation and Starship - Dang it!!!!! All I did was install Sage v2017 on the server last night and rebooted the server. Did nothing else. Now Starship is pointing to the new version (no company code for ECL). What the heck happened and how does it get fixed. We have sent a note to Starship tech support but who knows how long their response will take. It is my understanding that they make Sage Tech support look good. TIA

I would call Starship instead of emailing...I always get through and usually have great success with their staff.

I agree. 800-462-4016 #3

I think Starship points to the Sage 100 client that is running.

I think @JimWoodhead is correct. I recall having a similar experience when we upgraded a client on the same server (the client was in test mode at the time), and SS support resolved the issue.

I would give them a call. I also always get through quickly and to someone that really can help.

Epilogue - After talking with Abel, Kyle and then Terry at V-tech support, Terry said that all we had to do was access v2016 at the server, then close down the client in the shipping department, then go back into the client. Apparently, starting v2016 at the server resets the pvxcom which redirects the client to the correct version. BTW, Starship is running in ""MIFS"" mode. Very bizarre, but client is back up and shipping.

MIFS?

You got me! I am Starship Illiterate. Below is advice for the first tech support guy (which wasn't even close). Apparently, if you run in MIFS mode, the interface is faster. _The Sage interface is a range from 4.1 - 2017, we do not have a specific BOI interface for 2016. Please check the Windows registry on Client machine or if they use 'MIFS', on the Sage Server machine. Make sure the MAS90RootDirectory is set correctly. - (HKEY_CURRENT_USER\Software\Sage Software\MAS 90 Business Desktop\Settings\MAS90RootDirectory=' )_ Moral of the story, ask for Terry, he called it in about 30 seconds.

Looks like it stands for MAS InterFace Service.