|
Replies:
5
-
Pages:
1
-
Last Post:
Feb 25, 2010 3:01 AM
by: Damir Pirc
|
|
|
Posts:
10
Registered:
4/22/09
|
|
|
|
OEM Connector - Show log error message
Posted:
Feb 24, 2010 6:46 AM
|
|
|
Hi everyone,
I'm getting this message as red highlighted when I use SMS Trace for Show log option.
24.2.2010 15:22:00:OEMConnector:File MOM\CommonRoutinesConnector.js function RegisterConnectorThatSendsAlertsToMOM_ManagedCode(), connector ReceiveOEMAlertsToSCOMerror: A connector with that connector id or name already exists.
Can somebody explains to me why this is happening and is this a serious error?
Thanks,
Damir
Message was edited by: damir.pirc_1240392491562
|
|
|
Posts:
107
Registered:
2/12/08
|
|
|
|
Re: OEM Connector - Show log error message
Posted:
Feb 24, 2010 11:26 AM
in response to: Damir Pirc
|
|
|
Hi Damir -
I can do a WebEx to resolve this for you ... where are you located ... when are you available (I'm on the West Coast (California) of the US).
Thanx,
Norm.
|
|
|
Posts:
10
Registered:
4/22/09
|
|
|
|
Re: OEM Connector - Show log error message
Posted:
Feb 24, 2010 11:59 AM
in response to: Logan
|
|
|
Hi Norm,
I'm in Croatia, Europe.  
I don't think that webex would be possible because of security policy, but we can comunicate by email. I can provide you with some additional info.
I suspect on de-install problem because OEM Connector existed on the node before upgrade and was de-installed. Maybe some orphans persisted in the database?
Regards,
Damir
|
|
|
Posts:
107
Registered:
2/12/08
|
|
|
|
Re: OEM Connector - Show log error message
Posted:
Feb 24, 2010 12:10 PM
in response to: Damir Pirc
|
 |
Answered |
|
|
|
|
OK. Here's the instructions with a screen shot of the "sender-side" fix ... you need to do the same for the "receiver-side". It's fairly obvious from the screen shots and the file names (look for the two .dat files in the connector's base directory:
In SQL (Server Management Studio), the table/view you want is:
Table: Connector
View: MTV_Connector
Match up the BaseManagedEntityIds in the table and view. Copy out ConnectorId and put it into the [Send|Receive*.dat] files in the connector directory (the * is the column "Name" in MTV_Connector view) ... here's a sample (following the arrows from the upper left ... get into Views (in SQL Management Studio), click on dbo.MTV_Connector, find the "Send" name for your connector, the the Id field, and copy it into the SendSCOMAlertstoblahblah.dat (and save it). Then do the same for the "Receive" name. Then stop the connector. Then start the connector. That should fix it (if you need additional info or assistance, please let us know):
[cid:image001.jpg@01CAB547.9AFB0CD0]
|
|
|
Posts:
10
Registered:
4/22/09
|
|
|
|
Re: OEM Connector - Show log error message
Posted:
Feb 24, 2010 12:17 PM
in response to: Logan
|
|
|
Thanks Norm,
I'll try this first thing in morning and get back to you with info.
Regards,
Damir
|
|
|
Posts:
10
Registered:
4/22/09
|
|
|
|
Re: OEM Connector - Show log error message
Posted:
Feb 25, 2010 3:01 AM
in response to: Damir Pirc
|
|
|
Hi Norm,
this one solved my problem and now I can receive SNMP traps in SCOM Console.
SMS log entry:
25.2.2010 11:16:31:OEMConnector:File MOM\CommonRoutinesConnector.js function MOMMCFFrameworkImplInitialize_ManagedCode(), informational: InitializeConnector ReceiveOEMAlertsToSCOM(ac635e6a-b5b0-4258-b345-3d36ba77df1d) succeeded.
Thank you very match for you help.
Best regards,
Damir
|
|
|
|
Legend
|
|
Guru: 2001
+
pts
|
|
Expert: 751
- 2000
pts
|
|
Enthusiast: 31
- 750
pts
|
|
Novice: 0
- 30
pts
|
|
Moderators
|
|
Helpful answer
(5 pts)
|
|
Answered
(10 pts)
|
|
