May 2, 2014 at 9:14 am
Google is just not helping me. I've been trying to access the file table shares exposed on a server (I can select, delete, update, etc via SQL) via untransacted access with no luck (the share just sits there doing something when I try to access it, no error message of any kind).
So I thought I'd look to see if there were any open file handles via
SELECT * FROM sys.dm_filestream_non_transacted_handles;
I found there were 10 non transacted handles open, and they've been open for 3 days for automated processes and the files are about 1-2Kb in size.
so I tried to kill them via
exec sp_kill_filestream_non_transacted_handles
that's normally not something that takes very long (in fact when I cleared two for a different database it took just a second or two).
so leaving the stored proc running, I figured I'd connect and fire up Adam Mechanic's sp_whoisactive.
I see the processes to kill the open file handles, with a wait state of FFT_NSO_FILEOBJECT
Googling that brings back virtually no results, so any idea what this wait state is about?
May 5, 2014 at 12:42 pm
Mark,
I did some asking around and it looks like you should contact CSS to get an answer as they may need a mini-dump of the SQL Server process.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 11, 2015 at 1:29 pm
So it popped back up and in way larger force with SQL 2014... I've now opened a premier support ticket.
Whatever this problem is... it also prevents database Restores (backups seem to work).
Restores will get to 100% complete and just hang there. If I try to stop the restore query it will just cycle...
And I'll have a new Wait state FFT_NSO_DBLIST
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply