You’re offline. This is a read only version of the page.
1,465
Client upgraded to GP 2016 R2 and the scan button within GP hangs up the user. She is using a
I saw there was an issue with the TWAIN/ISIS driver - and that was fixed in the latest hotfix - which should mean the version we are on is inclusive of this.
Is there something else we need to update to get this to work? Like update a driver or something?
Thanks
*This post is locked for comments
I have the same question (0)
Hello Deborah,
Looking at the January Hotfix blog and list of fixes, I don't see anything mentioning scanners or scan functionality
community.dynamics.com/.../microsoft-dynamics-gp-january-2018-hotfix-has-released
The last we've heard on it was it was targeted for the January hotfix but doesn't look like it made it.
The problem stems from using WIA scanner drivers which are overwritten by TWAIN or newer ones by Windows operating systems later than Vista. Also, modern scanners, that do OCR, will not use WIA drivers.
We've also seem more issues with Brother, Fujitsu, Kodak, Epson, and Canon scanners even though they are all WIA compliant, having the most success with HP scanners.
The plan is to re-design the GP code to use TWAIN drivers instead of WIA, which is more robust with modern day scanners.
So, there are changes coming, but we don't have a definite timeframe yet.
What we've seen some customers do, as a work-around, is scan to a common folder area, then attach from that folder, instead of right in the Dynamics GP application.
Thank you,
Share
Report
All responses (
Answers (
