Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Tyler.
Can you help me. I'm have dev server w2012r2 with installed QV 12 desktop, QV 12 server. I'm deinstall QV 12 server and install QS 3.0. and faced with problem - operaion monitor not reload.
Reload stop on line " LIB CONNECT TO 'qrs_user';"
with error "Could not fetch connection by name using identifier qrs_user: LIB CONNECT TO 'qrs_user'"
Operations_Monitor_Reload_Stats_3.0.0.txt in attach and task log too
I think may be the cause of conflict with any previously installed QVRestConnetor, but why Licence monitor reload success.
Hi Tyler,
I have created Archive folders but still it is not loading , Please help me to fix it
This is a Qlik-supported app, so you can submit a help ticket.
What they (and I) would ask for are:
Hi Tyler, I am sharing required details below:
1. Version : 3.2.4
2. Error in log:
FROM JSON (wrap on) "root" PK "__KEY_root"
2017-06-12 20:54:43 18 fields found: userId, userDirectory, __FK_owner, id_u1, __KEY_app, __FK_app, id_u2, createdDate, modifiedDate, modifiedByUserName, description, objectType, publishTime_u0, published_u0, approved, name_u2, __KEY_root, __extra_,
2017-06-12 20:54:43 Error: QVX_UNEXPECTED_END_OF_DATA: DNS error
2017-06-12 20:54:43 Execution Failed
3. Single node
4. No virual proxy
5.Prior version 3.2.2
6. No shared persistence.
Please let me know if you need more details.
Aha - DNS error.
Make sure your DNS is working okay -- you might need to run the ip flush (I forget the exact command) or check the data connection URL for the qrs_app for example. Is it pointing to "localhost" or to a server name?
Below path is mentioned in QRS_APP connection:
CUSTOM CONNECT TO "provider=QvRestConnector.exe;url=http://localhost/qrs/app/full;timeout=180;method=GET;autoDetectResponseType=true;keyGenerationStrate..."
I am trying to run IP flush command , will update you
Weird. So the server that is reloading the Operations Monitor is not resolving the "localhost" DNS.
I confess this is a bit out of my expertise (I would tell you DNS = donuts )
Hi Tyler,
Okay, I agree we don't know how to resolve it, just help me to know, what exactly happened and what precaution I will take to avoid it ?
When in doubt, use the fully-qualified domain name (FQDN) instead of "localhost" in the data connections.