MIIS2003 Management Pack Guide

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

MIIS 2003 Management Pack for Microsoft Operations Manager 2000 SP1

Version 1.0

Developed by the MIIS 2003 Product Group, the Microsoft OTG Global Identity Management Team, and EC3, a Microsoft Consulting Services National Practice

Click here to download a copy of this guide

On This Page

Overview of the MIIS 2003 Management Pack
Recommended Knowledge and Skills
Deploying the MIIS 2003 Management Pack
MIIS 2003 Project Phases and Management Roles
Tuning the MIIS 2003 Management Pack
Recommendations for the Network Operations Center
References
Appendix A: Additional Management Packs Recommended for Use with MIIS 2003
Appendix B: MIIS 2003 Events

Overview of the MIIS 2003 Management Pack

Microsoft Identity Integration Server 2003 (MIIS 2003) enables the integration and management of identity information across multiple repositories, systems and platforms. MIIS 2003 augments the Active Directory directory service by providing broad interoperability capabilities including: integration with a wide range of identity repositories; provisioning and synchronizing identity information across multiple stores; and brokering changes to identity information by automatically detecting updates and sharing the changes across systems.

The MIIS 2003 Management Pack for Microsoft Operations Manager 2000 (MOM) monitors MIIS 2003 components and provides information necessary to ensure that:

• All necessary services that support MIIS 2003 are running.

• Identity integration is performing normally and predictably.

• Automation of identity integration does not result in data corruption or loss.

• All events that can adversely affect MIIS 2003 or MIIS 2003managed systems are visible.

The MIIS 2003 Management Pack collects events placed into the event log by MIIS 2003. The management pack contains expert knowledge, including a processing rule for every application event that MIIS 2003 generates. Key events are reported to indicate possible service outages, configuration problems, and degraded performance so that corrective or preventive actions can be taken in a timely manner. For example, the MIIS 2003 Management Pack alerts you to the following conditions:

• Management agent errors requiring administrative intervention

• Events indicating service outages on servers running MIIS 2003

• Management agent warnings indicating configuration issues and connected data source changes

By deploying MOM together with the MIIS 2003 Management Pack, you can monitor servers running MIIS 2003 to maximize the availability of your identity integration solutions.

MIIS 2003 Management Pack Monitoring Scenarios

The MIIS 2003 Management Pack provides monitoring data for each of the MIIS 2003 solution scenarios. This data is sent to a central console that can be monitored by the Network Operations Center. The MIIS 2003 Management Pack provides the following monitoring scenarios for each of the MIIS 2003 deployment scenarios.

Data Source Synchronization

In this scenario, you can use the MIIS 2003 Management Pack to ensure the availability of the MIIS 2003 synchronization solution for keeping multiple identity repositories synchronized. The MIIS 2003 Management Pack:

• Monitors the availability of MIIS 2003 components and services that are required to keep identity repositories synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

Active Directory Global Address List (GAL) Synchronization

You can use the MIIS 2003 Management Pack to ensure the availability of this MIIS 2003 synchronization solution for keeping address lists synchronized across forests. In this scenario the MIIS 2003 Management Pack:

• Monitors the availability of MIIS 2003 components and services that are required to keep identity repositories synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

Active Directory Printer, Site and Subnet Synchronization

You can use the MIIS 2003 Management Pack to ensure the availability of this MIIS 2003 synchronization solution for keeping Active Directory printer, site, and subnet information synchronized across forests. In this scenario the MIIS 2003 Management Pack:

• Monitors the availability of MIIS 2003 components and services that are required to keep the printer, site and subnet information synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

Password Management

In this scenario you can use the MIIS 2003 Management Pack to ensure the availability of a self-service password change tool that is driven by the password management functionality in MIIS 2003. The MIIS 2003 Management Pack:

• Monitors the availability of MIIS 2003 components and services that are required to keep identity repositories synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Notifies the appropriate team when the MIIS 2003 password interface is denying access requests.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

Account Provisioning

You can use the MIIS 2003 Management Pack to ensure the availability of the MIIS 2003 provisioning solution to get new employees productive on day one. Prevent outages in the provisioning solution, which could result in a delay in the revoking of user rights upon employee termination. The MIIS 2003 Management Pack:

• Prevents provisioning and de-provisioning outages.

• Monitors the availability of MIIS 2003 components and services that are required to keep identity repositories synchronized

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

Group Management

In this scenario you can use the MIIS 2003 Management Pack to ensure the availability of the group management MIIS 2003 solution. You can prevent mail routing issues by ensuring the accuracy of mail distribution groups and keep user rights in control by ensuring the accuracy of security groups. The MIIS 2003 Management Pack:

• Monitors the availability of MIIS components and services that are required to keep identity repositories synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

X.509 Certificate Publishing

Use the MIIS 2003 Management Pack to ensure the availability of an X.509 certificate publishing solution. The MIIS 2003 Management Pack:

• Monitors the availability of MIIS 2003 components and services that are required to keep identity repositories synchronized.

• Notifies the appropriate team when management agents are not completing successfully.

• Provides methods for escalating specific issues to the MIIS 2003 administrator or application owner for resolution.

MIIS 2003 Components

Microsoft Identity Integration Sever 2003 works together with other system components, including:

• Connected Identity Repositories, such as:

• Active Directory

• Sun ONE Directory Server

• Exchange 5.5

• Oracle Databases

• Microsoft SQL Server 2000 for the MIIS 2003 database store

• Rules extensions using the .NET Framework

• Microsoft Internet Information Services 6.0 (IIS) (for use with the MIIS 2003 Password Management application, if installed)

• Microsoft Windows operating systems

MIIS 2003 monitoring can be enhanced greatly by installing other available management packs in addition to the MIIS 2003 Management Pack.

Figure 1 illustrates these components and their relationship to the overall identity integration system. For more information about MIIS 2003 infrastructure, see the Microsoft Identity Integration Server 2003 Technical Library at https://go.microsoft.com/fwlink/?LinkId=18080.

Figure 1: MIIS 2003 and Related Components

You might want to investigate the components shown in Figure 1 when troubleshooting an identity integration solution based on MIIS 2003.

