I've seen that once before, when I was playing with corruption. Happened when there was an active transaction when the DB went suspect. Not sure why.
As far as I know, there's no way around it. Emergency mode repair is the absolute, final last resort. If it fails, there's no alternative, nothing else that can be done.
I hope you have a backup. If not and the DB is still readable, export the data, script the objects and recreate the DB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability