Share via

Enabling Topology - Completed with Errors (Error Code 2310)

  • Article

An issue I ran into when trying to publish my topology is that it would complete with errors when trying to do the enabling topology step:

Looking at the log, I can see that I'm getting the following errors when it trys to connect to the share:

Error: Error accessing share \\BETA-LS14-SE1.beta.deitterick.com\share - Method failed with unexpected error code 2310..  

Error: Cannot create directory. The path is read only: \\BETA-LS14-SE1.beta.deitterick.com\share\2-ApplicationServer-1\AppServerFiles

In this instance this server was a Standard Edition server and the issue was that I never created the share manually.  Unlike in OCS 2007 R1/R2, for a Standard Edition install, you need to manually create the share before publishing your topology.  This same error will happen for an Enterprise Edition pool if you haven't created the share, but for an Enterprise Edition install, you always had to manuall create the shares ahead of time.

Comments

  • Anonymous
    January 01, 2003
    @Sven Create the share like any other shared folder.  Just make sure that the account that you're running the installer as has share and NTFS rights to Read/Write to the share.  You can take a look at this TechNet article if you need more information (technet.microsoft.com/.../cc770880.aspx).

  • Anonymous
    January 01, 2003
    @Sven What rights got stamped on the share and the folder after you published the topology?  Did it create a folder structure inside of the shared folder?

  • Anonymous
    September 17, 2010
    Same issue is faced by me .......while publishing topology. Getting error like "completed  with errors" during Enabling topology process..

  • Anonymous
    October 12, 2010
    Same issue, how can i create the share manually?

  • Anonymous
    October 12, 2010
    The comment has been removed

  • Anonymous
    October 13, 2010
    The comment has been removed

  • Anonymous
    October 14, 2010
    @dodeitte: Thank's for your help i fixed the problem, the name of my share was wrong.

  • Anonymous
    January 11, 2011
    Thanks!  That helped me out too.  I did not realize that you had to create the share manually.

  • Anonymous
    May 09, 2011
    Error: Error accessing share \waluigi.ca.cheaphomes.comshare - Method failed with unexpected error code 2310..   5/4/2011 12:08:08 PM   Error             └    Error: Cannot create directory. The path is read only: \waluigi.ca.cheaphomes.comshare1-CentralMgmt-1CMSFileStore Where should i call the share file, to share it with lync and where is best location.

  • Anonymous
    July 07, 2011
    It worked for me! Just created a folder in C: drive and shared it. Many thanks! :)

  • Anonymous
    July 14, 2012
    "Lone" your are rock ......its a working solution for me ...thanks a ton

  • Anonymous
    March 14, 2013
    dodeitte u r a msater of genious...

  • Anonymous
    January 06, 2015
    after this option there is showing finish then selct Lync Server deployment wizrd ..step 1 Local user configuration store is not showing done

  • Anonymous
    April 20, 2015
    I have passed this pro plem by uncheck on "select an office web app sever" Step.
    i think everyone should try this.

  • Anonymous
    May 26, 2015
    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.localLyncShare$”.

    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
    RTCUniversalServerAdmin
    RTCUniversalConfigReplicator
    After changing the Share permissions, the topology published successfully.

  • Anonymous
    October 28, 2015
    The comment has been removed

  • Anonymous
    November 01, 2015
    @Siva

    You'll want to check out this log file mentioned in the error you posted:

    'C:Usersadministrator.mydomainAppDataLocalTemp2DbExists-CentralMgmtStore-skypeserver.mydomain.com-[2015_10_28][07_57_25].log'

    It will hopefully contain additional information on why Install-CsDatabase is failing.

  • Anonymous
    February 17, 2017
    Hi Dodeitte. I can really use your help. My issue is I'm getting a 4003 access is denied error enabling the topology. (Insuff_Access_Rights). I have already done the following:1. Created the shared folder called Chat.2. Gave NTFS full access permissions to myself which I'm running the topology builder as and RTCHSUniversalServices, RTCComponentUniversalServices, RTCUniversalServeradmins (which I'm also a member of), and RTCUniversalConfigReplicator.3. I also gave Full permissions for all those users to the Share (chat).4. I've run grant-CsSetuppermission for "dc=mydomain,dc=net" using the Link Management Shell running as administrator.5. I've also run grant-CsOupermision -OU "DC=mydomain,DC=net" -objecttype "user"6. When topology builder finishes publishing it says your topology was successfully publish, but some errors were encountered. I'm afraid of updating the deployment until I get all success across the board.7. Last my share (chat) has a folder created called 4-webservices-1 and it has a few MBs of files beneath it.I think that sums it up. If you can help me I'd appreciate it.

    • Anonymous
      February 19, 2017
      Your best option would be to open a support case. That way support can take a look at the log file generated when you run Enable-CsTopology to get a better idea on where during the Enable-CsTopology the error is occurring. Also, keep in mind that Grant-CsSetupPermission -ComputerOU wants the OU where the Lync/Skype servers are located in AD. From your example above, that wouldn't be a valid OU for computer objects.
      • Anonymous
        February 21, 2017
        So I have gone back and run the grant-cssetuppermission on the ou where the lync servers sit. Then I ran the test-cssetuppermission on that ou and it comes back "true", but still the same issue with error 4003. Is a call to Microsoft my only fix?
        • Anonymous
          February 24, 2017
          Update:The issue was that the share I was using was actually on a clustered file server. I needed to setup the share through the Cluster first. Once I did that then I was able to add the normal permissions and when re-publishing the topology it went right through. I do have a new issue though. It turns out that the persistent chat service starts and then quickly stops. I'm reading about people have to run a patch. Do you have any direct advice there? I'd like to know if running the patch or update requires a reboot. I don't want to knock existing lync users off.Thanks again.