How can I fix parser Error in ASP.NET?

How Can I fix the Microsoft Lync 2013 Installation Topology Error?

• If you encounter the Microsoft Lync 2013 Installation topology error, here is your fix. http://www.fortressitx.com/blog/microsoft-lync-topology-file-share-error-fix/ Today, the FortressITX engineers came across an issue with Microsoft Lync 2013. While installing the program, a topology error peaked their interest. To fix the error our engineers did what everyone does, search for the fix on Google however, to their dismay, they could not locate a proper fix. Well, instead of moaning about it, our IT experts set to work and fixed the error. Read below to find a quick fix to this common Microsoft Lync 2013 Enabling Topology error. Before we get going, here is the http://windowspbx.blogspot.com/2012/07/step-by-step-installing-lync-server.html most people are following to install Microsoft Lync 2013. The walk-through is fine until users try and publish the topology. When trying to publish Lync Topology, the user receives the following errors under the File Store (YOURDOMAINAME). ACL Error: Access permissions error Error:Failed to save permissions on (YOUR SHARED FOLDER) ACL Error: Failed Adding “Access Write” permission for “RTCHS Universal Services” on “share”. Access control list (ACL) might fail on UNIX files shares. Refer to the deployment guide to manually set the ACLs in the file share. And now for the quick fix: 1. Give Full Control access on the SHARE tab, not the SECURITY tab to the following groups: 2. Once inside the SHARE tab, open ADVANCED SETTINGS: 3. Once inside ADVANCED SETTINGS, open PERMISSIONS: 4. Add the full access permissions to the following groups: RTCHS Universal Services RTC Component Universal Services RTC Universal Server Admins RTC Universal Config Replicator 5. Choose OK.6. Publish the topology again All set.

• Answer:

  The errors generated in the topology log are very generic: These errors have no detail and are useless in determining what the problem is. This is Lync server 2013 installed on Server 2012 Std. Thoughts?