Sage 100

 View Only
  • 1.  Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 07:06
    Does anyone troubleshoot Starship or does everyone just let V-tech support do it. I installed v2017 on client server last night. Starship now looking at the v2017, not v2016. Last month when I did it, V-tech said to start up v2016 on the server and their link would automatically redirect back to v2016. That is not working today. This months Sage 100 is ADV, last month it was STD. Thoughts? TIA


  • 2.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 07:46
    There is a 12xSwitch program in C:\Program Files (x86)\Starship\Client somewhere. I dont remember the exact name of the program but is has ""MAS"" in the name I believe. Try running this program.


  • 3.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 07:48
      |   view attached
    Thanks It is in V-Tech's hands now. This is the first step they provided. Hopefully, it is the last step.

    Attachment(s)

    pdf
    StarshipGotchas.pdf   79 KB 1 version


  • 4.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 07:50
    Is it the BOI version or the Link? You might just need to go to Starship on the workstation and select Setup / Source Interface. Another option is to stop and restart the Starship server. If that does not work, call them. They have very good support


  • 5.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 07:53
    The registry hack doesn't look like the most elegant solution to having multiple versions of Sage 100 on one server. Seems that would be a common occurrence. Thought Vtech would have a better solution than this by now.


  • 6.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 08:54
    Client is running the MIFS connection. Per their email, they admit it is not elegant. I tend to think it is a bigger issue for ADV users. The registry hack did have some type of impact as they are now getting a different error. My question is how is v2017 advanced going to function with the changed registry. Maybe I should suggest moving the MIFS program service off the Sage server


  • 7.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 09:00
    reading again at what you are doing, you simply installed Sage v2017. The 12xSwitch most likely wouldnt help as I believe all it does is register dll programs. If Starship is working but looking at the worng Sage installation 12xSwitch would be useless. Vtechnologies generally has great support in my experience so good idea to call as soon as you did.


  • 8.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 09:06
    I have V-Tech handle all of the upgrades. I learned a few years back that V-Tech knows about most problems but doesn't publish them. I have since advised the customer to buy a case with V-Tech for upgrades and I have very little/no push back.


  • 9.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 10:45
    @WayneSchulz , we do the same.


  • 10.  RE: Does anyone troubleshoot Starship or does everyone

    Posted 08-10-2017 10:59
    I always install Starship myself and rely on Vtech for help on an as-need basis.