You are viewing limited content. For full access, please sign in.

Question

Question

Quickfields Agent 10: Login information was not specified. Failed to initialize scanner

asked on November 3, 2017

Quickfields Agent 10: Login information was not specified.  Failed to initialize scanner

This error appears in my quickfields event viewer after changing one of my sessions to use SSL to connect.  When I changed it back the error went away.  We already use SSL in our environment (client, import agent, weblink) so I'm surprised it doesn't work here.

0 0

Answer

SELECTED ANSWER
replied on December 19, 2017 Show version history

My VAR and Laserfiche were eventually able to solve this.

SSL wasn't the problem.  Laserfiche Capture Engine was ignoring the connection information in the QFX file.  Instead it used a registry key HKEY_CURRENT_USER\Software\Laserfiche\Client8\Profile\IPDatabase\RepositoryName

That string was the fully qualified domain name of our Laserfiche server.  We connect to Laserfiche with a different DNS name, and our SSL certificate has that name.  After fixing the registry entry to that of the SSL Certificate quickfields runs in SSL mode just fine.

0 0

Replies

replied on November 3, 2017

Is your session logging in as a specified user or is it using Windows authentication. Keep in mind that Quick Fields Agent runs in the context of the service user, so if that user does not have the certificate used for SSL, you might see that error.

0 0
replied on November 3, 2017

The quickfields session connection uses a repository user.

The quickfields agent service runs as an active directory account.  Can you elaborate on what it means for the service user to 'have' the certificate?

0 0
replied on November 4, 2017

See the Client Requirements section in the help file. If the root certificate was only put in the current user's store and not in the local machine store, the service account might not have access to it, so it can't validate it for SSL connections. By default, the Windows Certificate Manager defaults to the current user's store.

0 0
replied on November 7, 2017

Thanks Miruna,

The certificate is installed in the local machine store.  I should add that Import Agent runs as the same service account and the connection profiles use SSL successfully.  It's very puzzling why one service will talk SSL and the other will not.

0 0
replied on January 29, 2020

I've got the same error after an upgrade from Quick Fields 9.1 to 10.3, but none of the sessions showing this error are using SSL to connect to the repository. 

 

The registry key has 'localhost' as the name, and replacing it with the FQDN did not help. In the connection information for the scan sources and classifications the laserfiche server is identified as 'localhost'

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.