SCOM 2007 HP OVO certificate failure

Hello,

i have:

- SCOM 2007 R2 U3 installed on W2k8 R2 64bits

- HP OVO interop installed  on W2k8 R2 64bits

- OMW 9


At the end of installation, wizzard is able to communicate with my Interop connector, but certificate retrieval always in fault.



Ouput:

scicert.exe LMON1WSIS11V01 <local_admin> <pwd> "OpsMgr Connector for HP OpenView Operations"
Connecting to: https:local_admin@LMON1WSIS11V01:1270
ERROR: WSManLibException caught ==>
-- Error in method WSManSession::Execute --
<f:WSManFault xmlns:f="http:schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="1359" Machine="LMON1WSIS11V01"><f:Message><f:ProviderFault provider="WMI Provider" path="%systemroot%\system32\WsmWmiPl.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="1359" Machine="LMON1WSIS11V01.fr."><f:Message>HRESULT = 0x80041013</f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
Error number: 0x8007054f



I try with this:

winrm enumerate http:schemas.microsoft.com/wbem/wsman/1/wsmanfault auth:basic -remote:https:lmon1wsis11v01:1270 -username:local_admin -password:pwd -skipcncheck -skipcacheck

result is KO

WSManFault
    Message = The WS-Management service cannot process the request. The resource URI (http:schemas.microsoft.com/wbem/wsman/1/wsmanfault) was not found in the WS-Management catalog. The catalog contains the metadata that describes resources, or logical endpoints.
Error number:  -2144108485 0x8033803B

winrm enumerate http:schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_Service auth:basic -remote:https:lmon1wsis11v01:1270 -username:local_admin -password:pwd -skipcncheck -skipcacheck

result is good and services are displayed

So i wonder what could be the root cause of my issue, because the schemas that Connector try to reach seem unavailable !!

I uninstall and reinstall both connectors several times, with domain administrator and local admin, same result.



In documenation it says that we should transfer certificate manually, but procedure still bases on remote query. I try following this thread:

http:blogs.technet.com/b/stefan_stranger/archive/2011/08/16/lessons-learned-the-opsmgr-2007-r2-universal-connector.aspx

i copy the Interop certificate on OPS Connector and run the command 

scxcertconfig.exe" -sign c:\LMON1WSIS11V01.cer c:\LMON1WSIS11V01_sign.cer

Output:

Signing failed: Can't decode from base64

my sci.log show that OVO library seem not loaded.

I guess it's my OS fault because it is a 64bits and OMW9 that running on is 64bits application too.

Registry keys could solve my issue ? If yes, someone know wich key i have to create?




Please any help will be appreciate

EDIT: url link are well formated, i remove the // to prevent microsoft check that not allows me to post any link...


  • Edited by Nicnictout Monday, May 27, 2013 4:07 PM
May 27th, 2013 6:04pm

Have you done the following to get the provider installed on HPOM 9.x?

HP OM 9.x works with the connector but there are issues getting it installed if HP OM 9 is installed on a 64 bit version of Windows. You can get around this issue by creating the 32 bit registry key on the HP OM server under HKLM\SOFTWARE\Hewlett-Packard\HP OpenView\InstallDir (this key should already exist under the 64 bit tree) and point it to the appropriate directory HP OM is installed under before installing the provider for the connector.

Note that this is known to work but support will be limited as it is not a supported configuration.

Does the following winrm command work when run from the SCOM server?

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:<local administrator> -p:<local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"  

Regards,

-Steve

Free Windows Admin Tool Kit Click here and download it now
May 28th, 2013 4:00pm

Hi Steve,

i found this thread in order to install the Interop Provider on HPOM side. Installation was successfull.

When the connector wizzard start, systems are able to communicate each other, but process failed when i try to install the certificate.

In there a way to install this certificate locally, because documentation speak of physical media to transfer it, but command make a remote request !!!

I test your command, and it fail, even when locally... 

Output:

WSManFault
    Message
        ProviderFault
            WSManFault
                Message = HRESULT = 0x80041013
            ExtendedError
                __ExtendedStatus
                    Description = null
                    Operation = ExecQuery
                    ParameterInfo = select * from SCX_Connector where Management
GroupName = 'test'
                    ProviderName = WinMgmt
                    StatusCode = null

Error number:  -2147023537 0x8007054F
An internal error occurred.

As others request are working (for WMI process list for example) i wonder if the Interop is installed but not fully functionnal. As i said, i try to reinstall it several time, with a local admin, i am not an expert in WSMAN so i'm quite lost to troubleshoot :(

Thx to help me :)

May 28th, 2013 5:19pm

You can start troubleshooting but going here --> http://technet.microsoft.com/en-us/library/ee809025.aspx

but I'd first start by turning on "Enable TRACING for the Windows provider" -->http://technet.microsoft.com/en-us/library/ee809020.aspx

Once tracing is enable and you reboot the server, check the c:\sci.log and verify the provider is getting loaded properly. If the provider is loaded then try the winrm query I sent in my previous post and check the c:\sci.log again and see if it gives any clues as to what is going on.

Regards,

-Steve

Free Windows Admin Tool Kit Click here and download it now
May 28th, 2013 5:45pm

Steve here the output of debug:

For what i see the issue is caused by dynamic library that are not loaded:

SCI.LOG:

