9986 errors Installing SCOM 2007 Agent to Exchange 2003 SP2 Clusters - Day, Brian

Can anyone shed some light on deploying SCOM 2007 Exchange 2003 Management
Pack to monitor Exchange 2003 SP2 clusters? I installed the SCOM agents to
the machines, then the management packs, and then went through the
management pack config wizard.

Everything appeared happy except for the mailbox servers, which are
active/passive clusters. The front-ends, bridgeheads, SRS, public folder
servers had no issues.

The only errors during the config wizard were 8 pairs (We have 8
active/passive clusters) of these.....

Error: Cannot configure the mailbox access account on computer 'Active
Node'. This configuration can only be made after the Exchange MOM event 9986
is registered by MOM.
Error: Cannot configure the mailbox access account on computer 'Passive
Node'. This configuration can only be made after the Exchange MOM event 9986
is registered by MOM.

This pointed me to...

http://www.microsoft.com/technet/prodtechnol/exchange/2003/empconfig.mspx

http://support.microsoft.com/kb/899382

http://technet.microsoft.com/en-us/library/aa996174.aspx


..., but for the life of me I can't figure out what to do at this point. it
seems like all the documentation so far is for MOM 2005 on this issue.

In SCOM none of the mailbox servers show up under Back End Servers. The
agent is installed and lists the boxes as healthy, but it is like SCOM
doesn't realize Exchange is running on them. The servers themselves are
running a mix of Windows Server 2003 Enterprise SP1 and SP2, but any given
cluster is all SP1 or SP2, no mixing.

The articles keep saying "if Exchange is not installed", but Exchange is
definitely installed and running on one of the nodes of each cluster. I
would kind of understand if the passive node fails, but they both do.

The Windows Cluster Mananagement Pack is installed as well, but the Exchange
virtuals aren't showing up anywhere either.

Thanks everyone!

This is a multi-part message in MIME format.------=_NextPart_000_007B_01C7B400. - Lee Chang [MSFT]

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C7B400.A9D7A470
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=response
Content-Transfer-Encoding: 7bit

Hi Brian, sorry about the long delay with this, but we finally have a
workaround for your issue. I've attached a script that will help you set up
your exchange cluster.

1) On the cluster node with where the Exchange virtual server is active, run
the script
2) Move Exchange to the 2nd and 3rd possible target for the Exchange virtual
server, run the script
3) Run the Configuration Wizard and it should complete for all cluster nodes
4) 1st week of July there will be another version of the Exchange 2003 MP
(5000.11) which addresses another unrelated discovery problem

I apologize for the inconvenience. If you have any issues with this fix,
please let us know!

--
Lee Chang
Developer
Log a bug or Feature Request directly to the MOM Product Team by going to
http://www.microsoft.com/mom/feedback. This posting is provided "AS IS" with
no warranties, and confers no rights.

------=_NextPart_000_007B_01C7B400.A9D7A470
Content-Type: text/plain;
format=flowed;
name="Standalone -  Exchange - Publish ExMP Data.js.txt";
reply-type=response
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Standalone -  Exchange - Publish ExMP Data.js.txt"


//*************************************************************
// $ScriptName: "Publish ExMP Data" $
//
// Events created by this script:
// SOURCE		ID		TYPE	DESCRIPTION
// Exchange MOM	10000	error	Failed to publish Exchange Management Pack =
data=20
// Exchange MOM	10001	error	Failed to create the PubKeyPublisher object=20
// Exchange MOM	9986	info		Successfully published Exchange Management =
Pack data=20
//
// $File: Publish_ExMP_Data.js $
//
// $Date: 2004/07/09 10:41:48 $   $Revision: 4 $
//*************************************************************

var EVENT_SOURCE =3D "Exchange MOM";


// Event Constants
var EVENT_TYPE_SUCCESS =3D 0;
var EVENT_TYPE_ERROR =3D 1;
var EVENT_TYPE_WARNING =3D 2;
var EVENT_TYPE_INFORMATION =3D 4;

// Event ID Constants
var EVENT_ID_BASE_STATE_OK =3D 100000;


