Google is retiring the service.urchin.com server on 1 June, 2009. If your legacy Urchin 5.x installation references this server, you'll need to update the "__utm.js" that's being used on your web pages.
What to do:
Check to see if your Urchin Traffic Monitor (UTM) file is referencing this old service. If it is, you must make a change to the javascript or replace it if you wish to continue logging traffic both locally and to the Google Analytics system.
Option 1: Update Your Existing UTM
To see if your current "__utm.js" tracking code sends traffic to this server, check the following lines. The change, if necessary in your case, is simple:
The following lines should be modified.
change this:
var _ugifpath2="http://service.urchin.com/__utm.gif";
if (_udl.protocol=="https:") _ugifpath2="https://service.urchin.com/__utm.gif";
to this:
var _ugifpath2="http://www.google-analytics.com/__utm.gif";
if (_udl.protocol=="https:") _ugifpath2="https://ssl.google-analytics.com/__utm.gif";
With these modifications, utm.js calls ssl.google-analytics.com site instead of service.urchin.com in remote mode for both _userv=1 (remote logging only) and _userv=2 (remote and local logging).
Option 2: Replace Your Existing UTM
If you do not want to edit the __utm.js yourself, you can download a new one from http://www.google.com/urchin/hc/__utm.zip.
Background:
In 2004, when Urchin On Demand (UOD) was released, a feature was introduced which allowed administrators to log traffic to both the local Urchin server, and the hosted Urchin service. This hosted service (UOD) was the predecessor to Google Analytics. This was designed to permit a seamless transition to UOD while keeping a local copy of site traffic data. This method has since been superseded, but some old Urchin installations still reference this server.