Skip to main content
Announcements
See why Qlik was named a Leader in the 2024 Gartner® Magic Quadrant™ for Data Integration Tools for the ninth year in a row: Get the report
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Invalid Request exception on opening QEMC

Hi All,

need your  assistance in below issue.

when we try to open QEMC, its throwing below error.

Invalid Request: Exception has been thrown by the target of an invocation.

when we try to restart the QDS services on Server, getting below error:

windows could not start the Qlikview Distribution service on Local computer

Error 1067: The process terminated unexpectedly.

we have rebooted all servers. still no use.

Any suggestions on how to resolve the issue?

thanks,

jyothi

2 Replies
martinpohl
Partner - Master
Partner - Master

maybe this helps

The first step to take is making sure the QVB is registered.

  1. Open windows file explorer
  2. Locate qvb.exe, default location C:\Program Files\QlikView\Distribution Service\
  3. Double click on qvb.exe to create the necessary Windows registry keys and GUID.
  4. Restart machine to make sure registry changes are properly applied

If the QlikView Distribution Service still can not be started, check and manually configure the permissions for the COM control. 

  1. Run "DCOMCNFG.EXE"
  2. Expand the Console Root  => Component Services => Computers => My Computer => DCOM Config
  3. Locate "QlikViewBatch 7.0 Application", right click and choose properties
  4. Select the "Security" tab, then "Customize" on the "Launch and Activation Permissions", and then press "Edit"
  5. Add the account that needs launch permissions (the service account running the QlikView Distribution Service)
  6. Check the options "Local Launch", "Remote Launch", "Local Activation", and "Remote Activation"
  7. Save and try starting the QlikView Distribution Service
  8. If it still fails, repeat steps 4-7 for the "Access Permissions" and "Configuration Permissions" sections on the "Security" tab

Regards

Not applicable
Author

Hi Martin,

Thanks for your reply. however i couldnt do the above as i do not have necessary permissions.

looks like it was a namespace issue which was later resolved by Active Directory team.

thanks a lot.