Question

Could not connect to the Quick Fields Server. [QF10000]

Quick Fields

Updated January 11, 2023

asked on February 17, 2017

We recently updated to Quick Fields 10 several weeks ago. I noticed that we are not able to publish sessions or get into the Quick Fields Administration Console. We are receiving an error that states "Could not connect to the Quick Fields Server. [QF1000]". We have both ports 8092 & 8093 open. I am not sure where the problem lies and could use some help.

Thank You,

Zach Merrill

0 0

Answer

SELECTED ANSWER

replied on August 29, 2017

Hi all,

I found how to resolve mine.

As a reminder, my error is the same than Zach but for an internal network.

In my case, the Laserfiche Quick Fields Server' service didn't start and I can't start it.

1. Stop "Laserfiche Quick Fields Agent".

2. Start "Laserfiche Quick Fields Server".

3. Start "Laserfiche Quick Fields Agent".

4. Reload your Web Page.

@Raymond, can Laserfiche change the title?

This is not

"Could not connect to the Quick Fields Server. [QF10000]"

but

"Could not connect to the Quick Fields Server. [QF1000]"

Thank you in advance.

Regards

3 0

Replies

replied on February 17, 2017 • Show version history

How did you check that both ports are open?
Can you test both ports using telnet from both directions?
https://kb.acronis.com/content/7503
Run the telnet test for both ports to and from both machines. If it fails in either direction, then your port(s) are not open.

0 0

View 5 previous replies

replied on February 21, 2017

Raymond,

I am not able to telnet from our Laserfiche Quick Fields server to our Laserfiche server over ports 8092 and 8093. However, I am able to telnet from our Laserfiche Server to our Quick Fields Server over these ports. It appears the ports are only open 1 way. Do we need to switch this around on our firewall? Or do the ports need to be open both ways?

Thank You,

Zach Merrill

0 0

replied on February 22, 2017

You should open it both ways.

0 0

replied on August 24, 2017

Hi all!

Raymond, if my Laserfiche Quick Fields Server and my Laserfiche Server are on the same machine and use the port 8093, is it possible to have the same error than Zach if the port 8093 is closed?

0 0

replied on August 28, 2017

Yes it is possible. 8093 is the port used by the QF server.

0 0

SELECTED ANSWER

replied on August 29, 2017

Hi all,

I found how to resolve mine.

As a reminder, my error is the same than Zach but for an internal network.

In my case, the Laserfiche Quick Fields Server' service didn't start and I can't start it.

1. Stop "Laserfiche Quick Fields Agent".

2. Start "Laserfiche Quick Fields Server".

3. Start "Laserfiche Quick Fields Agent".

4. Reload your Web Page.

@Raymond, can Laserfiche change the title?

This is not

"Could not connect to the Quick Fields Server. [QF10000]"

but

"Could not connect to the Quick Fields Server. [QF1000]"

Thank you in advance.

Regards

3 0

replied on August 30, 2017

Thank you @████████for the detailed steps on how to resolve this issue. I followed those steps exactly and now I can load the server page and publish sessions again. That was a much easier fix than what I thought it would be!

0 0

replied on August 30, 2017

@Zach Merrill, I'm glad to help you.

However, if you server restart, you should do it 1 more time. In my mind, this is a bug and Laserfiche should fix it.

I'm not sure.

0 0

replied on June 10, 2021

Thanks Olivier for the great advice, this worked for me.

0 0

replied on March 1, 2018

Hi,

I tried to follow steps defined by Oliver:

1. Stop "Laserfiche Quick Fields Agent".

2. Start "Laserfiche Quick Fields Server".

3. Start "Laserfiche Quick Fields Agent".

4. Reload your Web Page.

But I am still getting <Could not connect to the Quick Fields Server. [QF1000]>

Pls. help me.

Also, I cant connect to LF Quick Fields Scanning

qf-scanning-account-error.jpg (98.86 KB)

| Download

0 0

replied on March 1, 2018

Hi Mahwish,

I was the same error and my first solution didn't work.

QF Scanning was browsing to a QF Server that was running on another machine and couldnt changed it unless we stop the QF Server on the other machine.

This is another solution.

First, under QF Server Configuration Utility, change your port to another one (example 8095)

Then, on Database, create a new database.

Restart your service

Launch QF Scanning first

Ensure under account it is set (with the new port) and pass the test. Apply

Then launch QF Admin and that should connect.

0 0

replied on March 1, 2018

Hi Olivier,

Thanks for your help but the steps described by youi didnt resolve the issue so I deleted the QFS folder from ProgramData and then re-installed QFS manually.

The QF scanning is error free but when I try to publish a session i get this error:

5.jpg (205.99 KB)

| Download

0 0

replied on January 11, 2023

I know this is an old post, but I found my own solution to this issue that I wanted to share in case anyone else comes across this. In Event Viewer > Windows Logs > Application, I could see that there were many errors with Event ID 400 with a source of Quick Fields Server. In these events, I could see two key details:

Message : Access to the path 'C:\ProgramData\Laserfiche\Quick Fields\Licenses\QFS\activation.xml' is denied.
WindowsIdentity : NT AUTHORITY\NETWORK SERVICE

I then changed the permissions on C:\ProgramData\Laserfiche\ to allow full control from the NETWORK SERVICE account, restarted the Laserfiche Quick Fields Agent service, and restarted the IIS application pool. After doing this, I had no further issues.

0 0

You are not allowed to follow up in this post.

Question

Question

Could not connect to the Quick Fields Server. [QF10000]

Answer

Replies

Sign in to reply to this post.