Absent Member.. wang,jiyuan Absent Member..
Absent Member..
755 views

remote agent for OMW can not start

Jump to solution
hi all,
i run "opcragt remote node B" command in OMW server, got the result:Failed to connect to OvMsmModelCache, Error….. ; Remote administration was not started because of the critical error.
does it means the remote HP operation agent down? why? licese? or others?
thank you!
0 Likes
1 Solution

Accepted Solutions
Acclaimed Contributor.. Harald Acclaimed Contributor..
Acclaimed Contributor..

Re: remote agent for OMW can not start

Jump to solution
Hello,

the problem is the OMW Server. The OvMsmModelCache is a server process.

You could also test the agent connection using ovpolicy -list -host .
Or e.g. ovrc -host -status
8 Replies
Acclaimed Contributor.. Harald Acclaimed Contributor..
Acclaimed Contributor..

Re: remote agent for OMW can not start

Jump to solution
Hello,

the problem is the OMW Server. The OvMsmModelCache is a server process.

You could also test the agent connection using ovpolicy -list -host .
Or e.g. ovrc -host -status
Absent Member.. Mohamed AbdelMo Absent Member..
Absent Member..

Re: remote agent for OMW can not start

Jump to solution
could you list the following information:
1. agent type (DCE - HTTPS)
2. Agent version (7.x - 8.6.x)
3. Patch level on OMW server and the agent
0 Likes
Absent Member.. wang,jiyuan Absent Member..
Absent Member..

Re: remote agent for OMW can not start

Jump to solution
hello,
the problem is the OMW Server. The OvMsmModelCache is a server process.
Then restart the process?

The result of 'ovrc -host -status':
ovcd OVControl CORE (5420) is running
opcmsgi OVO Message Interceptor AGENT,EA (5560) is running
opcle OVO Logfile Encapsulator AGENT,EA (5864) is running
agtrep OV Discovery Agent AGENT,AgtRep (3204) is running
coda OV Performance Core COREXT (3340) is running
opcacta OVO Action Agent AGENT,EA (4652) is running
opcmona OVO Monitor Agent AGENT,EA (6108) is running
opcmsga OVO Message Agent AGENT,EA (3208) is running
ovconfd OV Config and Deploy COREXT (1376) is running
ovbbccb OV Communication Broker CORE (6036) is running
0 Likes
Kumar Dilip Absent Member.
Absent Member.

Re: remote agent for OMW can not start

Jump to solution
Hi,
Are all the agent processes running on the agent? How about the communication between them?
Did u install the certificate properly?
0 Likes
Absent Member.. wang,jiyuan Absent Member..
Absent Member..

Re: remote agent for OMW can not start

Jump to solution
hi
The agent and agent node are all ok, server and agent can communicate successfully.i just want to see the status on the server node with the command 'opcragt' but it shows the result as i mentioned.
0 Likes
Acclaimed Contributor.. Harald Acclaimed Contributor..
Acclaimed Contributor..

Re: remote agent for OMW can not start

Jump to solution
Hello,

does it help to start/stop the omw server processes?
vpstat -3 -r stop
vpstat -3 -r start
0 Likes
Absent Member.. wang,jiyuan Absent Member..
Absent Member..

Re: remote agent for OMW can not start

Jump to solution
hi,
There is noe use to restart server.
The result still be:
Failed to connect to OvMsmModelCache ((ITF11E) Error 0xA004000B (FAILURE, Facility: ITF, Code: 11)). (MC44) Failed to initialize the WMI connection ((ITF61441E) Error 0x8004F001 (FAILURE, Facility: ITF, Code: 61441)). (MC379) Initialization of Server Monitor connection failed ((ITF61441E) Error 0x8004F001 (FAILURE, Facility: ITF, Code: 61441)).
Remote administration was not started because of the critical error

Anything wrong with WMI or others?
0 Likes
Highlighted
Absent Member.. aalgohary Absent Member..
Absent Member..

Re: remote agent for OMW can not start

Jump to solution

I also have the same problem but I think it arrised to me because I changed the FQDN of the OMW server then I followed these steps:

  • opcagt –kill
  • vpstat -3 -r STOP
  • ovconfchg –edit

 I changed all the occurrences of the old server fqdn with the new fqdn.

 

Use regedit to update the following registry keys. Change the old management server name to the new one:

HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\DBAccess\OvOWInstance

HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\MsgActSrv\MGMT_SERVER

HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\MsgActSrv\NAMESRV_LOCAL_NAME

 

Change the hostname and reboot the system.

Start the console and connect to the new management server name.

Check the Network tab of the Node Properties dialog box for the management server:

  • If the old name of the management server was specified in the Primary node name field, correct it.
  • Check also the Message Identification tab to see if the old name of the management server was specified there. If yes, correct it.
  • If Domain Name(FQDN) is selected, verify that the new name resolves to the IP address of the management server.
  • Optional. Change the display name of the management server on the General tab.

Open a command prompt and enter:

SetMgmtServer

 

The output will be similar to this:

 

Agent package 'C:\Program Files\HP OpenView\\packages\Windows\OvEpMsgActAgt.FM'

Management server name was updated from 'old_serv.rose.hp.com' to 'hpom_serv.rose.hp.com'

SYSTEM account installation: enabled

Authentication enforcement: disabled

Forced user account switch: disabled

 


After all these steps, every thing is OK except opcragt command, it displays the following:

 

(MC77) Failed to connect to OvMsmModelCache ((ITF11E) Error 0xA004000B (FAILURE,
 Facility: ITF, Code: 11)). (MC44) Failed to initialize the WMI connection ((ITF
61441E) Error 0x8004F001 (FAILURE, Facility: ITF, Code: 61441)). (MC379)  Initia
lization of Server Monitor connection failed ((ITF61441E) Error 0x8004F001 (FAIL
URE, Facility: ITF, Code: 61441)). <null>
Remote administration was not started because of the critical error

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.