For optimal monitoring with MOM, it is recommended that you install the management packs for all the building blocks of the solution you are deploying in addition to the MIIS 2003 Management Pack. For a complete listing of the management packs that you should install with the MIIS 2003 Management Pack, see the Appendix "Additional Management Packs Recommended for Use with MIIS 2003" later in this Guide.

Recommended Knowledge and Skills

To deploy and operate the MIIS 2003 Management Pack, it is recommended that you possess the following knowledge and skills:

• Working knowledge of the monitoring features in MOM.

• Basic understanding of the three MOM design architectures, and knowledge of the specific design architecture that is deployed in your organization. For more information about MOM design architectures, see "Architecture Overview" in the MOM SP1 Deployment Guide at https://go.microsoft.com/fwlink/?LinkId=18083.

• Be familiar with the recommended process for deploying Management Packs as described in "Deploying Management Packs" in the MOM SP1 Deployment Guide at https://go.microsoft.com/fwlink/?LinkId=18083.

• Possess a working knowledge of MIIS 2003. For information about MIIS 2003, including terms and definitions, see Microsoft Identity Integration Server 2003 Help.

Deploying the MIIS 2003 Management Pack

Before deploying the MIIS 2003 Management Pack, review the recommended management pack deployment processes described in "Deploying Management Packs" in the MOM SP1 Deployment Guide at https://go.microsoft.com/fwlink/?LinkId=18083.

The process for deploying management packs involves the following steps:

• Test the management pack in a test environment.

• Pilot the management pack.

• Deploy the management pack.

Do not install management packs directly into your production environment; instead, first install them in a test environment. After you have tested and tuned a management pack, export it from your test environment and import it to your production environment. If you are importing a management pack that is already installed in your production environment, overwrite the existing management pack to ensure that the management packs used in production have been tested and tuned in your test environment. Checklist 1 summarizes the recommended deployment process for management packs.

Checklist 1 Deploying Management Packs

Test management packs in a test environment.

Building a Test Environment

It is important to test the MIIS 2003 Management Pack in a test environment before deploying it to your production environment. The primary purpose of using a test environment for deploying management packs is to:

• Gauge the effect that the management pack will have on your production environment.

• Tune the management pack so that the alerts that are generated are meaningful.

• Scope the volume of monitoring data received so the resulting alerts do not overwhelm the production MOM Database Access Server/Consolidator/Agent Manager (DCAM) and database or your Network Operations Center.

Test Environment Options

There are two approaches that you can use to build a test environment:

• Build a test lab that is a reduced scale model of your production environment, and ensure that the lab is isolated from your production environment. This approach allows you to test the management pack without impacting your production environment. However, this approach requires a significant investment in hardware in order to fully replicate the management agent scenarios.

• Build a MOM test configuration group that is separate from any other MOM configuration groups, and then multihome the management agents in your production environment. This approach provides the advantage of testing the management pack with agents in a production environment, without impacting other production MOM configuration groups. However, this approach requires that you coordinate the agents that are multihomed. While this approach provides a more accurate view of the data that is collected from management agents, it increases the volume of data being sent over your production network.

Testing the MIIS Management Pack during the MIIS 2003 Development Phase

It is recommended that you start using the MIIS 2003 Management Pack early in the MIIS 2003 project cycle by deploying it to the development and test servers that are running MIIS 2003. This provides an opportunity to gauge the number and type of events being sent to MOM from MIIS 2003. The information gathered will assist in completing MIIS 2003 Management Pack deployment checklist items such as:

• Verifying that management agents are installed in the appropriate computer groups

• Verifying that monitoring data is being sent to the MOM Administrator console

• Testing processing rules and analyzing the data

• Tuning the management pack

Installing the MIIS 2003 Management Pack

To test the MIIS 2003 management pack, you must first install it in MOM by using the following procedure.

To install the MIIS 2003 management pack

1. In the MOM administrative console, select Processing Rule Groups and right-click Import Management Pack.

2. In the Import Management Pack window, click Browse.

3. In the Open window, type or browse for the location of the installation media.

4. Select the file named Microsoft Identity Integration Server.akm.

5. Select Replace Existing Management Pack and Backup Existing Management Pack on Upgrade.

6. Click Next to finalize the installation of the MIIS 2003 Management Pack.

Testing the Management Pack

The general recommendations for testing management packs are described in "Deploying Management Packs," in the MOM SP1 Deployment Guide at https://go.microsoft.com/fwlink/?LinkId=18083. For the MIIS 2003 Management Pack, you should also test the management pack rules. To test the rules, use one of the following tools to simulate events written to the event logs:

• If MOM is installed on a server running Windows 2000 Server, use the Logevent.exe event logging tool. Logevent.exe uses the following syntax:

logevent.exe -m \<computer name> -s <severity> -r "<source>" -e <event ID> "<event text>"

Logevent.exe is available in the Windows 2000 Server Resource Kit companion CD.

• If MOM is installed on a server running Windows Server 2003 use Eventcreate.exe instead. Eventcreate.exe is located in systemroot\system32. This tool uses the following syntax:

EVENTCREATE /T <type of event> /ID <event ID> /L <logname>

For example, at the command line type the following:

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">

eventcreate /T ERROR /ID 6063 /L APPLICATION

This generates an MIIS 2003 event with the description "The management agent failed because the management agent was unable to access the file due to insufficient permissions," which is written to the Application log. For a complete list of MIIS 2003 events see the Appendix "MIIS 2003 Events" later in this Guide.

Piloting the Management Pack

Once you have configured the MIIS 2003 Management Pack based on your test results, you can use a pilot program to validate your configuration choices against live data in a pilot environment. Based on the results of testing during the pilot program, you can make any necessary adjustments to your configuration before deploying the MIIS 2003 Management Pack in the rest of your production network.

For the pilot program, be sure to import the version of the MIIS 2003 Management Pack that you exported at the completion of the formal test process, and verify that everything that you tested in your test environment is working as expected. MIIS 2003You should verify the following:

• The DCAM and SQL server are sufficiently sized for your production load.

• Operations processes are sufficient and personnel are trained for monitoring, triaging, resolving, and escalating MIIS 2003 events.

• All reports that are needed for escalation processes can be produced, including information such as hardware and software configuration, MIIS 2003 configuration, and problem descriptions with location and impact.