PublishExMPData:
{
try {
=09
// Other Constants
var SUCCESS =3D 0;

var WshNetwork =3D new ActiveXObject("WScript.Network");
var strServerName =3D WshNetwork.ComputerName;

var PubKeyPublisherObjName;
=09
PubKeyPublisherObjName =3D "EMPKP.PubKeyPublisher";
=09
try {
var objKP =3D new ActiveXObject(PubKeyPublisherObjName);=20
}catch(err){
CreateEvent(EVENT_SOURCE, 10001, EVENT_TYPE_ERROR, "Failed to create =
the object '" + PubKeyPublisherObjName + "'.", "");
break PublishExMPData;
}

var errID;
errID =3D objKP.Publish();

if (errID !=3D SUCCESS)
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish =
Exchange Management Pack data required for performing MAPI logon on =
Exchange server:\"" + strServerName + ".\nError information:\n" + =
HResultToString(errID), "");=20
else
CreateEvent(EVENT_SOURCE, 9986, EVENT_TYPE_INFORMATION, "Successfully =
published Exchange Management Pack data required for performing MAPI =
logon on Exchange server:\"" + strServerName, "");=20
}catch(err){
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish =
Exchange Management Pack data required for performing MAPI logon on =
Exchange server:\"" + strServerName + ".\nError information:\n" + =
HResultToString(err.number) + " " + err.description, "");
}
}


function CreateEvent(strSource, lngEventID, lngEventType, strMsg, =
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, true);
}

function CreateReportEvent(strSource, lngEventID, lngEventType, strMsg, =
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, false);
}

function CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, blnIncScriptName)
{
//var objNewEvent =3D ScriptContext.CreateEvent();

//Append ScriptContext.Name to event if requested
//  if (blnIncScriptName)
//    strMsg =3D strMsg + "\n\nThis event was generated by the script: =
\"" + ScriptContext.Name + "\"\n"

//objNewEvent.Message     =3D strMsg;
//objNewEvent.EventNumber =3D lngEventID;
//objNewEvent.EventType   =3D lngEventType;
//objNewEvent.EventSource =3D strSource;
//if (strComputer !=3D "")
//{
//  objNewEvent.LoggingComputer =3D strComputer;
//  objNewEvent.SourceComputer  =3D strComputer;
//}

//ScriptContext.Submit(objNewEvent);
}



function HResultToString(hresult)
{
return "0x" + (hresult < 0 ? hresult +  0x100000000 : =
hresult).toString(16).toUpperCase() + "(" + hresult +")";
}



------=_NextPart_000_007B_01C7B400.A9D7A470--

I am having the EXACT same problem as indicated in this problem that you - Lester Thoma

I am having the EXACT same problem as indicated in this problem that you
addresses:

I am using SCOM2007,  Exchange management pack 6.0.5000.11, 2 active backend
servers and 1 passive backed server (Exchange 2003).

When I run the Exchange mgmt pack configuration wizard I get the same error
messages-  The 9986 error relates to the PHYSICAL server names of the
clusters.

I assume the script you mentioned will help this out?   How can I obtain it.

Thanks

Lester Thomas

This is a multi-part message in MIME format.------=_NextPart_000_0367_01C7D502. - Lee Chang [MSFT]

This is a multi-part message in MIME format.

------=_NextPart_000_0367_01C7D502.581524A0
Content-Type: text/plain;
format=flowed;
charset="Utf-8";
reply-type=original
Content-Transfer-Encoding: 7bit

I attached the script to the previous post. I'll attach it again here
though, in case the news server has eaten it.

Please let us know if there are any further problems with it.

--
Lee Chang
Developer
Log a bug or Feature Request directly to the MOM Product Team by going to
http://www.microsoft.com/mom/feedback. This posting is provided "AS IS" with
no warranties, and confers no rights.

------=_NextPart_000_0367_01C7D502.581524A0
Content-Type: text/plain;
format=flowed;
name="Standalone -  Exchange - Publish ExMP Data.js (1).txt";
reply-type=original
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Standalone -  Exchange - Publish ExMP Data.js (1).txt"


//*************************************************************
// $ScriptName: "Publish ExMP Data" $
//
// Events created by this script:
// SOURCE		ID		TYPE	DESCRIPTION
// Exchange MOM	10000	error	Failed to publish Exchange Management Pack =
data=20
// Exchange MOM	10001	error	Failed to create the PubKeyPublisher object=20
// Exchange MOM	9986	info		Successfully published Exchange Management =
Pack data=20
//
// $File: Publish_ExMP_Data.js $
//
// $Date: 2004/07/09 10:41:48 $   $Revision: 4 $
//*************************************************************

var EVENT_SOURCE =3D "Exchange MOM";


// Event Constants
var EVENT_TYPE_SUCCESS =3D 0;
var EVENT_TYPE_ERROR =3D 1;
var EVENT_TYPE_WARNING =3D 2;
var EVENT_TYPE_INFORMATION =3D 4;

// Event ID Constants
var EVENT_ID_BASE_STATE_OK =3D 100000;


