Answered by:
OpsMgr Connector for HP Openview Operations (.Net SqlClient Provider)

Question
-
We want to connect our SCOM 20007 R2 Server with the main monitoring tool HP Operations Manager for Windows 8.16. Wie installed the SCOM HP InterOp Connector. Everything during the installation and configuration went fine. But when we try to open the connector out of the SCOM console
Product Connectors -> Interop Connectors -> HP OpenView Operations Connectors -> OpsMgr for HP OpenView Operations
I got the following error message:
.Net SqlClient Provider
Invalid objectname 'dbo.SplitString_fn'
The message fowarding doesn't function.
Anyone who has used scom integrations and have some tips here?
Thanks in advance, Best Regards
Wednesday, September 12, 2012 8:21 AM
Answers
-
Not sure what is going on here. Looks like it could be an issue with SQL but I've never run across this error before with the connector. I suggest you open a support case with Microsoft as they can turn on tracing and get into the code a lot easier then we can do on the forums.
Regards,
-Steve
- Marked as answer by Steve Weber [MSFT]Moderator Tuesday, September 25, 2012 11:52 AM
Monday, September 17, 2012 1:32 PMModerator
All replies
-
The connector UI is driven by the MP. Try removing the MP and reinstalling it. It can be found under the install directory of the connector. If this does not help I would try reinstalling the connector and make sure you run the installer with Admin privileges.
If that still does not resolve the problem what CU for SCOM 2007 R2 are you running and what version of the connector did you install? Did you apply any CU on the connector?
Regards,
-Steve
Wednesday, September 12, 2012 1:32 PMModerator -
Thanks for the help - I also tried to reinstall the MP but it doesn't help.
We use SCOM 2007 R2 CU6
I tried the Connector with and without CU2
Wednesday, September 12, 2012 1:42 PM -
Let me see if I can repro on one of our CU6 environments. What version of Windows and SQL is SCOM running on/with?
-Steve
Wednesday, September 12, 2012 2:12 PMModerator -
We use SQL Server 2008 R2 CU6
on Server 2008 R2 SP1- Edited by Lars Bomsdorf Wednesday, September 12, 2012 2:26 PM
Wednesday, September 12, 2012 2:19 PM -
I installed OM 2007 R2 RTM on Windows 2008 R2 with SQL 2008 R2 then upgraded to CU6. Installed the connector on top of that and it worked as expected so I don't believe it is a CU6 or SQL 2008 R2 issue.
Couple things to verify:
- Did you run the C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2626076\SQLUpdate updates after the CU6 install?
- Did you run the SciConnectorSetup_x64.msi with 'Run as Administrator"?
- When configuring the connector at the end of the install does the certificate get copied properly?
Regards,
-Steve
Thursday, September 13, 2012 4:38 PMModerator -
I verified the following aspects:
- Did you run the C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2626076\SQLUpdate updates after the CU6 install? -> yes
- Did you run the SciConnectorSetup_x64.msi with 'Run as Administrator"? -> yes
- When configuring the connector at the end of the install does the certificate get copied properly? -> yes
Monday, September 17, 2012 6:59 AM -
Not sure what is going on here. Looks like it could be an issue with SQL but I've never run across this error before with the connector. I suggest you open a support case with Microsoft as they can turn on tracing and get into the code a lot easier then we can do on the forums.
Regards,
-Steve
- Marked as answer by Steve Weber [MSFT]Moderator Tuesday, September 25, 2012 11:52 AM
Monday, September 17, 2012 1:32 PMModerator