spid stuck in ROLLBACK

I killed a spid earlier - it's command is currently KILLED/ROLLBACK and has been for a very long time.  (couple hours, plus)
the cputime and disk i/o are very minimal and haven't changed at all, subsequent attempts to kill the spid return this:

spid 1: transaction rollback in progress.  Estimated rollback completion: 100%.  Estimated time remaining: 0 seconds.

but, status is RUNNABLE
and certain retrievals are actually blocked by this spid
very important, please advise as soon as possible
LVL 18
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Only way I have been able to clear this is to stop and start SQL Server. :(

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dbaSQLAuthor Commented:
so you've seen this before then?  do you know what causes it?  a restart isn't feasible right now at all.
I've had two cases when it happened.

1.) A stored procedure was stuck in an infinite loop.  Killing the spid stopped the infinite loop but the process stayed around until I did a stop\start.

2.)  I was copying DTS packages from one msdb database to another msdb database on another server.  The copy was being done via a trigger that had a misspelling in the table name.  The trigger would not end and both msdb databases were hung until I stopped/started SQL Server.

These were both stupid mistakes I made while trying to do something "quick". :(   Fortunately the number of users at the site was small so no real problem with the stop/start.
I have also seen this with xp_ procedures (xp_cmdshell, etc). These are external stored procedures that run in the SQL Server address space, but SQL Server does not have any knowledge or control of them.

DonKronos is right - you will have to stop/start the service to clear this spid out.
dbaSQLAuthor Commented:
well, unfortunately i can't do that right now.  but thank you both for your advice
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.