The filesystem path for the IIS web site does not point to an NTFS drive. SharePoint requires all web servers in the farm to be configured identically
I am getting below error while configuring WSS 3.0 on app tier. Exception: System.ArgumentException: The filesystem path for the IIS web site does not point to an NTFS drive. SharePoint requires all web servers in the farm to be configured identically. This requirement extends to drive letter names. Anyone has any idea on this? All drives are NTFS. can anyone tell the impact of Removing IIS and installing it again as mentioned in http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/ce14bc0a-63a3-4bbf-958e-11907f9965d1?
August 9th, 2010 4:27pm

Have you checked that someone hasn't moved a site directory in IIS on one of the servers from C to D for example, or your new server is placing IIS on D not C? Its telling you the configuration for that server isn't entirely the same as other app servers. You could uninstall and reinstall IIS, but it usually leaves you with other things out of synch like your asp.net version incorrectly set in IIS. Regards John Timney
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2010 7:41pm

Have you checked that someone hasn't moved a site directory in IIS on one of the servers from C to D for example, or your new server is placing IIS on D not C? Its telling you the configuration for that server isn't entirely the same as other app servers. I would guess that your new app server does not have the same drive letter configuration as your existing servers that contain IIS sites. We recently got this error when adding a new (virtual) WFE server to the farm. In our case, the WFE server only had a C: whereas the other servers had C: D: and E: drive letters. We added D: and E: to the virtual server which resolved the issue (in our case, IIS sites were created in D:). If your IIS sites are contained on a drive other than C: that is likely your problem.Benjamin Athawes Twitter SharePoint Blog
August 9th, 2010 9:10pm

You will need to spend some time determining what it is that is different about that specific server. Given you have a defunct server until you find out what is different you should ask yourself will it take you longer to track down the configuration issue than it would to rebuild it - I'm assuming to some degree here you have a build script to follow for your app servers and base OS, or hav an automated build. It could be a lot of things, like patch levels on the server not being the same as the other app servers if not! A rebuild sounds extreme but its really quite a quick activity. You could always try a reinstall of IIS first, it has been known to correct this type of problem if for some reason the role didn't actually complete configuration correctly. Regards John Timney
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2010 10:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics