I use this code in a command line application, saves a lot of time from not logging into a site, finding the list or library, opening settings, opening versioning properties, and then enabling.

public static void EnableVersioning(string URL, string ListName)

{

PDLists.Lists EnableVersions = new PDLists.Lists();

EnableVersions.Credentials = CredentialCache.DefaultCredentials;

EnableVersions.Url = URL + “lists.asmx”;

XmlNode _response = null;

XmlNode ndList = EnableVersions.GetList(ListName);

XmlNode ndVersion = ndList.Attributes["Version"];

XmlDocument xmlDoc = new System.Xml.XmlDocument();

XmlNode ndProperties = xmlDoc.CreateNode(XmlNodeType.Element, “List”, “”);

XmlAttribute ndVersionAttrib = (XmlAttribute)xmlDoc.CreateNode(XmlNodeType.Attribute, “EnableVersioning”, “”);

ndVersionAttrib.Value = “TRUE”;

ndProperties.Attributes.Append(ndVersionAttrib);

XmlDocument doc = new System.Xml.XmlDocument();

XmlElement batchElement = doc.CreateElement(“Batch”);

XmlNode newItemhome = EnableVersions.GetListCollection();

try

{

_response = EnableVersions.UpdateList(ndList.Attributes["ID"].Value, ndProperties, null, null, null, ndVersion.Value);

}

catch (Exception ex)

{

Console.WriteLine(ex.Message + “\n ” + ex.StackTrace);

}

Console.WriteLine(“[versioning enabled]“);

}

stsadm -o sync -listolddatabases 0

You can then use this information to query SQL and see which databases are having issues.  OR, you can use this VBS script to get the information:
Set Args = WScript.Arguments
Connstr = "Driver={SQL Server};Server=SQL2005;Database=Config_DB"
Set Connect = CreateObject("ADODB.Connection")
Connect.Open Connstr
strInput = Args.Item(0)
Set DB = Connect.Execute("SELECT Id, ClassId, Name, Status, Version, Properties FROM Objects WHERE (Id = '" & strInput & "')")
Do Until DB.Eof
WScript.Echo Db("Id")
WScript.Echo Db("ClassId")
WScript.Echo Db("Name")
WScript.Echo Db("Status")
WScript.Echo Db("Version")
'WScript.Echo Db("Properties")
DB.MoveNext
Loop


stsadm -o sync -deleteolddatabases 0

stsadm -o preparetomove -contentdb -contentdb : -site
stsadm -o deletecontentdb -url -databaseserver -databasename
To reattach:
stsadm -o addcontentdb -url -databasename -databaseserver

I hope that saves someone else some time.

I fixed the problem by assigning an indexer to the SSP. Not exactly sure how it happened that the indexer was never assigned, but here are the steps:

1. Open Central Administration
2. Go to the Application tab
3. Select “Create or Manage this farm’s shared services”
4. Use drop-down list for the SSP, select Edit Properties
5. Assign an indexer server

1. Download Adobe PDF IFilter 6.0 from Adobe. 
2. Stop the IIS Admin service: Start -> Run -> services.msc -> IIS Admin Service -> Stop
3. Run the Adobe PDF IFilter 6.0 Setup program to install the filter on the server.
4. Copy the ICPDF.GIF file to “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images”
5. Edit the file C:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\Template\Xml\DOCICON.XML
   1. Add an entry for the .pdf extension.
      <Mapping Key=”pdf” Value=”icpdf.gif”/>
6. Perform an iisreset or recycle the SharePoint Application Pools
7. Add the .pdf file type to the index list:
   1. Go to Central Administration, then to the Shared Services Administration Web of the current SSP, go to Search Settings and next to File Type
   2. Add a new file type pdf
8. Perform a Full Update on the Search content indexes

Note: The ICPDF.GIF file is included in the file.