• The deployment or upgrade process for the MIIS 2003 Management Pack operates successfully.

• Custom thresholds for your environment work as expected.

• Paging and e-mail notification are working properly.

• Credentials that MOM uses are sufficiently privileged to run properly, without being over-privileged.

• The MOM agent is not overloading the CPU on the server running MIIS 2003.

After you complete your pilot program, export the MIIS 2003 Management Pack to back up any changes made and to prepare for deployment to your production environment.

Deploying the Management Pack

When you install the MIIS 2003 Management Pack in your production environment, do not install directly from the installation media; install the version of the management pack that you backed up following your pilot program. If you are upgrading a previously installed version of the MIIS 2003 Management Pack, choose the option to replace the existing management pack entirely. This ensures that the version of the MIIS 2003 Management Pack that you are running in production is the same version that you verified through your testing and piloting phases.

Note: Always back up the MIIS 2003 Management Pack before upgrading; the MOM Import Management Pack Wizard prompts you to do this.

Merging management packs is no longer supported by MOM, because this can lead to inconsistent results. If you have made significant modifications to your management pack and want to retain them, copy the modifications to a different folder before installing the MIIS 2003 Management Pack.

Important: You must copy and not move the custom rules to another location so that the custom rules have a different GUID.

MIIS 2003 Project Phases and Management Roles

The MIIS 2003 Management Pack provides useful information not only for a fully deployed MIIS 2003 solution, but also for an identity integration project that is still in the development phase. During deployment of a new MIIS 2003 solution, the deployment team works with the MIIS 2003 operations team to ensure the team becomes familiar with the MIIS 2003 design. This helps to ensure a smooth transition of ownership following deployment. Once deployment is complete, the responsibility for maintaining the new MIIS 2003 environment passes to the operations team.

Monitoring MIIS 2003 Development

During the development phase of an MIIS 2003 solution, the MIIS 2003 Management Pack might be used to monitor lab servers and analyze trends in events in order to prioritize design changes. In this scenario, the MIIS 2003 design team tests the management pack in an MIIS 2003 lab environment. This testing results in a more finely tuned management pack, which directly contributes to the success of the deployment and operations phases of the MIIS 2003 project.

Monitoring MIIS 2003 Operations

In a production environment, the MIIS 2003 Management Pack can be used to immediately notify MIIS 2003 operators of service outages, and to forward indications of management agent rules errors to MIIS 2003 administrators, who can make configuration changes. Separating management roles in this manner empowers operators to repair most service outages and frees MIIS 2003 administrators from unnecessary involvement.

For more information about MIIS 2003 management roles, see "Defining Roles and Responsibilities for Microsoft Identity Integration Server 2003" in the Microsoft Identity Integration Server 2003Technical Library at https://go.microsoft.com/fwlink/?LinkId=18080.

MIIS 2003 Operator Responsibilities

After deployment of the MIIS 2003 solution is complete, the operation and maintenance of MIIS 2003 and associated SQL servers are integrated into the daily operation of your organization. Operations and maintenance tasks are the responsibilities of MIIS 2003 operators. These tasks include:

• Ensuring that the identity integration and SQL services are always available

• Handling MIIS 2003 daily operations and maintenance

• Reviewing event logs

• Preventing alterations of MIIS 2003 setup or configuration

  If the operators will inspect the server running MIIS 2003, it is important to assign them to security groups with sufficient user rights.

MIIS 2003 Administrator Responsibilities

Operational issues sometime indicate the need for a design change in the MIIS 2003 solution. For instance, management agents might start completing with warnings, or might not complete at all because the network has changed but the MIIS 2003 solution has not. In such cases the operations team is responsible for escalating the problem to an MIIS 2003 administrator.

MIIS 2003 administrators implement policy decisions made by service owners and handle the day-to-day tasks associated with maintaining the identity integration solution and associated SQL services. These tasks include:

• Managing servers that host the identity integration and SQL services.

• Controlling the configuration of metadirectory and SQL settings.

Because MIIS 2003 administrators have access to all shared data, for example shared account and configuration information in Active Directory, take care to assign this role only to trusted individuals in the organization. Ensure that the MIIS 2003 administrators in your organization are familiar with the operational and security policies on your network and understand the need to enforce those policies.

Tuning the MIIS 2003 Management Pack

Once installed, the MIIS 2003 Management Pack requires very little tuning. MIIS 2003 administrators and the MIIS 2003 design team are normally responsible for determining when tuning is needed and implementing the required changes. Common tuning tasks are:

• Disabling event processing rules

• Adding users to notification groups

• Adding company knowledge to the management pack

Disabling Event Processing Rules

By default all MIIS 2003 event processing rules are enabled in the MIIS 2003 Management Pack. Alert processing rules process the events generated by the event processing rules, based on the severity of the events. During testing and piloting you can determine how many events the management pack processes into alerts. If the alerts generated are not of interest, or if too many alerts are being generated, you can use the MOM Administrator console to disable individual events.

Events that indicate service outages should not be disabled. However, if a service outage event is routinely raised in a particular deployment scenario, and the event is deemed to be innocuous, you can disable the corresponding event rule in the management pack. Disabling specific event rules in such cases reduces the amount of noise produced by the management pack.

For information that is helpful for specific event rule tuning, see the Appendix "MIIS 2003 Events" later in this Guide.

Adding Users to Notification Groups

It is important that the right alerts are sent to the appropriate people. The MIIS 2003 Management Pack uses Notification Groups to respond to alerts. The default Notification Group is MIIS 2003 Administrators. You can use the MOM Administrator console to populate the MIIS 2003 Administrators group.

Adding Company Knowledge to the Management Pack

The MIIS 2003 Management Pack includes a knowledge base, which contains information associated with each processing rule. This information embodies knowledge about the meaning and importance of alerts generated by that rule. By default, the knowledge base contains predefined information from Microsoft, to which you can add information specific to your organization. This company knowledge can be stored in MOM, to help operators and administrators respond to those specific issues in the future.

Company knowledge can be gathered during the development, testing, and piloting phases, but you should also continue to gather knowledge after the MIIS 2003 solution is deployed. The following scenarios describe typical situations in which company knowledge is gathered.

