Help: KILL doesn't kill

I'm trying to kill a process (BACKUP DATABASE). It goes into KILLED/ROLLBACK
state. Kill WITH STATUSONLY says it's 100% rolled back with 0 time left to
finish. But the task stays around, and keeps both S and X locks on the
database.
This is apparently a repeatable problem. Is this an SQL Server 2000 bug?
What can I do? The server is a live application, I don't want to have to
cycle the server.
Thanks.
I've heard of this happening and that it's an issue with SQL 2000 SP4,
related to a concurrency fix in Tempdb.
"Scott" wrote:

> I'm trying to kill a process (BACKUP DATABASE). It goes into KILLED/ROLLBACK
> state. Kill WITH STATUSONLY says it's 100% rolled back with 0 time left to
> finish. But the task stays around, and keeps both S and X locks on the
> database.
> This is apparently a repeatable problem. Is this an SQL Server 2000 bug?
> What can I do? The server is a live application, I don't want to have to
> cycle the server.
> Thanks.
>