Hi Layth,

Just in case anybody else has this problem.  Here is some more info on it.

The problem exists after the Windows SP4 install as it somehow corrupts the
database version in sysdatabases.
To fix this and determine if you have the same problem, execute the
following statement in master with Query Analyzer:

PROBLEM
==========
select * from sysdatabases

This should return something like (the value may differ):

Microsoft SQL-DMO (ODBC SQLState: 22003)
Error 220: Arithmetic overflow error for that data type smallint, value=32826.
Arithmetic overflow error for data type smallint, value=32826.
The statement has been terminated.

CAUSE
==========
An offline database had a version value of 32826 (or whatever you value is)
in the "version"
field, which is too large for a smallint datatype column in the
sysdatabases table.

RESOLUTION
============
It will fall over when it when it gets to the database with the incorrect
"version" and will NOT
show you the name of the database, so you will need to know the actual
name of the database.   Keep in mind you CAN see the list of databases in
QA, but NOT the
problem database, so it's NOT the next one in the list when you run
the select query.
Once you identify your culprit. Run the Alter
database statement to set the database back online:
"ALTER DATABASE databasename SET ONLINE".

That should fix it.

Cheers
Richard