2013-05-28 17:06:45.338 Debug [SCInterop::Config] Creating default Config Object
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Creating default Config Object at C:\profile_sci
2013-05-28 17:06:45.338 Debug [SCInterop::Config] PROFILE_SCI environment variable not set, using C:\profile_sci
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Parsing config file
2013-05-28 17:06:45.338 Debug [SCInterop::Config] C:\profile_sci is open...
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Reading configuruation values.
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found AUTH=
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found CONNECTOR_HOME=C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found EMS=OVO
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found EVENT_READ_LIMIT=100
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found FILE_FORMAT=EVT
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found OVO_MOD_EVENT_CODESET=LOCALCODESET
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found OVO_NEW_EVENT_CODESET=LOCALCODESET
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found SERVER=
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found TEC_HOST=LOCALHOST
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found TEC_PORT=5529
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found USER=
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Transforming and checking read configuration values.
2013-05-28 17:06:45.338 Debug [SCInterop::Config] stored path=C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\
2013-05-28 17:06:45.338 Debug [SCInterop::Config] CONNECTOR_HOME=C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found EVENT_DIR=
2013-05-28 17:06:45.338 Info [SCInterop::Config] (EVENT_DIR) undefined, using is (CONNECTOR_HOME) path: C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\
2013-05-28 17:06:45.338 Debug [SCInterop::Config] Found EVENT_DIR=
2013-05-28 17:06:45.338 Debug [SCX_Adapter] Loading OVO Adapter
2013-05-28 17:06:45.338 Debug [SCInterop::ObjectLoader] Loading library: ScInteropOvo.dll
2013-05-28 17:06:45.338 Error [SCX_Adapter] Error initializing ConnectorProvider: Dynamic Linking Exception: Error opening library: 
2013-05-28 17:06:45.338 Error [SCX_Adapter] OVO DLL not loaded

evtCon.log:

5/28/2013 4:08:58 PM INFO - ***** Starting System Center OpsMgr Event Consumer for HP OpenView *****
5/28/2013 5:00:09 PM INFO - ***** Stopping System Center OpsMgr Event Consumer for HP OpenView *****
5/28/2013 5:00:35 PM INFO - Successfully set connector_home - C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\
5/28/2013 5:00:35 PM INFO - Setting sciConfigFile location - C:\Program Files (x86)\System Center Operations Manager 2007 Providers\Operations Manager 2007 Connector to HP OVO Provider\OvoEvents\sciOVOtoOpsMgr.conf
5/28/2013 5:00:35 PM WARNING - Service1: OpsMgr to HPOMW Provider: Registry Key is NULL
5/28/2013 5:00:35 PM WARNING - Service1: System Center OpsMgr to HPOMW: Could not open SubKey in Registry: System.NullReferenceException: Object reference not set to an instance of an object.
   at OpsMgrHPOMWEventConsumer.Service1..ctor()
5/28/2013 5:00:35 PM INFO - ***** Starting System Center OpsMgr Event Consumer for HP OpenView *****

I don't see anything else in others logfiles. Do you need it ?

in the meantime, i take a look to the other links you provide.

Thx

May 28th, 2013 6:14pm

I precise that the  ScInteropOvo.dll and  ScInteropProv.dll are present on system.
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2013 6:16pm

Your problem is here:

[SCInterop::ObjectLoader]  Loading library: ScInteropOvo.dll 2013-05-28 17:06:45.338 Error

[SCX_Adapter] Error initializing ConnectorProvider: Dynamic Linking Exception: Error opening library:  2013-05-28 17:06:45.338 Error

[SCX_Adapter] OVO DLL not loaded

The ScInteropOvo.dll links to HP OM dlls and they are not in the search path so we are getting "Error opening library" errors.

When you installed the provider on the HP OM server on the X64 bit system you had to create a registry key to the install directory of HP OM. Does this actually point to the location HP OM is installed? You can actually put anything in this key to get the provider to install but the provider uses this location to find the required HP OM DLLs to make the connector work. If this does not point to the HP OM install you will get the error you are seeing.

Regards

-Steve

May 28th, 2013 7:12pm

Yes i check the registry and key point to the right directory. I even check environment variable for OMW and there are good too !

I see this error yesterday, it seems i'm not the only one to have this issue, but all solution found were: reinstall the provider...

I try many times, same result


  • Edited by Nicnictout Tuesday, May 28, 2013 4:20 PM
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2013 7:20pm

I see the problem. Had to install the provider on a Windows 2008 R2 X64 bit system to figure it out but it is looking for the DLL under the "C:\Program Files\HP\HP BTO Software\bin\win64" (my default install location) directory and since this is a 32 bit app it needs to look under "C:\Program Files\HP\HP BTO Software\bin"

Add the following to your environment path:

right click My Computer>Properties>Advanced>Environment Variables>System Variables>Path>Edit>Variable Value, add a semicolon (which means "in addition to all before") and paste the full path to the 'bin' directory. In my HP OM install it is "C:\Program Files\HP\HP BTO Software\bin". Yours my vary...

Save this and reboot the server then try the winrm command again:

winrm e http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scx/* -r:https://<HP OM server>:1270 -u:<local administrator> -p:<local admin password> -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = 'test'"

If all goes well it should return nothing. Look at the c:\sci.log for errors if it does fail.

Regards,

-Steve

May 28th, 2013 8:45pm

Many thx Steve it's working now :)

Well it seems that system is not able to stop/start the connector now, but i saw many post on this error, i will investigate a bit by my own.

Thx

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2013 11:25am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics