Home › Forums › TWAIN Classic › TWAIN data source error.
- This topic has 5 replies, 4 voices, and was last updated 9 years, 1 month ago by JTinAZ.
- AuthorPosts
When running my application on some Windows systems, I am seeing an unusual error.
“The device could not be locked. Check that another application isn’t using the device. (-4630)”
I’m not sure what is putting up this dialog box but I am assuming twain_32.dll. It only happens on some systems and can’t be easily reproduced. It does appear that the close data source request hangs for a few seconds when it normally returns rather quickly. The close data source returns success but any attempt at opening the data source after that results in the above error. Only rebooting the machine will fix the problem, restarting the application has no effect.
[attachment=0:t5m6fdkq]lock.JPG[/attachment:t5m6fdkq]
Please reference this site: http://www.scan2soft.com/10
The error code -4630 is PIX_ERR_LOCKFAILED “The device could not be locked. Check that another application isn’t using the device.” This is defined in the pixerr.h include file, and is an error code for an ISIS driver, suggesting that the TWAIN driver you’re using is built on top of an ISIS driver.
The dialog box is being raised by the ISIS driver, or some software layer provided by EMC or the scanner vendor. It is not coming from the TWAIN Data Source Manager. You’ll have to contact either EMC or the scanner vendor to get help for this problem.
Was this issue resolved? If so, how?
Thanks!
@orbian wrote:
When running my application on some Windows systems, I am seeing an unusual error.
“The device could not be locked. Check that another application isn’t using the device. (-4630)”
I’m not sure what is putting up this dialog box but I am assuming twain_32.dll. It only happens on some systems and can’t be easily reproduced. It does appear that the close data source request hangs for a few seconds when it normally returns rather quickly. The close data source returns success but any attempt at opening the data source after that results in the above error. Only rebooting the machine will fix the problem, restarting the application has no effect.
[attachment=0:3pxw9saq]lock.JPG[/attachment:3pxw9saq]
Hello again! I am having the same problem. Were you able to resolve this issue? If so, can you share how?
I appreciate it!
Hi,
I have the same problem… did you solve it?
Thanks in advance.
Unfortunately, not. Still hoping for a reply. 🙂
- AuthorPosts