System.IO.IOException Error in the Configuration Wizard
To make a very long story very short, I’m rebuilding a production server farm from the ground up due to improper sizing of the server root partitions when the project was initiated. Fortunately, I built the farm with full redundancy so I can pull servers out, have them rebuilt, and put them back into production without too much undue interruption. Early on in this process, when we discovered that the C:\ drive on each server was way too small, I tweaked a number of settings to keep various log files and such from filling up the root drives. Specifically, I moved all IIS logging, diagnostic logging, usage analysis and indexes onto the D:\ drive where there was more space.
This solution worked fine until it came time to put one of the rebuilt web front end servers, now with a much bigger C:\ drive, back into the farm. MOSS installed just fine but each time I ran the Configuration Wizard I got a bizarre System.IO.IOException error indicating that the "device is not ready". What really threw me off is that this error occurred during Step 2, when the WFE attempts to connect to the database server to join the farm. After checking all the database connections, validating permissions, using an ODBC connection to verify connectivity, and doing a hundred other things that had nothing to do with the actual problem, one of the network engineers I was working with said to me, just as a random comment, "I wonder if it has something to do with the fact that we no longer have a D:\ drive on this server". Aha!
When you change the log file locations in Central Administration, those settings apply to every server in the farm. Apparently SharePoint checks to make sure those directories exist before it begins the process of provisioning files to the specified locations (wow, someone finally coding something pre-emptive into the stack – I love it!). I knew something was out of whack based on the error description – network connectivity issues rarely show up as System.IO errors – but the fact that it threw the exception during the database connection task really threw me off.
The moral of this story is to make sure your local directory structure is correct before joining a new server to an existing farm. ’nuff said.
This is awow gold rare subject that Iwow gold speak on because I buy wow goldgenerally trybuy wow gold to stay away from itcheap wow gold. I’m don’t follow thecheap wow gold campaigns orworld of warcrft gold feedback of theworld of warcrft gold candidates. I justwow power leveling stick to my “guns”. That old power levelingwestern saying. It’s that time again and yes, we finally get the chance to get rid that “thing” that weworld of warcraft power leveling have as a president and put someone new in house.
I spent 4 hours researching and trying many things, only to scratch my head because I was getting nowhere. Then I ran into your post and my problem was solved.
I am soooo glad you posted this solution!
In my humble opinion this is a stupid error that never should have happened. And in any event MS should provide an error message that makes sense and relates to the “actual” problem.
Thanks again!
In our case, the WFE’s did not have D: drives (but the other farm servers did and had their logs configured to go to D:). However, because the CDROM was D: it was trying there first. I changed the drive letter of the CDROM to E and reran the config wizard. The configuration was successful.
In our case, the WFE’s did not have D: drives (but the other farm servers did and had their logs configured to go to D:). However, because the CDROM was D: it was trying there first. I changed the drive letter of the CDROM to E and reran the config wizard. The configuration was successful.
I tried by changing the cd-rom drive letter from d: to z: but it still give me the error. So I just did a “map network drive” mapping, mapping d: to the \\machine_name\c$ and it went through!
Thanks man, I know it has to deal something with file/read write operation but was not zeroing in to figure out that to write the file to some other location, your posted helped me.
Thank You!
Open the command prompt. Please open it as administrator. By righ clicking program run as administrator
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
Type it in manually
stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword -local
Do this in all servers connected in the farm.
Then do an iisreset\noforce in all servers
Then run SharePoint Configuration Wizard in one server. If this is successful. Attempt adding the server to the farm