Qlik Community

Ask a Question

New to Qlik Sense

If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.

Announcements
Become an analytics expert with Qlik's new 15 week course: Applied Data Analytics using Qlik Sense. READ MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
AnjaliRai
Contributor III
Contributor III

Engine Service on Qlik Proxy node

Hi All,

Need a help. Engine service should run on Proxy Node at Qlik Sense Server?

We believe it should not , but every time we restart Proxy node, the engine service stops and when restarted it throws an error:

Error: 1067, Service cannot run over server, it fails.

But, when under nodes, if we activate engine and then again restart the service over server, it starts runningwithout throwing an error.

As of now, we are using Sept 2020 Sense version.

Just wandering about the issue. Kindly suggest!

AnjaliRai_0-1602486134856.png

 

--Anjali Rai

Anjali Rai
Labels (1)
1 Solution

Accepted Solutions
AnjaliRai
Contributor III
Contributor III
Author

Hi @ArnadoSandoval ,

Back with an update. Had a discussion with Qlik on the issue  I reported to get better understanding.

As per Qlik, we can go ahead and disable the Qlik Engine Service over Proxy node if that is creating an issue and not starting up on it's own.

If the service is disabled in the QMC, the Central Node Repository Service understands this service is not needed and will not be contacted. Otherwise we would see other issues in the QMC like the node still showing 5 of 5 services running when Engine or another service is disabled. That is not the case here.

There is no requirement for all services to run on a Rim node, if not all services are selected in QMC. Furthermore, in previous versions you would choose the type of Rim that you wish to install and some of the services would be left out and never installed to begin with. This installer model has changed, yet the requirement for services to run remains the same: only if enabled in the QMC, this governs all Central Node communication patters with the Rim nodes.

Nevertheless, since this change was not known nor documented in the Release Notes, Support Team has raised the issue with R&D under ID QB-2562 and they will get back to us once they have some feedback on this report.

But in the meantime, rest assured there is no impact to environment if this service is not running.

--Anjali

Anjali Rai

View solution in original post

17 Replies
mikelutomski
Creator
Creator

Hi Anjali.

We are experiencing this same issue.

We upgraded from April-2020 SR3 to Sept-2020 SR2 tonight, and this immediately started happening.

My initial thought is that this is NOT required to run unless otherwise specified in the QMC that the Proxy should act as an Engine, however it makes me a little uneasy as this service has always ran in the past.

Were you able to find a solution?

-Mike

Chanty4u
Champion III
Champion III

Hi ,

this usally happens.  but there is a workaround  provided on below link . it might help

https://support.qlik.com/articles/000041755

 

ArnadoSandoval
Specialist II
Specialist II

Hi @AnjaliRai 

I did some research, these are my findings:

Engine service should run on Proxy Node at Qlik Sense Server?

Actually, based on Qlik's Qlik Sense Enterprise on Windows: multi-node deployment you can do it, scroll down the linked document, a couple of diagrams include the Proxy and Engine Services in the same node.

Error: 1067, Service cannot run over server, it fails.

According to Microsoft, the error 1067 appears due to viruses or file system corruptions, take a look at the following articles: (VIPRE) Error 1067: 'Process unexpectedly Terminated' when starting VIPRE service ; (IBM) "Error 1067: The Process terminated unexpectedly." when starting Application Server Service ; the first article points to file system corruption, the second a sort of time-out connecting to a database; I suggest you to review the Server's Event Viewer for more details about the error happening at your site, it will help us to understand the details.

Other articles in the Qlik Community:

One or more Qlik Sense services did not start after installation this article include some check-points!

Qlik Sense Proxy Service service won't start Old topic, the solution given was to increase the time-out windows assigned to start a service from 30 seconds to 2 minutes. If you review the Events log the messages could lead you into this solution.

QlikSense proxy service not starting Another old article, the solution given there was by changing the time-out!

My suggestions:

The error you reported does not relate to the time-out error previously reported, I suggest checking the Events Logs for more details.

Review the QlikSense ports assigned on the server hosting the proxy; this article may help: Ports 

Make sure the server hosting the Proxy Service also start the Repository Service

01-Repository-Node-01.png

Hope this helps,

Arnaldo Sandoval
A journey of a thousand miles begins with a single step.
AnjaliRai
Contributor III
Contributor III
Author

Hi @mikelutomski ,

Even when we were running on April 2020, we never faced this issue and we upgraded to Sept 2020 last week then the problem has started to occur.

To start the service, as a workaround, I enable the engine under proxy node and then start the service over server. Once service is running fine, I disable the engine under proxy again.

I will let you know if anything I found as a solution. Thanks for sharing !

--Anjali Rai

Anjali Rai
AnjaliRai
Contributor III
Contributor III
Author

Hi @ArnadoSandoval ,

Thanks much for your detailed analysis and suggestions as always. 🙂

All looks good from port and Platform perspective, did a quick check. Also, we have not done any recent changes on Platform except Upgrade to Sept 2020.

To start the service, as a workaround, I enable the engine under proxy node and then start the service over server. Once service is running fine, I disable the engine under proxy again ( not sure if we keep it enable, will there be any issues ?)
Also, I remember it never happened with any release 
earlier though, but happening now every time server reboot is happening.

As per my understanding, Engine should not run over Proxy node, but since this issue never happened earlier, a bit stuck at this point.

Also, as per the article  did a quick check on the setting we have currently-

--https://support.qlik.com/articles/000041755?_ga=2.219398681.1487762103.1602485286-1149973368.1591644...

AnjaliRai_0-1602595791700.png

Should we change it and see how this works? Pleas suggest!

-Anjali 

 

Anjali Rai
AnjaliRai
Contributor III
Contributor III
Author

Hi @Chanty4u ,

 

Thanks for sharing the article. I did checked the current setting over our Proxy server and found as below-

AnjaliRai_0-1602597046843.png

Just wanted to check if you had faced the same issue in Sept 2020 Qlik Release and this setting change has fixed the issue?
I cannot test this over any test server and need to directly implement it in production, if this is the fix. Before doing that, wanna make sure no adverse impact of it.

Please share!

--Anjali

Anjali Rai
Chanty4u
Champion III
Champion III

Hi,

i  have not faced this issue.    Michael_Tarallo 

 

AnjaliRai
Contributor III
Contributor III
Author

Thanks @Chanty4u , yes we went through Sept 2020 Release fix thoroughly along with Qlik Support team before the upgrade, but no topic related to services came up/addressed in any of our meetings.

Yes I will wait for expert suggestions and let's see if we can fix the issue.

--Anjali 

Anjali Rai
Chanty4u
Champion III
Champion III

Did you log any ticket with qlik support team?

if not please raise the ticket along with your issue statement.