Knowledge gathered during development

During development the MIIS 2003 design team encounters events that indicate when rules are not working correctly. The MIIS 2003 design team adds this company knowledge to the events in the MIIS 2003 Management Pack to assist the Network Operations Center in properly escalating events to the MIIS 2003 administrator.

Knowledge gathered during piloting

During the pilot program the MIIS 2003 deployment team encounters events that indicate exceptions in the data that the server running MIIS 2003 processes from the connected identity systems. After consulting with the MIIS 2003 design team it is determined that the MIIS 2003 rules are working as expected and that the issue requires escalation to the owners of the system where the data originated. The MIIS 2003 deployment team adds this company knowledge to the events in the MIIS 2003 Management Pack to assist the Network Operations Center in properly escalating the events to the owners of connected identity systems.

Knowledge gathered after deployment

During normal operations the Network Operations Center encounters events that can be resolved without further escalation. The Network Operations Center adds this company knowledge to the events in the MIIS 2003 Management Pack to assist handling of future similar events.

Recommendations for the Network Operations Center

Ideally, an MIIS 2003 deployment will enforce identity integration rules across disparate identity repositories with little or no intervention required. However, the reality of distributed systems is that events occur that require attention. Because the Network Operations Center is dedicated to monitoring the health of the network on an ongoing basis, it makes sense to delegate to it as much responsibility as possible for routine MIIS 2003 operations. This approach frees the MIIS 2003 administrator and the MIIS 2003 design team to integrate more identity repositories.

Network Operations Center employees will likely have limited knowledge of the MIIS 2003 deployment that they monitor. However, the expert knowledge contained in the MIIS 2003 Management Pack is designed to enable Network Operations Center personnel to handle most issues. This knowledge also helps the Network Operations Center make decisions to escalate issues to the appropriate teams.

Routine MIIS 2003 operations include a number of tasks that the Network Operations Center should perform on a daily, weekly, or monthly basis. You must adjust the frequency of these tasks to meet the needs of your particular environment. Tasks recommended for the Network Operations Center include:

• Verifying communication between MIIS 2003 and MOM.

• Reviewing open alerts.

• Performing MIIS 2003 system recovery.

• Performing MIIS 2003 troubleshooting.

Note: For a baseline of events of interest to the Network Operations Center, see the Appendix "MIIS 2003 Events" later in this Guide. This initial collection of events that should generate alerts for the Network Operations Center is marked "Yes" in the "Network Operations Center" column.

Verify That MIIS 2003 Is Communicating with the MOM Console

Communication failure between servers running MIIS 2003 and the monitoring infrastructure prevents you from receiving alerts so that you can examine and resolve them.

To verify that servers running MIIS 2003 are communicating with the MOM console

1. In the MOM console, click Monitor, All Agents.

2. In the right pane, click the Last Contact column header. This sorts all computers based on last contact time. If the last contact time is greater than five minutes, troubleshoot why the computer is not communicating with MOM.

Review Open Alerts

You should triage all alerts for resolution on a daily basis. Network Operations Center staff can use MOM to view alerts from the MIIS 2003 Management Pack. The alerts are categorized by severity; high priority severities include service outages and critical errors.

Note: You should also pay attention to events that are logged in MOM but do not raise alerts; consider periodically sending a report of these non-alert events to the MIIS 2003 application owner for attention.

Service outage alerts

Service outages are usually the result of a problem with the server running MIIS 2003. The event knowledge base for most alerts contains prescribed actions for remedying the situation. Where possible, and where security permits, the prescribed remedy can be performed by Network Operations Center staff. If the prescribed remedy does not resolve the issue, the service outage needs to be escalated to the MIIS Administrator or Microsoft Product Support Services.

Critical error alerts

Critical errors are usually the result of an MIIS 2003 configuration issue. Where possible, and where security permits, the prescribed remedy can be performed by Network Operations Center staff. If the prescribed remedy does not resolve the issue, the critical error needs to be escalated to the MIIS Administrator.

Reviewing Open Alerts

You should triage all new alerts in the following order of priority:

• Service Unavailable alerts

• Critical errors

• Warnings (optional)

• Informational alerts (optional)

You should not expect that all problems can be resolved in one day or less. Commonly, parts must be ordered, computers must be scheduled for reboot, and so forth. It is important to follow up open alerts to make sure that they are addressed in a timely manner.

To review open alerts

1. In the MOM console, click Monitor, All Open Alerts.

2. Review all alerts that are older than 24 hours to make sure they are addressed in a timely manner.

Perform MIIS 2003 System Recovery

Should a service outage require system recovery, it might be possible to delegate the task to the Network Operations Center. For more information about MIIS 2003 system recovery see the Microsoft Identity Integration Server 2003Technical Library at https://go.microsoft.com/fwlink/?LinkId=18080. Training Network Operations Center staff on this material allows you to either delegate system recovery or utilize Network Operations Center staff for preparatory work.

In the case of a fault tolerant configuration where the database survives but the server running MIIS 2003 does not, the Network Operations Center staff can be tasked with activating the standby server.

In the case of a complete system recovery, the Network Operations Center staff might be tasked only with gathering the hardware and media required to perform the restore.

Perform MIIS 2003 Troubleshooting

If the Network Operations Center staff is familiar with handling first level issues and performing other operations in a Windows Server System integrated server software environment, it might be attractive to delegate more advanced tasks such as performing MIIS 2003 troubleshooting. For more information about MIIS 2003 troubleshooting see MIIS 2003 Help, and see the Microsoft Identity Integration Server 2003 Technical Library at https://go.microsoft.com/fwlink/?LinkId=18080. The troubleshooting information found there can guide Network Operations Center staff through basic MIIS 2003 troubleshooting.

References

Microsoft Identity Integration Server 2003 Technical Library

See the Microsoft Identity Integration Server 2003 Technical Library at https://go.microsoft.com/fwlink/?LinkId=18080 for information about deploying, configuring and tuning the MIIS 2003 Management Pack.

Microsoft Operations Manager

• See the Microsoft Operations Manager User Guide at https://go.microsoft.com/fwlink/?LinkId=18081.

• See the Microsoft Operations Manager Deployment Guide at https://go.microsoft.com/fwlink/?LinkId=18083.

