SQLSrvE2E Work Item Rss Feed

Commented Issue: Error: Invalid handle.\r\nParameter name: handle [8622]

rfyffe — Tue, 03 Apr 2012 09:30:35 GMT

Error Message is : "Invalid handle.\r\nParameter name: handle" on line :

The code instruction generating the error is : FileStream destBlob = new FileStream(handle, FileAccess.Write);

Stack Trace is :

A first chance exception of type 'System.ArgumentException' occurred in mscorlib.dll
System.Transactions Critical: 0 : <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Critical"><TraceIdentifier>http://msdn.microsoft.com/TraceCodes/System/ActivityTracing/2004/07/Reliability/Exception/Unhandled</TraceIdentifier><Description>Unhandled exception</Description><AppDomain>FileStreamLoader.vshost.exe</AppDomain><Exception><ExceptionType>System.ArgumentException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>Invalid handle.
Parameter name: handle</Message><StackTrace> at System.IO.FileStream..ctor(SafeFileHandle handle, FileAccess access, Int32 bufferSize, Boolean isAsync)
at System.IO.FileStream..ctor(SafeFileHandle handle, FileAccess access)
at FilestreamLoader.Program.Main() in C:\demos\Katmai\SQLSrvE2E_SQL2K8_Samples_v1.1\SQLSrvE2E_SQL2K8_Samples_v1.1\FILESTREAM-WPF-HTTP Sample\CS\FilestreamWpfHttp\FilestreamLoader\main.cs:line 106
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()</StackTrace><ExceptionString>System.ArgumentException: Invalid handle.
Parameter name: handle
at System.IO.FileStream..ctor(SafeFileHandle handle, FileAccess access, Int32 bufferSize, Boolean isAsync)
at System.IO.FileStream..ctor(SafeFileHandle handle, FileAccess access)
at FilestreamLoader.Program.Main() in C:\demos\Katmai\SQLSrvE2E_SQL2K8_Samples_v1.1\SQLSrvE2E_SQL2K8_Samples_v1.1\FILESTREAM-WPF-HTTP Sample\CS\FilestreamWpfHttp\FilestreamLoader\main.cs:line 106
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()</ExceptionString></Exception></TraceRecord>

Connection to the database are ok, I have traced with SQL Profiler :

exec sp_executesql N'INSERT [dbo].[media]([mediaId], [fileName], [contentType]) VALUES( @mediaId, @fileName, @contentType);',N'@mediaId uniqueidentifier,@fileName nvarchar(256),@contentType nvarchar(256)',@mediaId='1AB1E4B3-1F87-48DF-B3FA-88582E3D29D4',@fileName=N'RogAndZachOnFilestream.wmv',@contentType=N'video/x-ms-wmv'

exec sp_executesql N'SELECT [file].PathName(), GET_FILESTREAM_TRANSACTION_CONTEXT() FROM [dbo].[media] WHERE [mediaId] = @mediaId;',N'@mediaId uniqueidentifier',@mediaId='1AB1E4B3-1F87-48DF-B3FA-88582E3D29D4'
Comments: ** Comment from web user: rfyffe **

I too am having this problem. The only diffence is that i'm already using windows authentication to connect to my DB. I'm using Visual Studio 2005 and MSSQL 2008.
This is and example of my connection string
<add key="ServerConnStr" value="Data Source=SYSLT1990;Initial Catalog=TEST_DB;Integrated Security=SSPI"/>

Please tell me wat to do here i'm deperate. Thanks

COMMENTED ISSUE: File size limitations

ZachSkylesOwens — Thu, 24 Jan 2008 23:46:40 GMT

Kudos on the samples for FileStream in Katmai!

Our organization will be serving up video files from 1.6 to 3 GBs in size. I'm currently running the source code in a virtual machine session (VMWare Fusion 1.0, Win Server 2008, Katmai). Everything works great, until I try to upload a 1.6GB file, and I run into the ever popular "OutOfMemoryException".

My question: Am I stupid for trying to run this in a virtual machine with only 2GB of mem, or is there something inherent in the system that is going to limit us from uploading files of this size to SQL Server?

Thanks!
Comments: ** Comment from web user: ZachSkylesOwens **

Have you made any progress on this dizzyguy? Have you identified where the bottle neck is? You mentioned the input-file tag… The code in the sample doesn’t actually provide an interface for uploading video via a web page.

Are you experiencing the file size issue when trying to serve up the video? It reads and writes the file in 512K chunks which shouldn’t cause an issue.

I’m interested to hear your conclusion.

COMMENTED ISSUE: File size limitations

dizzyguy — Fri, 18 Jan 2008 17:39:23 GMT

And yeah, definitely interested in learning more about your custom IIS 7 module...

COMMENTED ISSUE: File size limitations

dizzyguy — Fri, 18 Jan 2008 14:21:11 GMT

