FIX: "MMC has detected an error in a snap-in" when a non-administrator starts SNA Manager in Host Integration Server

Symptoms
Consider the following scenario:
  • In a Microsoft Host Integration Server environment, you have one or more users who are not members of the local Administrators group.
  • You want these non-administrator users to manage your Host Integration Server systems.
  • You add the user accounts to the HIS Administrators groups.
  • The user accounts are configured to let the users log on to the Host Integration Server systems by using Remote Desktop Protocol (RDP).
In this scenario, logged-on users receive the following error message when they start the SNA Manager MMC snap-in:

SNA Manager

MMC has detected an error in a snap-in. It is recommended that you shut down and restart MMC.

This error message window also contains the following options list:

  • Report this error to Microsoft and then shut down MMC.
  • Continue running and ignore errors with this snap-in for the rest of the session.
  • Continue running and always ignore errors with this snap-in, regardless of user or session.
Note This problem occurs on the following versions of Host Integration Server:
  • Host Integration Server 2013 and Host Integration Server 2013 Cumulative Update 1 (CU1)
  • Host Integration Server 2010 Cumulative Update 1 (CU1) or a later version

Resolution
The fix that resolves this problem is included in the following cumulative updates.

Note Because this fix was made to the Configuration tool, it will resolve the issue only if the fix is applied to the installation before you run the Configuration tool. For systems that have already been configured, follow the steps in the "Workaround" section.

Host Integration Server 2013

Host Integration Server 2010

Workaround
If the non-administrator users have to log on to the Host Integration Server systems in order to use SNA Manager, you must add the Create global objects user right to the HIS Administrators group. To do this, follow these steps:
  1. On the server on which Host Integration Server is installed, click Administrative Tools.
  2. Click Local Security Policy.
  3. Expand Local Policies, and then click User Rights Assignment.
  4. Double-click Create global objects in the details pane.
  5. Click Add User of Group.
  6. In the Enter the object names to select text box, enter HIS Administrators.
  7. Click OK.
  8. Restart the SnaBase service on the server that is running Host Integration Server.

    Note When you stop the SnaBase service, you also stop all other Host Integration Server services. This disconnects all active Host Integration Server users.
  9. After the Host Integration Server services are restarted, have the non-administrator user connect remotely to the Host Integration Server computer to start SNA Manager.
The non-administrator user accounts must still be members of the HIS Administrators group to have the appropriate permission to manage Host Integration Server systems. If the non-administrator users log on remotely to different Host Integration Server systems in order to run SNA Manager, you must make the described change on each Host Integration Server system because this change is a local security setting.

If the non-administrator users are not required to log on to the Host Integration Server systems remotely, you can do the following:
  • Add the non-administrator user accounts to the HIS Administrators groups.
  • Install the Host Integration Server Client on the non-administrator user workstations.
  • Run SNA Manager from the workstations in order to manage the Host Integration Server systems.

Note The user must still create the global object rights. Therefore the user must be a member of the local Administrators group on the workstation.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 2929716 - Last Review: 09/30/2015 20:54:00 - Revision: 3.1

Microsoft Host Integration Server 2013, Microsoft Host Integration Server 2010

  • kbqfe kbfix kbexpertiseinter kbsurveynew kbbug KB2929716
Feedback