Article ID: 889017 - Last Review: July 24, 2007 - Revision: 3.4 You receive an exception error when the MCF tries to insert alerts in MOM 2005, or event ID 10042 is written to the Application log when you use the MMPC
On This PageSYMPTOMSWhen the MOM Connector Framework (MCF) tries to insert alerts in Microsoft Operations Manager (MOM) 2005, you receive the following exception error: System.Web.Services.Protocols.SoapException: Exception of type System.Web.Services.Protocols.SoapException was thrown. --> ServerRoleInstance cannot be NULL or an empty string when ProblemState is set to Active or Inactive.
Parameter name: ServerRoleInstance at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at ConnectorServiceV2.InsertAlerts(Guid registrationId, AlertInsert[] alerts) Source: MOM to MOM Connector
CAUSEThis problem occurs if the MCF generates a state alert where one of the following conditions is true:
When you use the MMPC, the alert prevents the forwarding of all alerts until a set bookmark is called to clear alerts from the cache. However, using a set bookmark causes other alerts to be removed before forwarding has occurred. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft Operations Manager 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:905416
(http://support.microsoft.com/kb/905416/
)
How to obtain the latest Microsoft Operations Manager 2005 service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart requirementYou do not have to restart your computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Date Time Version Size File name -------------------------------------------------------------- 18-Nov-2004 21:07 6.0.2800.1106 133,352 Mom2005-rtm-kb889017-x86-enu.exe Date Time Size File name ------------------------------------------- 17-Nov-2004 15:10 142,848 Q889017.msp 18-Oct-2004 04:52 118,784 Update~1.exe Installation instructionsYou must install this hotfix on each computer that meets both of the following conditions:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Operations Manager 2005 Service Pack 1. MORE INFORMATION
For more information about other problems that are resolved by Microsoft Operations Manager 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
905420
(http://support.microsoft.com/kb/905420/
)
List of bugs that are fixed in Microsoft Operations Manager 2005 service packs
For additional information about standard terminology used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
