Windows Server

Travis D. Liles · Guest

I am trying to delete an existing MOM-to-MOM connector. Everytime I try to
delete I get and error that "Cleanup for MOM connector on the zone management
server failed. Item not being deleted. Make sure all MOM to MOM connector
services are not running on this Management group:" In the details of the
alerts I recieve an

"Exception of type System.Web.Services.Protoclos.SoapExceptions was thrown.
--> Forwarded id: A027ADAD-C09D-4D36-DD2610C2E526 is invalid, -->
{InvalidOperation_InvalidForwardedID#A027ADAD-C09D-4D36-DD2610C2E526}
--SQL Server error 0 encountered in MCF_DoCleanup
Result Code : 80131501"

The MOM-to-MOM connector service is stopped. I have also set a bookmark to
clear out any existing qued alerts or discovery data and I recieve the above
information everytime I try to delete it. I also tried to uninstall the
connector all together and reboot,. This removes the existing connector, but
when I reinstall the framework and try to create the new connector the old
connecotr reappears.

The Product Connectors tab shows the connector is not initialized and is
also suppended. Restarting the connecotr service and Resuming the connector
has not produced any results.

Any help is greatly apprecitated!

Selma Tanaka [MSFT] · Guest

Hi Travis,
What build are you using on the zone and on the master?
Could you execute the following query and send me the results? Please,
execute it on both databases (zone and master management groups).

use OnePoint
select * from MMPC_Config
select * from MMPC_Forwardees
select * from MCF_Forwardees

Thanks,
Selma

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm .

Travis D. Liles · Guest

Both management groups ( source and destination) are MOM 2005. I am not
currently at the client site, but will forward you the query results when I
recieve them.

Travis D. Liles · Guest

Here are the queries you requested;

Destination Group
ForwardeeId ForwardeeResolutionState ForwardeeName
IsInitialized IsSuspended
------------------------------------ ------------------------
-------------------------------------------------- ------------- -----------
19B3D4F9-DA95-4AF3-AD56-34667296E493 NULL US Connector
1 0
DC31B059-5746-4BC1-99FE-68E97B41C19C NULL UK Connector
1 0

(2 row(s) affected)

Source Group

ForwardeeConfigGroup ForwarderResolutionState
ForwarderGuid ForwardeeGuid
ForwarderMode ForwardeeMode PollingInterval IsSP1
-------------------------------------------------- ------------------------
------------------------------------ ------------------------------------
------------- ------------- --------------- -----
TLWWMOM01 150
3FC78404-3F96-405A-BC4D-436838463C82 A027ADAD-C09D-4D36-AD34-DD2610C2E526 7
2 20 0

(1 row(s) affected)

ForwardeeConfigGroup Forwardee

Priority
--------------------------------------------------
TLWWMOM01
http://tlwmom01:1271/connectorserviceV2.asmx

8

(1 row(s) affected)

ForwardeeId ForwardeeResolutionState ForwardeeName
IsInitialized IsSuspended
------------------------------------ ------------------------
-------------------------------------------------- ------------- -----------
3FC78404-3F96-405A-BC4D-436838463C82 150 EU Connector
0 0

(1 row(s) affected)

Selma Tanaka [MSFT] · Guest

Hi,
It looks like the database on the destination group got corrupted, "EU
Connector" doesn't exist on the database anymore... The error "Forwardee id:
A027ADAD-C09D-4D36-DD2610C2E526 is invalid" means that we tried to cleanup
the forwardeeId 'A027ADAD-C09D-4D36-AD34-DD2610C2E526' from the destination
database, but it failed to find it.

Did someone manually delete "EU Connector" from the destination? Was
OnePoint database deleted and reinstalled? If not, please let me know if you
have the steps to reproduce this incorrect database state.

What we can try to do is to restore the original settings of that connector
on the destination's database based on the query result you've sent me. Then
we initialize the connector at the source management server and see if the
product connector can be removed successfully.

1. on the destination group's database execute:
-- restore and initialize 'EU Connector' entry at the destination
use OnePoint
exec mcf_dosetup 'A027ADAD-C09D-4D36-AD34-DD2610C2E526','EU
Connector',null
exec mcf_doinitialize 'A027ADAD-C09D-4D36-AD34-DD2610C2E526',2

2. on the source group's database execute:
-- initialize 'EU Connector' at the source
use OnePoint
exec mcf_doinitialize '3FC78404-3F96-405A-BC4D-436838463C82',7

After these steps, you should be able to delete "EU Connector" without
errors.
Please let me know if this works for you.

Thanks,
Selma

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm .

Travis D. Liles · Guest

Thanks, I was able to just run the first query and the connector
reinitialized and began working again.

The next issue - The SQL query was run against the wrong DB (the SQL admin
misunderstood my directions the first time) and it added an EU connector to
my US source group. I do not have the option to delete this connector. It
appears as the connectors do on the destination group. It is Supended and
not causing any issues, but I would like to get rid of it. Any suggestions?

Thanks for the help on the original issue

Selma Tanaka [MSFT] · Guest

To delete the incorrect entry from the database execute the following (I'm
assuming you've executed item 1 at the source management group's database):
-- uninitialize 'EU Connector' entry and delete it
use OnePoint
exec mcf_douninitialize 'A027ADAD-C09D-4D36-AD34-DD2610C2E526',2
exec mcf_docleanup 'A027ADAD-C09D-4D36-AD34-DD2610C2E526'

But for future troubleshooting, please, do NOT modify the connector directly
in the database. Those stored procedures are meant to be used only by the
AdminConsole UI and changes to the database are not supported.

Do you know how the connector entry got deleted from the destination
management group's database? If this inconsistent state happens again,
please let us know how to reproduce the error.

Thanks,
Selma

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm .

Travis D. Liles · Guest

that worked, thanks again.

Here are the steps that lead to the Connector error.

I installed KB 883925 because the Destination MOM server was running 100% on
the W3wp.exe process. After the HotFix was installed the 3 Mom-to-Mom
connectors started queing up alerts and discovery data. 2 of the connectors
were fixed when I restarted the Mom-to-MOM connector service. The third
connector would not ever forward the alerts or discovery data. I
suspended/resumed the connector and that did nothing. I also Set a bookmark
to clear the que, then restarted the Mom-to-MOM connector service again.
This also did not work.

I decided to recreate the connector and tried to delete it from the source
group and recived an error (the error is the one I referenced in the original
thread). The Connector was removed from the Desination Groups Admin console
under "Product Connectors" but remained in the Source group's.

Please let me know of you need more detail on anything. I will be glad to
assist.

fiberman · Joined: 03 Feb 2006 Posts: 1

Hi,

I deleted my mom to mom connector to setup a new one.

Now i get this error

There was an error processing an external command by the service.

Message:
System.Data.DuplicateNameException : A DataTable named 'ForwardeeData' already belongs to this DataSet.

Call stack:
at System.Data.DataTableCollection.RegisterName(String name)
at System.Data.DataTableCollection.BaseAdd(DataTable table)
at System.Data.DataTableCollection.Add(DataTable table)
at System.Data.DataTableCollection.Add(String name)
at Microsoft.ServerManagement.MOM.MomConnector.Service.GetConfigurationData()
at Microsoft.ServerManagement.MOM.MomConnector.Service.OnCustomCommand(Int32 command)

how can I fix this

Thanks,

Robert

	Windows Server Forum Index -> MOM	All times are GMT
Page 1 of 1