PublishExMPData:
{
try {
=09
// Other Constants
var SUCCESS =3D 0;

var WshNetwork =3D new ActiveXObject("WScript.Network");
var strServerName =3D WshNetwork.ComputerName;

var PubKeyPublisherObjName;
=09
PubKeyPublisherObjName =3D "EMPKP.PubKeyPublisher";
=09
try {
var objKP =3D new ActiveXObject(PubKeyPublisherObjName);=20
}catch(err){
CreateEvent(EVENT_SOURCE, 10001, EVENT_TYPE_ERROR, "Failed to create =
the object '" + PubKeyPublisherObjName + "'.", "");
break PublishExMPData;
}

var errID;
errID =3D objKP.Publish();

if (errID !=3D SUCCESS)
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish =
Exchange Management Pack data required for performing MAPI logon on =
Exchange server:\"" + strServerName + ".\nError information:\n" + =
HResultToString(errID), "");=20
else
CreateEvent(EVENT_SOURCE, 9986, EVENT_TYPE_INFORMATION, "Successfully =
published Exchange Management Pack data required for performing MAPI =
logon on Exchange server:\"" + strServerName, "");=20
}catch(err){
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish =
Exchange Management Pack data required for performing MAPI logon on =
Exchange server:\"" + strServerName + ".\nError information:\n" + =
HResultToString(err.number) + " " + err.description, "");
}
}


function CreateEvent(strSource, lngEventID, lngEventType, strMsg, =
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, true);
}

function CreateReportEvent(strSource, lngEventID, lngEventType, strMsg, =
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, false);
}

function CreateEventEx(strSource, lngEventID, lngEventType, strMsg, =
strComputer, blnIncScriptName)
{
//var objNewEvent =3D ScriptContext.CreateEvent();

//Append ScriptContext.Name to event if requested
//  if (blnIncScriptName)
//    strMsg =3D strMsg + "\n\nThis event was generated by the script: =
\"" + ScriptContext.Name + "\"\n"

//objNewEvent.Message     =3D strMsg;
//objNewEvent.EventNumber =3D lngEventID;
//objNewEvent.EventType   =3D lngEventType;
//objNewEvent.EventSource =3D strSource;
//if (strComputer !=3D "")
//{
//  objNewEvent.LoggingComputer =3D strComputer;
//  objNewEvent.SourceComputer  =3D strComputer;
//}

//ScriptContext.Submit(objNewEvent);
}



function HResultToString(hresult)
{
return "0x" + (hresult < 0 ? hresult +  0x100000000 : =
hresult).toString(16).toUpperCase() + "(" + hresult +")";
}



------=_NextPart_000_0367_01C7D502.581524A0--

I am having the same problem with a clustered exchange environment. - jrmurphy3

I am having the same problem with a clustered exchange environment. I am not
sure how you are attaching files to this post, but there is attachments in
any of these threads that I can see.

Sorry, silly question, but do i need to run this on the Active, thenfailover, - Nick Madge

Sorry, silly question, but do i need to run this on the Active, then
failover, and run it on the other node as well?

That's correct. - Lee Chang [MSFT]

That's correct.

--
Lee Chang
Developer
Log a bug or Feature Request directly to the MOM Product Team by going to
http://www.microsoft.com/mom/feedback. This posting is provided "AS IS" with
no warranties, and confers no rights.

That's odd. I'm just attaching them using Windows Mail. - Lee Chang [MSFT]

That's odd. I'm just attaching them using Windows Mail.  I'll cut and paste
the whole thing below. I hope it helps!


//*************************************************************
// $ScriptName: "Publish ExMP Data" $
//
// Events created by this script:
// SOURCE  ID  TYPE DESCRIPTION
// Exchange MOM 10000 error Failed to publish Exchange Management Pack data
// Exchange MOM 10001 error Failed to create the PubKeyPublisher object
// Exchange MOM 9986 info  Successfully published Exchange Management Pack
data
//
// $File: Publish_ExMP_Data.js $
//
// $Date: 2004/07/09 10:41:48 $   $Revision: 4 $
//*************************************************************

var EVENT_SOURCE = "Exchange MOM";


// Event Constants
var EVENT_TYPE_SUCCESS = 0;
var EVENT_TYPE_ERROR = 1;
var EVENT_TYPE_WARNING = 2;
var EVENT_TYPE_INFORMATION = 4;

// Event ID Constants
var EVENT_ID_BASE_STATE_OK = 100000;


