The literal cause of the error "Another blog or Google Site is already using this address." is that the Google Sites service is mapped to the address in question, in the Google domain services mapping database.
Some help articles published on the Internet imply that Sites mappings are the only cause of this error. This misconception creates some of the confusion associated with the error. Sites is not the only service in the services mapping database - but it is the only service with web address mappings.
The Sites service contains both service address, and web address, mappings - and both mappings can cause this problem. This oddity creates complexity, and makes a linear check list impossible, when using Google Apps to clear the error - as well as diagnosing the error, in a typical dialogue in Blogger Help Forum: Something Is Broken.
When the Sites service is suspected as the cause of "Another blog or Google Site is already using this address.", one must check both the Service Address Mapping, and the Web Address Mappings, in the Sites service.
Note that the presence of the mappings is not directly affected by the presence of the service wizards, on the desktop of the Google Apps account which you are using. Neither deleting the Apps account, nor uninstalling a given service wizard from the desktop, will immediately reset the mappings for that service, from the database.
If not present on the desktop, the Sites service must be first installed and activated, using the dashboard "Get more apps and services" link.
The Sites service address mapping, like all other services, can be examined and reset using the CustomURL form in Google Apps, as well as "Change URL" in the "General" tab, in the Sites Settings menu. The web address mappings can only be examined and reset using the "Web Address Mapping" tab, in the Sites Settings menu.
If a Sites mapping is not the cause of your problem, Sites won't have a mapped address, in "Web Address Mapping". You will then need to check other settings, in Control Panel / Google Apps.
A Sites service address mapping, like other service address mappings, can sometimes be diagnosed in a simple "302 Moved Temporarily" redirect, in a typical HTTP trace.
A Sites web address mapping is not always so easy to diagnose - and may be the reason behind the fact that some HTTP traces end with the blog owner reporting "Another blog or Google Site is already using this address.", and an HTTP trace simply showing the generic 404 Not Found.
A Sites "Web Address Mapping" can include an address which is mapped outside Google Apps. This creates a mapping which can't be managed using Google Apps.
Some help articles published on the Internet imply that Sites mappings are the only cause of this error. This misconception creates some of the confusion associated with the error. Sites is not the only service in the services mapping database - but it is the only service with web address mappings.
The Sites service contains both service address, and web address, mappings - and both mappings can cause this problem. This oddity creates complexity, and makes a linear check list impossible, when using Google Apps to clear the error - as well as diagnosing the error, in a typical dialogue in Blogger Help Forum: Something Is Broken.
When the Sites service is suspected as the cause of "Another blog or Google Site is already using this address.", one must check both the Service Address Mapping, and the Web Address Mappings, in the Sites service.
Note that the presence of the mappings is not directly affected by the presence of the service wizards, on the desktop of the Google Apps account which you are using. Neither deleting the Apps account, nor uninstalling a given service wizard from the desktop, will immediately reset the mappings for that service, from the database.
If not present on the desktop, the Sites service must be first installed and activated, using the dashboard "Get more apps and services" link.
The Sites service address mapping, like all other services, can be examined and reset using the CustomURL form in Google Apps, as well as "Change URL" in the "General" tab, in the Sites Settings menu. The web address mappings can only be examined and reset using the "Web Address Mapping" tab, in the Sites Settings menu.
- Select the "Web Address Mapping" tab, in the Sites Settings menu.
- Select all addresses mapped, and click on "Delete Mapping(s)".
- Click on "Yes" in the "Are you sure" popup.
If a Sites mapping is not the cause of your problem, Sites won't have a mapped address, in "Web Address Mapping". You will then need to check other settings, in Control Panel / Google Apps.
A Sites service address mapping, like other service address mappings, can sometimes be diagnosed in a simple "302 Moved Temporarily" redirect, in a typical HTTP trace.
Sending request: GET / HTTP/1.1 Host: www.letthykingdomcome.com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 Referer: http://www.rexswain.com/httpview.html Connection: close • Finding host IP address... • Host IP address = 74.125.129.121 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending request... • Waiting for response... Receiving Header: HTTP/1.1·302·Moved·Temporarily(CR)(LF) Content-Type:·text/html;·charset=UTF-8(CR)(LF) Location:·http://sites.google.com/a/letthykingdomcome.com/ sites/system/app/pages/meta/domainWelcome(CR)(LF)
A Sites web address mapping is not always so easy to diagnose - and may be the reason behind the fact that some HTTP traces end with the blog owner reporting "Another blog or Google Site is already using this address.", and an HTTP trace simply showing the generic 404 Not Found.
Sending request: GET / HTTP/1.1 Host: www.markhamdesign.co.uk User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 Referer: http://www.rexswain.com/httpview.html Connection: close • Finding host IP address... • Host IP address = 216.239.32.21 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending request... • Waiting for response... Receiving Header: HTTP/1.1·404·Not·Found(CR)(LF)
A Sites "Web Address Mapping" can include an address which is mapped outside Google Apps. This creates a mapping which can't be managed using Google Apps.
If you own a domain and have access to change the CNAME record, you can map any site created in Google Sites outside of Google Apps (for example, sites.google.com/site) to a custom URL
Sending request: GET / HTTP/1.1 Host: www.medtechpedia.com User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 Referer: http://www.rexswain.com/httpview.html Connection: close • Finding host IP address... • Host IP address = 74.125.129.121 • Finding TCP protocol... • Binding to local socket... • Connecting to host... • Sending request... • Waiting for response... Receiving Header: HTTP/1.1·200·OK(CR)(LF) <body·xmlns="http://www.google.com/ns/jotspot"·id="body"·class="·en············">(LF) <script·src="//www.gstatic.com/caja/5246m/caja.js">·</script>(LF) <script·src="http://www.gstatic.com/sites/p/926884/system/js/jot_caja.js">·</script>(LF) <div·id="sites-page-toolbar"·class="sites-header-divider">(LF) <div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-status"·class="sites-status"·style="display:none;"><div·id="sites-notice"·class="sites-notice"·role="status"·aria-live="assertive">·</div></div>(LF) </div>(LF) <div·id="sites-chrome-everything-scrollbar">(LF) <div·id="sites-chrome-everything">(LF) <div·id="sites-chrome-page-wrapper"·style="direction:·ltr">(LF) <div·id="sites-chrome-page-wrapper-inside">(LF) <div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-chrome-header-wrapper"·style="">(LF) <table·id="sites-chrome-header"·class="sites-layout-hbox"·cellspacing="0"·style="">(LF) <tr·class="sites-header-primary-row"·id="sites-chrome-userheader">(LF) <td·id="sites-header-title"·class=""><div·class="sites-header-cell-buffer-wrapper"><h2> <a·href="http://sites.google.com/site/medtechpedia/"·dir="ltr"·id="sites-chrome-userheader-title">MedTechPedia</a></h2></div></td><td·class="sites-layout-searchbox·"><div·class="sites-header-cell-buffer-wrapper"><form·id="sites-searchbox-form"·action="/system/app/pages/search"><input·type="hidden"·id="sites-searchbox-scope"·name="scope"·value="search-site"·/><input·type="text"·id="jot-ui-searchInput"·name="q"·size="20"·value=""·aria-label="Search·this·site"·autocomplete="off"·/><div·id="sites-searchbox-button-set"·class="goog-inline-block"><div·role="button"·id="sites-searchbox-search-button"·class="goog-inline-block·jfk-button·jfk-button-standard"·tabindex="0">Search·this·site</div></div></form></div></td>(LF) </tr>(LF) <tr·class="sites-header-secondary-row"·id="sites-chrome-horizontal-nav">(LF) <td·colspan="2"·id="sites-chrome-header-horizontal-nav-container">(LF) <div·class="sites-header-nav"><ul·class="sites-header-nav-container-tabs"><li·class="current"><a·class="sites-navigation-link·current"·href="/home">Home</a></li><li·class="unselected"><a·class="sites-navigation-link·unselected"·href="/introduction-to-medical-technology">Introduction·to·Medical·Technology</a></li></ul><div·style="clear:·both;"></div></div>(LF) </td>(LF) </tr>(LF) </table>·(LF) </div>·A Sites mapping won't always be present - but when it is, it's not difficult to solve - as long as you can access Google Apps aka "Control Panel".
Comments