I had the same problem.

Apparently we're not alone:

forums.microsoft.com/.../ShowPost.aspx

Useful quotes from the site include:

"I'm gonna be fired!"

"The best part of your situation is that since you upgraded, you cannot
restore your stsadm backups over the config and admincontent databases.
They need to warn folks in the upgrade  KB paper about this! How great
it is that they tell you to backup your system when you have no ability
to recover from a fubar!"

"Later on I realized that the Config wizard should be run only after the
MOSS SP1 installation."

"Has everyone followed steps like *removing the orphaned objects from
database*, I missed this step  since I didnt understand this one.
Also, there is one step of checking and removing the previous upgrade
timr jobs from the jobs list.

See here,
technet2.microsoft.com/.../f484f5f2-35bb-4d70-bf
56-dd1c4c287c721033.mspx?mfr=true"

The technet link SORTA helped. Learned that I could change the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\12.0\WSS\SetupType to CLEAN_INSTALL and it at least pretended
to finish the upgrade.

Now I get the error:
The schema version (3.0.149.0) of the database [DB] on [DBHOST]\[SCHEMA]
is not consistent with the expected database schema version (3.1.3.0) on
[HOST]. Connections to this database from this server have been blocked
to avoid data loss. Upgrade the web front end or the content database
to ensure that these versions match.

I finally got mine back up. The log  shown by the wizard did not
help, but the update.log sure did. I have some junk site that was
throwing an error  in the update.log. I luckly could still get
Central Admin to work(but css was screwed up) and deleted that site.
Once I did that everything worked ok.

If you are running  MOSS, install the wss sp1  first on all boxes but
hit cancel before running wizard. The install MOSS sp1 on all boxes
but dont run wizard. Once code is updated on all boxes, then go back
to CA box and upgrade  it first. Once completed, do each box in the
farm.

Somewhere in the process I removed the only WFE from the farm.

I rolled my databases back to early Monday Morning, and right now I'm in
the process of trying to add the WFE back to the farm.

It'll be interesting because You can't just uninstall the SP1 binaries
from the WFE, so I wonder if the schema differences will cause me grief.


When this doesn't work  I'm going to create a new WFE in a Pre- Service
Pack 1 configuration.