Skip to main content
Announcements
Introducing a new Enhanced File Management feature in Qlik Cloud! GET THE DETAILS!
cancel
Showing results for 
Search instead for 
Did you mean: 
ag072023
Contributor II
Contributor II

QEPM service is failing on one node after upgrading to 2023.05

Qlik EPM service is stopped running after upgrading to 2023.05 version. it runs fine on node 01 but keep failing when running on node 02 . (cluster server)

 

 

 

Application: aemctl.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Attunity.Infrastructure.HostManager.HostManager.OnServiceStop()
at System.ServiceProcess.ServiceBase.DeferredStop()
at Attunity.Infrastructure.ServiceManager.ServiceRunCommand.StopService(Int32)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

 

Faulting application name: aemctl.exe, version: 2023.5.0.285, time stamp: 0x64be232d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff9c48218d9
Faulting process id: 0x1d50
Faulting application start time: 0x01da1be3f0dda833
Faulting application path: E:\Program Files\Attunity\Enterprise Manager\bin\aemctl.exe
Faulting module path: unknown
Report Id: 88a6494c-9ee9-4669-bce2-14eb75c47441
Faulting package full name:
Faulting package-relative application ID:

Labels (2)
2 Replies
OritA
Support
Support

Hi, 

Could you please open a support case for this issue and provide in the case the details of the scenario from which version did you upgrade? and attach to the case the QEM log with the error for further analysis. 

Thanks & regards, 

Orit

haung38
Contributor
Contributor

ya its a case of read the docs. Some are middleware generators where you call a function passing in a config... some are middleware ready to use and you just pass the function in.

A good way of telling is if you console log the function you'll see if it has the normal 3 param function... its middleware... if its anything else its a middleware generator/factory.