SCOM 2012 r2
SCOM CONNECTOR 4.3
Catalyst Container 3.4.1
Q: "The connector is online, but all the SCOM entities appear in CA SOI as "Unknown"
A: Please check for the following message in the ifw.log(s) on the connector
System.Collections.Generic.KeyNotFoundException -- The given key was not present in the dictionary" message
If there is an occurrence of this message there is a known Microsoft problem in the SCOM SDK.
Microsoft is aware of this issue and is working on a fix. It is recommended that you contact Microsoft Support
to see if any pre-release versions of the fix can be made available to you.
Yes, my description is the same.
Still not working for me.
Though, Connector description show as:
"Catalyst 3.x connector running in Catalyst node HOSTNAME_CatalystConnector"
Does yours also show the same as mine?
The binaries was for v4.3. When you have v4.4, no new binaries are required.
I applied connector version 4.4 and now the "Unknown" CIs are gone. BUT, I'm not seeing anything else either. You mentioned that you got some new binaries from CA, what are they?... so that I can refer it back to CA support. I have just opened a ticket with them, they have yet to respond.
My environment looks the same as mentioned above. I had the same issue. Logged a call with CA and got some new binaries. Applied that and it worked.
I then saw that there is a new MS SCOM connector available. Downloaded the new MS SCOM connector yesterday and installed it. Don't have the issue of 'Unknown' CIs. The new SCOM connector version is 4.4
It didn't work for me. My environment:
Any help on this would be great.
The connector system for the scom connector.
Am 18.05.2016 um 07:20 schrieb indothai <firstname.lastname@example.org<mailto:email@example.com>>:
CA Communities <https://communities.ca.com/?et=watches.email.document_comment>
Tech Tip : The connector is online, but all the SCOM entities appear in CA SOI as "Unknown"
new comment by indothai<https://communities.ca.com/people/indothai?et=watches.email.document_comment> View all comments on this document<https://communities.ca.com/docs/DOC-231160421?et=watches.email.document_comment#comment-233937845>
I'm also having the same problem. Which system did you restart?
Got this error today, we have restarted the whole system that fixed the problem for us. It was a new installation Catalyst based SCOM Connector.
(same versions as mentioned by paul)