UTIM access denied error 0x80070005

[rrhodes]

Recently replaced Unity 5.x server hardware and OS (OS upgraded from 2000 to 2003) and after DiRT restore cannot access UTIM while Unity is running. Attempts to launch UTIM while Unity is running result in error message "Failed loading the MuiHRegistry component. Error 0x80070005. Access is denied." In order to launch UTIM Unity has to be stopped.

Any ideas?

[Brad Magnani]

Robert,

I would take a look at this link:

http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K11648085

and also make sure all of your services are running under the proper accounts per the installation guide:

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html

Hope that helps,

Brad

[Rob Huffman · Accepted solution]

Hi Robert,

Just to add a note to the great tips from Brad (+5 points here Brad :)

You may be hitting this bug;

CSCsi54038 Bug Details

UTIM Failed Loading the MIURegistry Component Error 0x800705

Symptom:

UTIM will not start while Unity is running

Error message displayed with text:

"Failed loading the MiuRegistry component. Error 0x8007005. Access is denied

In order to use the Telephony Integration Manager your Windows account must be a Cisco Unity administrator and a member of the Administrators group on this computer."

Conditions:

Any version of Unity software installed on Windows 2003 operating system.

Workaround:

Option 1. Stop the Unity services, UTIM launches without problem

Option 2.

- Use Process Explorer (available from MS) to change the ownership and access to MTXMiuRegistryReadWrite object.

- Launch Process Explorer and select AvCsMgr.exe.

- In the bottom pane, locate Mutant object \BaseNamedObjects\MTXMiuRegistryReadWrite.

- Double click and change the security settings for this object so that the Local Administrators Group is the owner and has access.

- UTIM should now start.

Additional Comments:

If the problem persists after a restart of Unity or the server, the local security policy likely overrides the default behavior and doesn't make the Administrators Group the default object owner.

To change this, reassign the local (or DC) security policy, Security Option "System objects: Default owner for objects..." to Administrators.

On Windows 2003 "not defined" should act the same as Administrators.

Note this requires rebooting the Unity server

Hope this helps!

Rob

[rrhodes]

Excellent, thanks.