The web application could not be extended because an unused zone could not be found.  Unextend the web application from the zone
hi , i am trying to extend my current sharepoint site but even for default zone it gives me error "The web application could not be extended because an unused zone could not be found. Unextend the web application from the zone that you intend to use for the new IIS web site before performing this operation"
October 10th, 2007 7:14am

Tri this How-To: http://technet2.microsoft.com/Office/en-us/library/be9d31d2-b9cb-4442-bfc6-2adcdbff8fae1033.mspx?mfr=true
Free Windows Admin Tool Kit Click here and download it now
October 30th, 2007 12:14pm

hi shekhar, To me it seems that the zones on which the Sharepoint site can be extended are exhausted. Why don't u try the option of removing the "SharePoint site from a web application" in central administrationsite and then try again extending the web app... Hope this helps.
October 30th, 2007 12:23pm

After removing it from from Central Administration i had lost my site and thank god i was doing it on testing server. Any Other option or trick and how we can trace what the exact problem cause it does'nt showup in event viewer also. ?
Free Windows Admin Tool Kit Click here and download it now
March 5th, 2011 6:59am

After removing it from from Central Administration i had lost my site. Here is some more option to trace the error. When an error occurs within Microsoft SharePoint Foundation 2010 a Correlation ID will be displayed in the error message: This Correlation ID is logged within the SharePoint log files and you can use it to find out more details about the error that occurred. The two pieces of information you will need from the error message above are the Correlation ID and the date and time of the error. Once you have those two pieces of information, browse to the SharePoint log files on your SharePoint server located at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS The log files will be labeled with a date time stamp so find the one that corresponds to the time frame of the error and then open this log file in Notepad (or the text editor of your choice) and search for the Correlation ID. You will probably find it listed in several places, from the beginning GET request to when the error occurred, and finally to when the logging of correlation data stops. Of course you are probably most interested in the error message but there will be more information in the log associated with the Correlation ID to help you find the root cause of the error. Any Other option or trick and how we can trace what the exact problem. ?
March 5th, 2011 2:57pm

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

Other recent topics Other recent topics