ScanConnect Crash

replied on May 4, 2017

Does the scanner work using testappn.exe in "C:\Windows\PIXTRAN" ? If the scanner works with testappn, it should work with Scanconnect. Try clearing out the user attributes in the admin console along with the registry "HKEY_CURRENT_USER\SOFTWARE\Laserfiche\Client8" after getting it configured with testappn.

1 0

View 3 previous replies

replied on June 7, 2017

I have a user with the same issue. The testappn file did not work for us. Typically when clients have an issue loading the driver directory, the testappn file works perfectly. For whatever reason - not this time...

As far as the registry key you mention to delete from the registry - delete the whole Client8 node? Or delete the key inside that Client8 node?

Regards,

Jon

0 0

replied on June 7, 2017

If testappn doesn't work, there's a problem with the driver. Deleting the attributes from the registry won't make a difference. Try downloading the latest scanner driver from the manufacturer's website.

1 0

replied on June 8, 2017

Hi Miruna,

Yes, we have tried downloading the latest and greatest from the Canon website. This client has a Canon DR9080c. When I uninstalled the old scanner driver, we had issues getting the most recent scanner driver installed. After 4 attempts, we finally got it installed. The unusual thing about the install of the driver is when looking in the programs and features, there is no information displayed about the driver (date, manufacturer, version, etc.), just the name of the driver is displayed....

0 0

replied on June 8, 2017

Those properties of the installer are optional and should not affect the actual functionality.

1 0

replied on June 28, 2018

Solution (at least in our case)

Had the same issue. Basically there are a few files in LF Client and/or ScanConnect that don't automatically update with later iterations of LF Client. This results in a failure to find the files it's programmed to find, and the above-mentioned crash. Rather than spending hours combing through and find each file that needs to be updated, we followed these simple steps.

1) Uninstalled LF Client

2) Uninstalled ScanConnect

3) Uninstalled the Canon Driver (worked for both the DR M140 and the DR 6010c stations)

4) Made sure that in Services>Windows Image Acquisition (WIA), that this service is both Stopped, and Disabled. It will take the scanner driver and will NOT let go, so you have to shut this off.

5) Re-install all of the above programs in the same order (LF Client, ScanConnect, and the Driver).

Tested it out, and everything worked again. Also check to make sure that your C:\Windows\PixTran folder has been given appropriate rights for the domain users on that machine, or else it will not be able to access those files when using ScanConnect. You can use PixTran's "Testappn" program to configure the scanner if you're having trouble with it in LF Scanning.

Hope that helps somebody out there. Good luck!

3 0

replied on April 23, 2019

I just wanted to add our findings to this post as well. The above steps did not work for us when using Quick Fields and we were not able to use testappn.exe either. What we did was:

1. Uninstalled ScanConnect

2. Deleted the contents of C:\Windows\PixTran (not the folder, just the contents)

3. Rebooted the machine

4. Reinstalled ScanConnect

We thought we would have to reinstall the scanner drivers on top of that since Support said deleting the contents of the PixTran folder would essentially remove the driver but it did not require us to reinstall them.

We did have the WIA service stopped as well since it was in the above steps but not sure if that was needed in our case. Hope this helps anyone else!

0 0

Question

Question

Replies

Sign in to reply to this post.