Error Cannot Create Directory Because The Path Is Read Only
Contents |
14, 201017 0 0 0 An issue I ran into when trying to publish my topology is that it would complete with failed to save permissions on lync share errors when trying to do the enabling topology step: Looking at the lync 2013 file share permissions log, I can see that I'm getting the following errors when it trys to connect to the share:
Kb2982006
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. Tags Lync Server 2010 Comments (17) Cancel reply Name * Email * Website dodeitte says: October 10, 2016 at 10:10 am @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). Reply dodeitte says: October 10, 2016 at 10:10 am @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? Reply LK says: September 17, 2010 at 3:37 pm Same issue is faced by me …….while publishing topology. Getting error like "completed with errors" during Enabling topology process.. Reply Sven says: October 12, 2010 at 9:07 am Same issue, how can i create the share manually? Reply Sven says: October 12, 2010 at 1:01 pm @dodeitte: Thanks, now i'm fix this problem with the manuell
takes a few minutes. Join Now Ok - so my Group Sales Manager has asked me to get Lync 2013 installed in our environment so he can keep an eye on his sales guys through using presence. Not too bad and not a shabby idea. Problem is, I've built the environment as per; http://www.markc.me.uk/blog/files/LyncStandard.html and the accompanying video.
When I attempt to log in through my test Win 7 Ultimate VM, I get the error of it can't find a Lync Server for my domain, or there's an issue with DNS. I feel the root cause of these errors are one in the same however, I've added Forward Lookup Zone A records for lyncdiscover, lyncdiscoverinternal, meet, SIP and https://blogs.technet.microsoft.com/dodeitte/2010/09/14/enabling-topology-completed-with-errors-error-code-2310/ the server FQDN to all point to the same place; the Lync 2013 server's IP address. I'm at a loss, mostly due to my Lync knowledge is less than a lot and the Train Signal video's I've got send me to sleep before they actually tell me anything. Does anyone else have some ideas/another walk through I can utilize/steal for this project? Reply Subscribe RELATED TOPICS: Lync 2013 questions... Lync 2013 Federation? Lync 2013 suddenly won't connect - https://community.spiceworks.com/topic/433222-lync-2013-standard-edition multiple users   7 Replies Ghost Chili OP tfl Jan 19, 2014 at 7:53 UTC This is almost certainly a DNS error. In general - you should have an SRV record of the form: _SipInternalTLS._Tcp.R2 SP164bits *2 2 Lync Server 2010 standard Lync Server 2010 SQL included 3 Lync Client 2010 Lync client 4 Silverlight addon Desgin https://colinzhong.blogspot.com/2014/06/mircrosoft-lync-2013-installation-guide.html Before install OS 安装步骤 Install DC Install IIS Start -> All Programs -> Administrative Tools -> Server Manager Web Server (IIS) Services Add Required Role Services close Install http://unix.stackexchange.com/questions/111970/read-only-file-system-error-while-creating-a-directory Active Directory Install Active Directory Domain Services 2. dcpromo 3.next 4.New a domain 5.Set FQDN to nest.com(gsta@1234) 7.DNS Server 8.static ip addresses are required 9.yes 10. error cannot 11.password 12.next 13.Installation success Join test.com Install Active Directory Certificate Services 2.Tick Certificate Authority Certification, Authority Web Enrollment, Online ResponderCerticate Enrollment Policy Web Service 3.Choose Enterprise Install Lync Server 2010 Join domian Change hostname to "Nest-srv-lync" and join Nest.com Install Lync Server 2010 1, login 2008 server using domain administrator 2, install framework 4.5 download: http://www.microsoft.com/en-au/download/details.aspx?id=30653 error cannot create 3, install powershell 3.0 http://go.microsoft.com/fwlink/?linkid=268538&clcid=0x804 4, server manager add feature remote server administration tools 5,install windows identity foundation http://go.microsoft.com/fwlink/?linkid=204657&clcid=0x804。 Windows6.1-KB974405-x64.msu 六, open Lync Server install file install Microsoft Visual C++ 2008 redistributable 2. Preare Active Directory 3.Preare Schema Install successes 4. prepare current forest, local domain 5."Preare Current Domain" Add DC member to group CSAdministrator. Back 6. "Preare first Standard Edition server. Install SQL 2008 Express and Lync Server. Will take a while. 7.Install Topology 8.Build up Topology. Start->All Programs -> Microsoft Lync Server 2010 ->Lync Server Toplogy Builder. Choose "New Topology" MyTopology.tbxml 9.Setup SIP Domain 10.First side 11.Install pool 12. The prefix of FQDN should be same as hostname: Nest-srv-Lync.nest.com 13.Choose services 14. roles 15. "Fileshare" shared directory。 16.Edit topology 17.Access url is https://admin.test.com Manually create director share (user share as the name which will affect lync "setup or remove lync server components"),otherwise will get an error after publishing topology, like: Error: Cannot create directory because the path is read only: \\Nest-srv-Ly
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Read-only file system error while creating a directory? up vote 2 down vote favorite I have one of our production Ubuntu machines set up by PRODUCTION Unix team here in our company, but somehow when I am doing like this - root@machineA:/test01# ls -lt ls: reading directory .: Input/output error total 0 It is giving me an error. And if I am trying to create any directory in the promary01 directory, it is giving me an error as well - mkdir: cannot create directory `/test01/primary': Read-only file system Any thoughts on what is wrong? I am thinking to fix this myself instead of telling UNIX PROD guys as I have root access, and I will be able to learn something new as well. Maybe it was not mounted properly? filesystems share|improve this question edited Apr 27 at 18:11 Anthon 47.4k1462125 asked Feb 1 '14 at 8:15 lining 79892337 what is the output of cat /proc/mounts ? –SHW Feb 1 '14 at 9:00 It may be a good idea to do a filesystem check (e2fsck), which may happen automatically if you reboot the system. –brm Feb 1 '14 at 10:29 @SHW: This is what I get on the console from cat /proc/mounts - /dev/sdb /test01 ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0 /dev/sdc /test02 ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0 –lining Feb 1 '14 at 17:23 It's clear that I/O error has to do with faulty disc, as said by Timo. And I guess, denial of directory creation is because, you have mounted the test01 as Read-Only. remount it as sudo mount -o remount,rw /test01 –SHW Feb 3 '14 at 5:15 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted Input/Output errors are more an indication of faulty discs than of unproperly mounted filesystems. I have seen that mostly with USB drives, but also with IDE, SATA and SCSI. You should definitely ask your support to get a look at that and replace. share|improve this answer answered Feb 1 '14 at 9:31 Timo 3,9371024 1 Indeed. My experience has