As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
We can't stop the service for a managed server. When we click on the stop we get the following windows error in the services pop up box "Windows could not stop the Iway Service Manager 6.2 - osha service on local machine. The service did not return an error. This could be an internal windows error or an internal service error. if the problem persists, contact your system administrator."
After I get the error, windows does show that the service is stopped, however, when I then click on start windows tells me that it's started but the ISM tells me that it is not started. I even rebooted the server, hoping that it will reset anything that was still in memory, that didn’t help either. Is there anybody that experienced this and what is the solution.This message has been edited. Last edited by: Tamra,
It appears that you are having problems starting up a "non-base" managed server.
What is unclear is that, how does the problem appear even after a system restart?!?
Anyway, try following this approach:
Following lines of code is based on an assumption that the name of problematic managed server involved here is "osha".
Launch a command prompt:
Start -> Run -> CMD Prompt [Run it as Admin] Naviate to iWay_Root/bin iwsrv.exe osha -s remove [this command should give you a message that service was removed successfully or something along those words] Now, run this: iwsrv.exe osha -s install -c -l iWay61.cmd [this command should give you a message that service was installed successfully or something along those words]
Come back to Windows Services, choose the service and try to start it up.
I see that this thread has been closed. I suggest to, please, mention a closure description which may include a response for my suggestion or was only that a fix for your problem or you had to do something else to fix this?
Please understand that this may bbe helpful for otehr members of the community to get a clear picture when they face the same problem and go through this.