Article ID: 943319 - Last Review: October 11, 2007 - Revision: 1.0
Engyro Connectors for MOM 2005: OVO epcmomd restart
Rapid publishing disclaimer
Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.SYMPTOMS
When the epcmomd daemon goes down hard the OVO Management server does not release the instance that the epcmomd daemon was running under. When you try to restart the daemon it is unable to restart.
RESOLUTION
Please follow the steps below to resolve the issue:
- stop OVO:
ovstop -c - delete the following via a command prompt:
rm -rf /var/opt/OV/share/tmp/OpC/mgmt_sv/*
Note: The files in this directory will get recreated when you restart the management server - start OVO:
ovstart -c
Note: This article is from Microsoft Knowledage Base
Related problems posted by other users | |
| more... |