See the following articles in the Microsoft Knowledge base at https://support.microsoft.com:

• Article 296565, "Microsoft Operations Manager 2000 Pre-Installation Checklist."

• Article 296566, "Microsoft Operations Manager 2000 Installation Checklist."

• Article 296569, "Microsoft Operations Manager 2000 Post-Installation Checklist."

• Article 297579, "How to Resolve Multiple Alerts Simultaneously."

Appendix A: Additional Management Packs Recommended for Use with MIIS 2003

MOM provides out-of-the-box base management packs and predefined rules and performance counters to monitor all of the key technologies on which MIIS 2003 relies. Adding the MIIS 2003 Management Pack adds to these capabilities by allowing you to monitor the core aspects of MIIS 2003 itself. You can further enhance monitoring effectiveness by also installing the specific management packs for these technologies. Table 1 lists some of the management packs recommended to use with the MIIS 2003 Management Pack:

Table 1 Additional Recommended Management Packs

Management Pack	Description	Examples of Critical Condition Alerts
SQL Server 2000 MP MIIS 2003 depends on SQL Server 2000 for the database store. Deploy the SQL Server 2000 Management Pack to the server hosting the MIIS 2003 database and use it to monitor the MIIS 2003 database component.	Monitors events placed in the application event log by SQL Server 2000 and 7.0 Highlights events that might indicate possible service outages or configuration problems so you can quickly take corrective or preventative actions Alerts you to warnings and hardware errors, as well as failures in a backup or recovery of the SQL database	SQL Server 2000 becomes unavailable SQL Server 2000 can no longer accept connections SQL Server 2000 process crashes SQL Server 2000 cannot allocate memory for normal operations
Active Directory MP Active Directory is one of many systems that contains identity data. Deploy the Active Directory Management Pack to monitor the impact on replication initiated by MIIS 2003 exports.	Monitors Active Directory events in system and application event logs Includes performance counters to monitor the overall performance of Active Directory Allows you to perform accurate load balancing and capacity planning Alerts you to possible future problems	Active Directory replication failure The Global Catalog is not available Active Directory is not responding The DNS server for a given domain is not available
.NET Framework MP MIIS 2003 can be extended with rules developed using the .NET Framework. Deploy the .NET Framework Management Pack on the server running MIIS 2003 to monitor MIIS 2003 rules extensions.	Monitors the performance of the applications leveraging the .NET Framework Provides basic out-of-the-box monitoring through a series of predefined rules Enables a customized monitoring solution through a large set of rule samples, or templates Helps indicate, through the combination of the predefined rules and customized rules, whether the applications leveraging the .NET Framework are performing at optimal levels by monitoring the performance data produced by the applications
Windows Operating Systems MP MIIS 2003 runs on Windows Server 2003. Deploy the Windows Operating Systems Management Pack to monitor the operating system hosting MIIS 2003.	Monitors Microsoft Windows 2000 and Windows Server 2003 events in the system and application event logs. These events indicate exceptional conditions associated with various aspects of Windows operations Includes several performance counters to monitor the overall performance of the Windows operating system Allows accurate load balancing and capacity planning Allows you to proactively manage your Windows 2000 or Windows Server 2003 operating system configuration, helping increase availability, security, and performance	Primary domain controller has failed indicating a possible system failure Conflict for an IP address on a system indicating network configuration errors An illegal server message block was received indicating a possible break-in attempt Service Account Manager (SAM) database failed to write changes to the database, indicating a failure of the security system Windows 2000 audit log is full indicating that audit data might be lost
Internet Information Services (IIS) MP Self-serve password management can be done using IIS and MIIS 2003. Deploy the IIS Management Pack to the Web server hosting the password self-serve site.	Monitors events placed by IIS and its services in the Microsoft Windows NT, Windows 2000, and IIS event logs Includes a script that polls and tracks the responsiveness of IIS Provides the performance data you need to understand usage trends and perform accurate capacity planning Allows you, through its extensive embedded expertise, to proactively manage your IIS configuration and avoid costly service outages Quickly brings service outages or configuration problems to your attention, increasing the security, availability, and performance of your Web site	Bad or missing links on your site or from a referring site Heavy Web traffic preventing users from connecting to your site Configuration errors or resource shortages affecting service levels Security issues, such as attempts at a buffer overrun attack Active Server Page errors, indicating a possible service outage of an application on your site

Appendix B: MIIS 2003 Events

Table 2 contains specific information for each event produced by MIIS 2003. You can use this information to learn more about the MIIS 2003 events and for help in tuning the MIIS 2003 Management Pack by disabling events. An initial set of baseline events that should generate an alert for the Network Operations Center is marked "Yes" in the Network Operations Center column.

Table 2 MIIS 2003 Events