Yep, that's right, within an ASPX page. And it appears that ASPNET doesn't play well with large files. My next attempt is going to be to build a WCF service (binary over TCP). This is all pretty new to me, so this may be yet another wasted effort, but I'll be happy to keep you all informed if you like.

COMMENTED ISSUE: File size limitations

ZachSkylesOwens — Fri, 18 Jan 2008 02:09:39 GMT

Sorry that it took me a couple days to see this… I tried this with videos that were a few hundred MB without any problem. I’m not sure what limitation you might be running into with the GB size.

We have a sample that uses a Custom IIS 7 Module written in C++ which has great performance for serving these up. We were able to tap into some lower level system resources. We are working on solidifying that code and will publish it in the next few weeks.

Just to clarify… Are you having this issue when serving the file with the ASPX service?

COMMENTED ISSUE: File size limitations

dizzyguy — Wed, 16 Jan 2008 21:01:33 GMT

Sorry for all of the comments, but can you tell me if you think that a WCF service set up to receive streamed data (e.g. transferMode.Streamed) might solve the OOM Exception? My thought is that Silverlight+WCF/Streaming might be an answer for getting > 1GB files into a FILESTREAM on SQL 2008? This is probably a question for the WCF team, because as I understand it, the problem with ASPNET is that the data is saved in memory - instead of being written to the hard drive - which is the reason we get OOM exceptions. But does streaming break the data up enough to solve any memory issues? All rhetorical questions on my part, but if someone out there can help me put this all into perspective, I'd really appreciate it!

COMMENTED ISSUE: File size limitations

dizzyguy — Wed, 16 Jan 2008 02:40:43 GMT

After further reading, I learned that this is an ASPNET worker process "problem". I will need to either buy a component or figure out another way to get users from disparate networks to upload 2GB+ files to our servers.

COMMENTED ISSUE: File size limitations

dizzyguy — Tue, 15 Jan 2008 22:28:23 GMT

One more thing worth noting...I moved the code to a server with plenty of resources, but it still failed to load the larger files. Makes me think this is something related to the INPUT tag and how IIS is processing this????

COMMENTED ISSUE: File size limitations

dizzyguy — Tue, 15 Jan 2008 22:26:39 GMT

I've done everything that was laid out in the demo, except with one not-so-minor change evidently. I'm trying to use the <input type='file'> tag to load the file into SQL. It works with 50MB files, but I get a 404 error when trying to work with files in the GB+ range.

In this case, the INPUT is an ASPNET FileUpload component, and I'm loading the FileStream from the FileUpload's InputStream like so:

// Open up a new stream to write the file to the blob.
destFile = new FileStream(handle, FileAccess.Write);

// Open up a new stream to read the source media file.
// --- Not using sourceFile: FileStream sourceFile = new
// FileStream(String.Concat(filePath, fileName), FileMode.Open, FileAccess.Read);
// Use the FileUpload.PostedFile.InputStream
byte[] buffer = new byte[FileUpload1.PostedFile.InputStream.Length];
int bytesRead;
while ((bytesRead = FileUpload1.PostedFile.InputStream.Read(buffer, 0, buffer.Length)) > 0)
{
destFile.Write(buffer, 0, bytesRead);
}
destFile.Close();
// sourceFile.Close();

Maybe using the INPUT-FILE tag isn't the right option? But we do need to enable offices from around the organization to upload the data in a standard manner -- and the INPUT-FILE tag was our first choice.

Any thoughts on that?

COMMENTED ISSUE: File size limitations

ReedMe — Tue, 15 Jan 2008 18:05:10 GMT

Other than the obvious limitations of the virtual environment that you're in, dizzyguy, there should be no reason that you'd be limited. How exactly are you trying to load the filestream? With SNAC?

CREATED ISSUE: File size limitations

dizzyguy — Mon, 14 Jan 2008 18:02:16 GMT

COMMENTED ISSUE: Error: Invalid handle.\r\nParameter name: handle

rdoherty — Thu, 22 Nov 2007 04:32:05 GMT

I reproduced this and forwarded to FILESTREAM team for investigation. Great catch!

COMMENTED ISSUE: Error: Invalid handle.\r\nParameter name: handle

ZachSkylesOwens — Wed, 21 Nov 2007 21:34:51 GMT

This issue was found by a developer in France.

After going back and forth a few times we discovered that the problem was he was using SQL Server authentication mode and using "sa". We developed these samples using Windows Authentication. Once he updated his configuration the sample ran without an issue.

We will investigate what changes need to be made for SQL Server authentication mode to work properly before closing this Issue.

CREATED ISSUE: Error: Invalid handle.\r\nParameter name: handle

ZachSkylesOwens — Wed, 21 Nov 2007 20:17:19 GMT

CLOSED ISSUE: Test

ZachSkylesOwens — Fri, 09 Nov 2007 16:10:21 GMT

This is a test Issue
Comments: This was just a test.

CREATED ISSUE: Test

ZachSkylesOwens — Wed, 07 Nov 2007 23:58:57 GMT

This is a test Issue