I've seen this problem somewhat frequently. The solution is to do a DBCC CHECKALLOC

    ( 'database_name' ,  REPAIR_ALLOW_DATA_LOSS )    

--

Hilary Cotter

Looking for a SQL Server replication book?

http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS

http://www.indexserverfaq.com