Lync 2013 – Enabling Topology Completed With Errors

I recently started building a Lync 2013 Pilot Pool alongside my Lync 2010 deployment. When publishing the topology I got the following errors:

_Publishing in progress
_

_Failed adding “AccessWrite” permissions for “RTCComponentUniversalServices”
Failed adding “AccessRead” permissions for “RTCComponentUniversalServices”
Failed adding “AccessWrite” permissions for “RTCHSUniversalServices”
Failed adding “AccessRead” permissions for “RTCHSUniversalServices”
Failed adding “AccessWrite” permissions for “RTCUniversalServerAdmins”
Failed adding “AccessRead” permissions for “RTCUniversalServerAdmins”
_

_Access control list (ACL) might fail on UNIX file shares. Refer to the deployment guide to manually set the ACLs in the file share.
_

When the Publishing wizard is complete you see the error:

_Enabling Topology… Completed with errors
_

When you view the log file you see the following errors for the Lync File Share:

ACLError: Access permissions error.

Error: Failed to save permissions on “\server.domain.localLyncFS$”.

Updated Fix: When running Topology Builder, right click and “Run As Administrator”. Thanks to Dave in the comments below.

To fix this I had to add the following groups to the Share (Not NTFS) permissions on the Lync File Share. I had to do this even though Everyone had Full Control on the Share Permissions. Topology Builder would fail publishing the topology until I added these groups on.

RTCComponentUniversalServices
RTCHSUniversalServices
RTCUniversalServerAdmins

After changing the Share permissions, the topology published successfully:

10 comments

password1! 17 May 2013 at 09:04

I encounter the same problem. I don't know why the "Everyone" group permission is not working perhaps something to do with the grouping permission in the grouping setting in AD.

Jessica G. 9 August 2013 at 17:15

This post resolved my problem, also I had to add another group RTCUniversalConfigReplicator.

Thanks for the post.

Jessica

Chris Hayward 14 August 2013 at 08:22

Thank you for the info Jessica, it's a very odd problem!

Andy Liu 6 September 2013 at 05:39

You also need remove the NTFS right if you put those groups in.

Dave D. 13 September 2013 at 07:01

After trying a bunch of published solutions including the ones above and all not working, I found that opening the Topology Builder with a right-click "run as administrator" helped resolve this for me.

Chris Hayward 13 September 2013 at 07:27

Thanks for the info Dave! Sounds like a much easier solution.
David 1 May 2014 at 15:39

Very good answer, thank you!
I confirm it works
Sam Anim 7 April 2016 at 22:53

You are 100% right Dave, I just did that and it work, good answer Dave

mohammad 27 July 2015 at 11:44

my problem is about enable cs-topology :
<< a trusted service with the type"qos" and the fully qualify domain name ---- was found for a previouse server version .

gayjosi 24 September 2015 at 22:04

tnks man, but i need to also add:
RTCComponentUniversalServices
RTCHSUniversalServices
RTCUniversalServerAdmins
RTCUniversalConfigReplicator

Comments are closed.