Exception from HRESULT: 0x80210015 !

Sep 3, 2011 at 5:40 AM


Any solution to prevent this "Exception from HRESULT: 0x80210015"?



Dec 8, 2011 at 2:20 PM

Hey hishamix, 

Most probably this means the device is unplugged, make sure the scanner is plugged (the code does not check for a missing scanner)

Could you try playing around with the DPI. Try setting it to 150 or 300 or more. (Some scanners seem to have issues with different DPI's)

Could you please add  the stack trace here if it continues?

Jan 28, 2012 at 8:47 AM

Same problem here, Windows 7 64bit with ScanSnap S1500. DPI doesn't change anything for me, but here's the error stack:


See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************

System.Runtime.InteropServices.COMException (0x80210015): Exception from HRESULT: 0x80210015   at WIA.CommonDialogClass.ShowSelectDevice(WiaDeviceType DeviceType, Boolean AlwaysSelectDevice, Boolean CancelError)   at ADFScanner.ADFScan.Scan(ScanColor clr, Int32 dpi)   at ADFScanner.ADFScan.BeginScan(ScanColor color, Int32 dotsperinch)   at ADFScannerTest.Form1.button2_Click(Object sender, EventArgs e)   at System.Windows.Forms.Control.OnClick(EventArgs e)   at System.Windows.Forms.Button.OnClick(EventArgs e)   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)   at System.Windows.Forms.Control.WndProc(Message& m)   at System.Windows.Forms.ButtonBase.WndProc(Message& m)   at System.Windows.Forms.Button.WndProc(Message& m)   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib    Assembly Version:    Win32 Version: 2.0.50727.4963 (win7RTMGDR.050727-4900)    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------ADFScannerTest    Assembly Version:    Win32 Version:    CodeBase: file:///C:/Users/Remo%20Laubacher/Desktop/New%20folder/ADFScannerTest.exe----------------------------------------System.Windows.Forms    Assembly Version:    Win32 Version: 2.0.50727.4961 (win7RTMGDR.050727-4900)    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/    Assembly Version:    Win32 Version: 2.0.50727.4962 (win7RTMGDR.050727-4900)    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/    Assembly Version:    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/    Assembly Version:    Win32 Version:    CodeBase: file:///C:/Users/Remo%20Laubacher/Desktop/New%20folder/ADFScanner.DLL----------------------------------------Interop.WIA    Assembly Version:    Win32 Version:    CodeBase: file:///C:/Users/Remo%20Laubacher/Desktop/New%20folder/Interop.WIA.DLL----------------------------------------
************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.
For example:
<configuration>    <system.windows.forms jitDebugging="true" /></configuration>
When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.

Jan 28, 2012 at 8:56 AM

It seems like a common problem and probably means that the attached device doesn't work with. A bit surprising to me as I have a webcam as well, which works with anything so far, and does not even shut down when my face is in the picture.



Jan 28, 2012 at 8:56 AM
Edited Jan 28, 2012 at 8:58 AM

You are absolutely sure the scanner is on right?

Did you try settings the DPI really high and then decreasing in steps of 250 or something?

I'm looking into this..


Didn't see your first post. Yea, from what I remember when I used this lib in production was. If the scanner wasn't connected it would throw up this HRESULT.

Jan 28, 2012 at 8:59 AM

Yes, I just scanned with the application from the vendor a second before I used your application. However, I can confirm that this isn't a problem in your code but rather because my lovely scanner doesn't work with WIA. I found a (German) site which confirms this http://www.officemanager.de/scansnap/faq.html

It might be nice to handle such errors and show the users a message box telling him that no attached device supports WIA but at the end there's probably nothing you can do about this problem!

Jan 28, 2012 at 9:04 AM
Edited Jan 28, 2012 at 9:04 AM

Yea I'll try and update the test code and put this up as a known issue.

Thanks for taking the time to look into this and posting it here :)