Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..
209 views

not showing opcmsga in agent status output

Hello Support,

 

on few of nodes where OA is installed, i dont see opcmsga/opcacta listed. i rememeber this kind of issue in the past when license was missing but this is not the case here.

 

also when i run opcagt i get the following error.

 

Input Error: Can not find script file "C:\bin\win64\OpC\opcagtw.vbs".

 

Does anyone have idea what is wrong here?

 

-KAKA-

 

0 Likes
7 Replies
Highlighted
New Member.

Re: not showing opcmsga in agent status output

Hello Kaka

 

start_chk_msga.pl may be failing

 

Check this value in ovconfchg -edit

 

[sec.core.auth]

MANAGER=<valid mgr ip/name>

 

If not set

 

Please run opcactivate again and see if that value is set

 

Then do

 

ovc -start

 

Thanks

Sandeep

Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: not showing opcmsga in agent status output

Hallo Sandeep,

 

Thank you for your response.

Don't see any issue with sec.core.auth. valid manager name is set.

 

-KAKA-

0 Likes
Highlighted
New Member.

Re: not showing opcmsga in agent status output

Hi

 

Please try running

 

start_chk_msga.pl from command line

 

echo %errorlevel%

 

 

Thanks

Sandeep

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: not showing opcmsga in agent status output

below is the output i got from this machine.

 

C:\Program Files\HP\HP BTO Software\nonOV\perl\a\bin>perl "C:\Program Files\HP\H
P BTO Software\bin\win64\start_chk_msga.pl"
'""' is not recognized as an internal or external command,
operable program or batch file.
'""' is not recognized as an internal or external command,
operable program or batch file.

 

where as on other machine i get the output "success".

 

-KAKA-

0 Likes
Highlighted
New Member.

Re: not showing opcmsga in agent status output

Hi Kaka

 

Looks strange

These are the 2 commands which is checked by that script

 

oalicense -check OA

 

And

 

ovconfget sec.core.auth MANAGER

 

Other checks are using

 

ovpath -instdir

 

That retrieves install dir

 

Please check if that is set correctly

 

 

To check if PATH is correct in the system you can use this command

 

ovdeploy -cmd env

 

 

 

 

 

Thanks

Sandeep

0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: not showing opcmsga in agent status output

This seems like the paths are not set part of ovpath procedures which adds additional entries to the Windows registry part of the agent installation process.

 

I would suggest running the oainstall.vbs again so that the appropriate paths are set in the Windows registry. As I think the system path variable for the agent may potentially be set but the path in the Windows registry for the agent configuration isn't.

 

Another option is to locate the HP Operations Agent windows registry keys from a working system which has the paths set and export or create them on the system that doesn't have these set.

Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: not showing opcmsga in agent status output

Hi Nick,

 

i have already checked, path is set in the registry as well. if i run the ovpath.exe from command prompt it does return the installtion directory. problem is when it is executed from a perl script or batch file it does not. so it looks like a issue with the shell.

 

i have raised a case with Support.

 

-KAKA-

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.