PublishExMPData:
{
try {

// Other Constants
var SUCCESS = 0;

var WshNetwork = new ActiveXObject("WScript.Network");
var strServerName = WshNetwork.ComputerName;

var PubKeyPublisherObjName;

PubKeyPublisherObjName = "EMPKP.PubKeyPublisher";

try {
var objKP = new ActiveXObject(PubKeyPublisherObjName);
}catch(err){
CreateEvent(EVENT_SOURCE, 10001, EVENT_TYPE_ERROR, "Failed to create the
object '" + PubKeyPublisherObjName + "'.", "");
break PublishExMPData;
}

var errID;
errID = objKP.Publish();

if (errID != SUCCESS)
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish
Exchange Management Pack data required for performing MAPI logon on Exchange
server:\"" + strServerName + ".\nError information:\n" +
HResultToString(errID), "");
else
CreateEvent(EVENT_SOURCE, 9986, EVENT_TYPE_INFORMATION, "Successfully
published Exchange Management Pack data required for performing MAPI logon
on Exchange server:\"" + strServerName, "");
}catch(err){
CreateEvent(EVENT_SOURCE, 10000, EVENT_TYPE_ERROR, "Failed to publish
Exchange Management Pack data required for performing MAPI logon on Exchange
server:\"" + strServerName + ".\nError information:\n" +
HResultToString(err.number) + " " + err.description, "");
}
}


function CreateEvent(strSource, lngEventID, lngEventType, strMsg,
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, strComputer,
true);
}

function CreateReportEvent(strSource, lngEventID, lngEventType, strMsg,
strComputer)
{
CreateEventEx(strSource, lngEventID, lngEventType, strMsg, strComputer,
false);
}

function CreateEventEx(strSource, lngEventID, lngEventType, strMsg,
strComputer, blnIncScriptName)
{
//var objNewEvent = ScriptContext.CreateEvent();

//Append ScriptContext.Name to event if requested
//  if (blnIncScriptName)
//    strMsg = strMsg + "\n\nThis event was generated by the script: \"" +
ScriptContext.Name + "\"\n"

//objNewEvent.Message     = strMsg;
//objNewEvent.EventNumber = lngEventID;
//objNewEvent.EventType   = lngEventType;
//objNewEvent.EventSource = strSource;
//if (strComputer != "")
//{
//  objNewEvent.LoggingComputer = strComputer;
//  objNewEvent.SourceComputer  = strComputer;
//}

//ScriptContext.Submit(objNewEvent);
}



function HResultToString(hresult)
{
return "0x" + (hresult < 0 ? hresult +  0x100000000 :
hresult).toString(16).toUpperCase() + "(" + hresult +")";
}




--
Lee Chang
Developer
Log a bug or Feature Request directly to the MOM Product Team by going to
http://www.microsoft.com/mom/feedback. This posting is provided "AS IS" with
no warranties, and confers no rights.

9986 errors Installing SCOM 2007 Agent to Exchange 2003 SP2 Cl - jrmurphy3

Thanks !

Hi Lee,We have deployed the 5000.11 MP to our SCOM 2007 server. - brothervogo

Hi Lee,

We have deployed the 5000.11 MP to our SCOM 2007 server. We are also using
an Exchange 2003 active-passive 2 node cluster. After installing the agent on
both physical nodes and allowing the agents to act as a proxy we can see the
Exchange virtual servers - all good.

When we have tried to run the config wizard it fails with the dreaded 9986
error but only on one node of the cluster. When we check the registries for
the ExMPLS key it is present on the server that is currently active but not
the passive one.

What is the correct way to complete the registration on the passive node?
Should we failover the resource groups and then try running the wizard again?

Regards,

Vaughan

The script should be run against each physical node - run it as a task. - Robin Drake

The script should be run against each physical node - run it as a task.
The Exch config tool should be run against the virtual node.  The exch
config tool fails to set the correct reg information on the passive node(s)
unless the event 9986 exists in the local OpsMgr event log.   This should be
happening naturally but for clusters you must run the script.   The script
verifies the existence of the EXMPLS com server and posts event 9986.

The proof is that the EXMPLS reg key contains multiple data(x) entries (not
just data0).   With these keys in place the mailflow, mapi logon etc should
will work correctly.

Thanks Robin, I thought that the release of the 5000. - brothervogo

Thanks Robin, I thought that the release of the 5000.11 MP meant you did not
need to run the script, my mistake.

Our Exchange admin is concerned that by running this script we will affect
the provision of support for the Exchange cluster. Are you able to confirm
that this script does not invalidate future Exchange support from MS?

Regards,

Vaughan

I'm obviously not in a position to comment on how Ms will/will not support - Robin Drake

I am obviously not in a position to comment on how Ms will/will not support
Exchange cluster but I can confirm that the script and configuration tool
are harmless.

Script - Thor Kakar

Should this be a .vbs script?