Sage 100

 View Only
  • 1.  Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 14:59
    Trying to do a V4.5 PU 5 update. Getting the message that the integration engine service is running and needs to be stopped. When I look at the servcies, the integration engine is not running. I set the service to manual, reboot the server, get the same message. Any thoughts on what else to try or look?


  • 2.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 15:01
    check for an apache tomcat service and try stopping that. @AaronClark - could Apache be causing that message?


  • 3.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 15:16
    If the services window shows it as stopped, I'd refresh the window to make sure I've got the latest information (skipped that once, and regretted it later), and then I'd check the processes in Task Manager for integrationengine.exe and kill 'em all. I don't know that Tomcat would have anything to do with that piece of the integration.


  • 4.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 15:17
    sounds good - I just remember having to shut down that Tomcat service one time - but it was probably for something else. Thanks Aaron!


  • 5.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 15:17
    Could it be running on another server in the organization?


  • 6.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 15:53
    Will try again at a later time. I hate new orphan clients!!!! Everything is a mystery the first time or so around. There have been way too many cooks in this kitchen. Thanks for the thought about the integrationengine.exe. I was looking for something with Sage or MAS in the name and didn't think beyond that!


  • 7.  RE: Trying to do a V4.5 PU 5 update. Getting the mess

    Posted 03-04-2013 17:50
    I had a similar issue and couldn't for the life of me figure out what the problem was. After shutting everything down and rebooting we recalled that they had separate install at an older version that runs Automated Service and due to several upgrade nightmares they just run it separately from their ""regular install"". With an orphan I could see something like that being possible.