Event Source	Event ID	Event Type	MOM Rule Name	Event Processing Group	Remedy	Alert Severity	State Before	State After	Alert Tuning Information	Network Operations Center
MIIServer	100	Success	The MIIS operation was successful.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Information	NA	NA		No
MIIServer	2000	Informational		\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Unused	NA	NA		No
MIIServer	2001	Informational	The MIIS service was started successfully.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	None. This represents a healthy state.	Information	MIIS Service Stopped	MIIS Service Started		No
MIIServer	2002	Informational	The MIIS service was stopped successfully.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Start the MIIS service.	Information	MIIS Service Started	MIIS Service Stopped		No
MIIServer	2003	Informational	Retry passes were needed to complete the run.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Information	NA	NA		No
MIIServer	4000	Warning		\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server			NA	NA		No
MIIServer	6000	Error	The management agent failed because the credentials were invalid.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the credentials and configuration for the management agent.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6001	Error	The management agent failed because a connection could not be established to the server.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the connectivity to the server. *Verify the management agent configuration.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6002	Error	The management agent failed because the target file is already open.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the file is not locked by another user or process. *Run the management agent again.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6004	Error	The management agent failed because of an undiagnosed server error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS server. Try restarting the MIIS service. If this doesn't work, escalate to Microsoft Product Support Services.	Yes
MIIServer	6005	Error	The management agent failed because of an undiagnosed MA error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. The MIIS server is fine, but it indicates an unhandled error by the MIIS management agent. Needs investigation. Could be ok.	Yes
MIIServer	6006	Error	The management agent failed because the operation specified is a delta-import and only a full import can be performed.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Run the management agent to perform a full import	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	Should happen only if MIIS management agent has not run for a long while or is new created.	Yes
MIIServer	6007	Error	The management agent failed to start because the domain controller could not be contacted.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the connectivity to the server. *Verify the management agent configuration. Microsoft Knowledge Base Article - 310456. How to Use Portqry to Troubleshoot Active Directory Connectivity Issues	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken. If the event does not repeat, then it was likely caused by a network problem that has since been resolved.	Yes
MIIServer	6008	Error	The management agent failed because the code page specified was incorrect.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the code page configuration for the management agent.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6009	Error	The management agent failed because the configuration specified for the MA is not valid.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS management agent.	Yes
MIIServer	6010	Error	The management agent failed because the type of the file being imported/ exported from does not match the operation.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the log file configuration for this run profile step is correct.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped		Yes
MIIServer	6011	Error	The management agent failed to start because the MA detected that the partition has been renamed.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Refresh and verify the partition configuration for the management agent.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6012	Error	The management agent failed because the MA did not import any objects.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the connected system has objects. *Troubleshoot the management agent discovery process if necessary.	Warning	MIIS Management Agent Running	MIIS Management Agent did not find any changes/ objects to import but is still running.	This could just be because there were no changes and the import file had no data.	Maybe/Yes
MIIServer	6013	Error	The management agent failed because the MA did not import any objects from the input file.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the file was created properly	Warning	MIIS Management Agent Running	MIIS Management Agent Stopped	This could just be because there were no changes and the import file had no data.	Maybe/Yes
MIIServer	6014	Error	The management agent failed because the management agent is not configured for a step type of delta import.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the management agent is configured to perform deltas. If the management agent cannot be configured to perform deltas, then configure the run profile to perform full imports instead of delta imports.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken. This should not happen unless a delta import run-step was setup in run profiles incorrectly.	Maybe
MIIServer	6015	Error	The management agent failed because the management agent has detected that a partition has been deleted.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Refresh and verify the partition configuration for the management agent.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6016	Error	The management agent failed because the management agent has detected that the database schema has changed	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Refresh and verify the schema for the management agent.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6017		The management agent failed because the management agent has detected that a partition has not been configured for the operation.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Refresh and verify the partition configuration for the management agent.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6018		The management agent failed because the management agent was unable to connect to the source database due to insufficient permissions.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify that the account used to access the database has sufficient permissions.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6019		The management agent failed because the management agent was unable to open the database table.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the permissions for the database table.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6050	Error	The management agent failed because of connectivity issues.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify network connectivity before starting the management agent again.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken. This event might correct itself.	Yes
MIIServer	6051	Informational	The management agent failed because the user terminated the operation.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	View the management agent run history for details.	Information	MIIS Management Agent Running	MIIS Management Agent Stopped		No
MIIServer	6052	Error	The management agent failed because the MIIS service was shutdown.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the MIIS service is started before attempting another management agent run.	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped	The MIIS server was shut down while an MA was running.	Yes
MIIServer	6053	Warning	The management agent was stopped because the object limit was exceeded.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Review the configured object limits in the management agent run profile and adjust if necessary.	Warning	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	No
MIIServer	6054	Error	The management agent failed because there were errors reading CD objects.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the health of the connected system and verify network connectivity before running the management agent again.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped		Yes
MIIServer	6055	Error	The management agent failed because the export operation encountered write errors.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the health of the connected system and verify network connectivity before running the management agent again.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped		Yes
MIIServer	6056	Error	The management agent failed because the server stopped.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	This error message should not occur under normal situations. It indicates an error situation not handled by MIIS 2003. 1. View the management agent run history for details. 2. Attempt to restart the MIIS service.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS server.	Yes
MIIServer	6057	Error	The management agent failed because the MA encountered errors.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	This error message should not occur under normal situations. It indicates an error situation not handled by MIIS 2003. 1. View the management agent run history for details. 2. Attempt to restart the MIIS service.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS management agent.	Yes
MIIServer	6058	Error	The management agent failed because the file could not be found.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the run step configuration has specified the correct file. *Verify that the input file is in the management agent's working directory.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6059	Error	The management agent failed because of a problem reading/ writing to a file.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the available space on the drive partition and that the file is not corrupted.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6060	Error	The management agent completed a step with errors.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the health of the connected system and verify network connectivity before running the management agent again.	Error	NA	NA	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken. MIIS might be able to correct the errors on the next run.	Maybe
MIIServer	6061	Error	The management agent was stopped because the error limit of 5000 was exceeded.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	This is a hard coded limit and cannot be configured. View the management agent run history for details.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This alert can be safely disabled in lab environments since frequent rule changes might result in large error counts. This alert should not be disabled in production since rule changes should not be changing often, and well tested rules should not produce large error counts.	Yes
MIIServer	6062	Error	The management agent failed because the disk containing the MaData working directory is full.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Free up disk space before running the management agent again.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes/Maybe
MIIServer	6063	Error	The management agent failed because the management agent was unable to access the file due to insufficient permissions.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the MIIS service account is able to access the file.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6064	Error	The management agent failed because the file could not be opened.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Verify the MIIS service account is able to open the file.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken. In some cases this is not necessarily critical since it could be that an attempt was made to write data to file when the run starts.	Yes
MIIServer	6065	Error	The management agent failed because the MA encountered parsing errors.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	View the management agent history for details.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This alert should not be disabled in production. It indicates a possible change in the connected system that the integration solution was not designed to handle.	Yes
MIIServer	6066	Error	The management agent failed because the MA could not convert the data.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the code page configuration for the management agent. *Verify the file was properly constructed.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6067	Error	The management agent failed because the changelog is not enabled on the target server.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the directory configuration on the target system. *If changelog has been disabled on the target system, adjust the management agent configuration and run profiles accordingly.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped		Yes
MIIServer	6068	Error	The management agent failed because the extension explicitly ended the run.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Review the stack trace in the event log detail. *Verify the metaverse extension is operating as expected. *Contact the extension developer for assistance.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken. The Developer of the extension need to debug. If the problem during debugging can not be found, escalate to Microsoft Product Support Services.	Yes
MIIServer	6069	Error	The management agent failed because the management agent configuration is invalid.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	This error message should not occur under normal situations. It indicates an error situation not handled by MIIS 2003. View the management agent run history for details. Attempt to restart the MIIS service. If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS server. The MIIS server is still running, but the MIIS management agent in question is not likely to work.	Yes
MIIServer	6070	Error	The management agent failed because of embedded null characters in the input file.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the input file and the code page configuration for the management agent. *Verify the file is being created properly.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6071	Error	The management agent failed because of database deadlock.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	This error message should not occur under normal situations. It indicates an error situation not handled by MIIS 2003. View the management agent run history for details. Attempt to restart the MIIS service. If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should NOT be disabled. It indicates an unhandled error by the MIIS server. If the MIIS management agents run sequentially this could correct itself.	Yes
MIIServer	6072	Error	The management agent failed on run profile because the system is out of memory.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Find the process consuming large amounts of memory. *Troubleshoot the process as required.	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6073	Error	The management agent failed because the database or database log file is full.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the available space on the partition hosting the database or increase the database log file size.	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6074	Error	The management agent failed because a changelog with an invalid order was detected on the data source server.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Run the management agent with a step type of full import.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6075		The management agent failed because the connection to the server database was lost.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify that SQL Server is running.	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken. The MIIS server is up, but can not connect to the database.	Yes
MIIServer	6100	Warning	The management agent completed but there were object errors.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	View the management agent run history for details.	Error	NA	NA	This alert can be safely disabled in lab environments since frequent rule changes might result in large error counts. This alert should not be disabled in production since rule changes should not be changing often, and well tested rules should not produce large error counts.	Maybe/Yes
MIIServer	6105	Warning	The management agent completed but objects had exported changes that were not confirmed on import.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*View the management agent run history for details. *Determine how the exported changes are being overwritten in the data source.	Warning	NA	NA	This alert can be safely disabled in lab environments since frequent rule changes might result in large warning counts. This alert should not be disabled in production since rule changes should not be changing often, and well tested rules should not produce large warning counts.	No
MIIServer	6125	Warning	The management agent completed a delta import before completing a full import.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	To ensure the updated rules are applied to all objects, a run with step type of full import should be completed.	Warning	NA	NA	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Maybe
MIIServer	6126	Warning	The management agent completed a delta import or delta synchronization. Since the rules have changed you may want to perform a full import or full synchronization step.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	To ensure the updated rules are applied to all objects, a run with step type of full import should be completed.	Warning	NA	NA	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Maybe
MIIServer	6127	Warning	The management agent completed a delta run. Since the rules have changed you may want to perform a step with full synchronization.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	To ensure the updated rules are applied to all objects, a run with step type of full import should be completed.	Warning	NA	NA	This alert can be safely disabled in lab environments since the rules are frequently changing. This alert should not occur in the production unless rule changes have been planned. If rule changes have NOT been planned, then this alert is an indication of rules changes that might not have been planned and tested properly. Deploying rules in this manner is very risky.	Maybe
MIIServer	6150	Error	The management agent failed. The run step stopped because a required extension DLL is not configured for the MV.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the configuration for the metaverse rules extension in the Identity Manager.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6151	Error	The management agent failed. The run step stopped because a required extension DLL is not configured for the MA.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the configuration for the management agent rules extension in the Management Agent Designer.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6152	Error	The management agent failed. The run step stopped because a required extension DLL could not be loaded.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify that the rules extension is located in the Extensions directory.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6154	Error	The management agent failed. The run step stopped because there are duplicate extension object implementations in the specified .NET assembly.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the extension at the configured location properly implements the management agent or metaverse extension. *Review the MIIS developer reference for samples. *Contact the extension developer for assistance.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6155	Error	The management agent failed. The run step stopped because the extension object in the specified .NET assembly could not be instantiated.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur until the corrective action is taken.	Yes
MIIServer	6156	Error	The management agent failed. The run step stopped because access was denied to the specified extension dll.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the MIIS service account is able to access the extension file.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6157	Error	The management agent failed. The run step stopped because the specified extension dll is not a valid .NET assembly.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify the file at the configured location is an MIIS extension DLL.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6158	Error	The management agent failed. The run step stopped because the specified extension dll could not be found.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	Verify that the rules extension specified is located in the Extensions directory.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6159	Error	The management agent failed because of a problem with the initialize method on the specified extension object.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Review the stack trace in the event log detail. *Verify the extension is operating as expected. *Contact the extension developer for assistance.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6160	Error	The management agent failed because the specified extension could not be loaded as there was a missing dependency.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent		Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6161	Error	The management agent failed because the extension does not contain a class implementing the required (IMVSynchr onization or IMASynchr onization) interface in the assembly.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify the extension at the configured location properly implements the management agent or metaverse extension. *Review the MIIS developer reference for samples. *Contact the extension developer for assistance.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6162	Error	The management agent failed because the rules extension has been updated while a run was in progress.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	To ensure the change rules are applied to all objects a run with step type of full synchronization should be completed.	Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken. The next run of the MIIS management agent should succeed.	Yes
MIIServer	6163	Error	The management agent failed because the specified extension does not implement the required entry point.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Management Agent	*Verify all rules configured as rules extensions are implemented in this rules extension. *Review the MIIS developer reference for samples. *Contact the extension developer for assistance.	Critical Error	MIIS Management Agent Running	MIIS Management Agent Stopped	This event should not be disabled. Multiple events of this type will likely occur before the corrective action is taken.	Yes
MIIServer	6201	Informational	The server encryption keys have been created.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Store a backup of the encryption keys in a secure location. This will be required for server restore operations.	Information	NA	NA		No
MIIServer	6202	Error	The server encryption keys could not be created.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Verify that the service account has permissions to the following registry key: HKEY_LOCAL _MACHINE\ SOFTWARE\ Microsoft\Microsoft Identity Integration Server	Error	NA	NA		Yes
MIIServer	6203	Error	The server encryption keys could not be loaded.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Verify that the service account has permissions to the following registry key: HKEY_LOCAL _MACHINE\ SOFTWARE\ Microsoft\Microsoft Identity Integration Server	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6204	Error	The server encountered an unexpected error when trying to load the database. The database is in an inconsistent state.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6205	Error	The server encountered an error when performing a move for an object.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6206	Error	The server encryption keys could not be found.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Verify that the service account has permissions to the following registry key: HKEY_LOCAL _MACHINE\ SOFTWARE\ Microsoft\Microsoft Identity Integration Server If the problem persists, run setup and restore the encryption keys from backup.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6207	Error	The server encryption keys are corrupt.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Run setup and restore the encryption keys from backup.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6208	Error	The server encryption keys could not be accessed.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Verify that the service account has permissions to the following registry key: HKEY_LOCAL _MACHINE\ SOFTWARE\ Microsoft\ Microsoft Identity Integration Server If the problem persists, run setup and restore the encryption keys from backup.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6209	Error	The service was unable to start because it failed to authenticate to the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6210	Error	The service is stopping because it is unable to authenticate to the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6211	Error	The service was unable to start because the version of the database does not match the version of the product.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	*Verify the correct version of MIIS is installed. *Verify the database was not restored from a previous MIIS version.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6212	Error	The service is stopping because the version of the database does not match the version of the product.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	*Verify the correct version of MIIS is installed. *Verify the database was not restored from a previous MIIS version.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6213	Error	The service was unable to start because it was unable to access the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6214	Error	The service is stopping because it is unable to access the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6215	Error	The service was unable to start because it failed to open the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6216	Error	The service is stopping because it failed to open the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6217	Error	The service was unable to start because the service account does not have database owner permissions.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that the service account has database owner permissions for the Microsoft Identity Integration Server database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6218	Error	The service is stopping because the service account does not have database owner permissions.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that the service account has database owner permissions for the Microsoft Identity Integration Server database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6219	Error	The service was unable to start because a connection to the SQL Server could not be established.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL server is accessible and try and restart the MIIS service.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6220	Error	The service was unable to start because a connection to the SQL Server could not be reestablished.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL server is accessible and try and restart the MIIS service.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6221	Error	The service was unable to start because it failed to connect to the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6222	Error	The service is stopping because it failed to connect to the database.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6223	Error	The server encryption keys do not match the database instance or keyset id.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	The encryption keys should be restored from a backup copy by running setup.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6300	Error	The server encountered an unexpected error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6301	Error	The server encountered an unexpected error in the synchronization engine.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6302	Error	The server encountered an unexpected error in the management agent controller when starting a run.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6304	Error	The server encountered an unexpected memory allocation error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6305	Error	The server encountered an unexpected error searching for connector space objects.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6306	Error	The server encountered an unexpected error while performing an operation for the client.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6307	Error	The server encountered an unexpected error searching for metaverse objects.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6308	Error	The server encountered an unexpected error enumerating management agents.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6309	Error	The server encountered an unexpected error while performing an operation for a management agent.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6310	Error	The server encountered an unexpected error while performing an operation for the joiner.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6311	Error	The server encountered an unexpected error while performing a callback operation.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6312	Error	The server encountered an unexpected error while performing an operation for a rules extension.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Critical Error	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6313	Warning	The server encountered an unexpected error creating performance counters.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Warning	NA	NA		No
MIIServer	6314	Warning	The server encountered an unexpected error renaming performance counters.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Warning	NA	NA		No
MIIServer	6315	Error	The server was unable to backup all modified files in the extensions directory.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	NA	NA		Yes
MIIServer	6316	Error	The server encountered an unexpected error restoring rules extensions.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6317	Error	The computer name in the database does not match the computer name.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Run miisactivate.exe to update the server configuration to match the new computer name.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6318	Error	The server encountered an unexpected error loading the configuration for the management agent.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6319	Error	The server encountered an unexpected error loading the configuration for the metaverse.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6320	Error	The management agent encountered an error. The Terminate method for rules extension threw an exception.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Management Agent Running	MIIS Management Agent Stopped		Yes
MIIServer	6321	Error	The server encountered an error. The Terminate method for metaverse rules extension threw an exception.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6322	Error	The server encountered an error because the connection to SQL Server failed.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Verify that SQL Server is running and that the service account has permissions to access the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6323	Error	The server encountered an error because SQL Server is out of disk space.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Database	Verify the available space on the partition hosting the database.	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6324	Error	The server encountered an unexpected error and stopped.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
MIIServer	6325	Warning	The server encountered a problem while clearing the export error state for objects that are no longer in error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Warning	NA	NA		Yes
MIIServer	6326	Warning	The server encountered a problem while removing placeholder objects that are no longer referenced.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Warning	NA	NA		Yes
MIIServer	6327		The server encountered a problem while processing data.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Error	NA	NA	The next run of the MIIS management agent should fix the problem.	Maybe/Yes
MIIServer	6401	Error	The management agent controller encountered an unexpected error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	Attempt to restart the MIIS service.If the management agent continues to report this error: Search Support for a resolution Contact Microsoft Product Support Services for assistance	Critical Error	NA	NA		Yes
MIIServer	6600	Error	A user was denied access for an operation.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server	*Review the event log details. *Determine if the denied access indicates an attack on the MIIS server.	Security Breach	NA	NA		Maybe/Yes
NA	NA		Core service stopped: The MIIS service entered a stopped state.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Unlikely since this was the scm meaning someone knew what they were doing.
NA	NA		Core service paused: The MIIS service entered a paused state.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Same as above.
Service Control Manager	7031, 7034, 7024, 7023		Unexpected core service failure: The MIIS service terminated unexpectedly.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
Service Control Manager	7022		Unexpected core service failure: The MIIS service hung on starting.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
Service Control Manager	7000		Unexpected core service failure: The MIIS service failed to start due to the following errors	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
Service Control Manager	7038		Core service configuration related failure: The MIIS service was unable to log on with the currently configured password due to the following error.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes
Service Control Manager	7001, 7003		Core service configuration related failure: The MIIS service depends on another service which failed to start or is nonexistent.	\Microsoft Identity Integration Server\\ Microsoft Identity Integration Server 2003\Server		Service Unavailable	MIIS Server Running	MIIS Server Stopped		Yes

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

2003 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.