
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
QVCONNECT64.exe doesn't run because it isn't 'signed'
So far so secure.
However, here's the 'kicker'...
Since, our policy prevents execution of unauthorised programs from %temp% (a common vector for virus attacks) when QV.exe runs a script and extracts the ODBC EXE connector into %temp%
I get:
Failed to start connector: QvConnect64.EXE
System error: This program is blocked by group policy. For more information, contact your system administrator.
Any workarounds/solutions would be gratefully received.
HEY QLIK ! - why do you run the ODBC connector this way?
You already have copies of QVCONNECTnn.EXE in the QV Program folders AND they are digitally signed so I can run them from anywhere.
- Tags:
- qlikview_deployment
.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Duplicate post, see the following link: https://community.qlik.com/t5/QlikView-Connectors/QVCONNECT64-exe-doesn-t-run-because-it-isn-t-signe...
Regards,
Brett
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
