Tuesday, January 19, 2010

Error: is already routed to the Default zone of another application. Remove that mapping or use a different URL

This happened while trying to re-create a web application after it had been deleted. Looking around I found a few suggestions around this, but none of them would be something I would attempt. For example, one forum thread stated this:

"Open the object table, find an entry that has the same name as the site and delete the row. This worked for me."

Seriously, I don't care if that worked. I would never modify or update anything directly on the database. Let me repeat that, I would NEVER modify or update anything directly on the database. I assume most of you already know why, hence I will not be going into it.

Resolution then? Well, my non-suicidal work around was to get into Central Administration. On the Operations page, under Global Configuration click on Alternate Access Mapping (AAM).

You would probably see a list of entries, one being the very URL that caused the error with it's zone set as Default.

Click on the URL, under the Internal URL column heading to get into the Edit Internal URL page. On the URL protocol, host and port field, append the URL there to something else. For example, I added in a suffix of 123.

url01

url02

Click on OK, now get back to re-creating the Web Application. You would have no errors now and the Web Application will get created as required.

To finish things off, get back into AAM. Click on the relevant URL again. And this time reverse the process. Append the URL protocol, host and port field by setting in back to the original URL. For example, I removed the 123 suffix from mine.

url02

url01