Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Folks,
great way to start a Friday.
Just had a call from a client who have rebooted the QV server earlier today as is now getting:
All service are up and running, they use a domain account as the service user. We have advised them to restart the services but to no avail.
I suspect this may be a DNS issue:
I have seen other threads that recommend changing to use Local host, but do you actually change it against the Qlikview Server Name e.g
and the same place against the other services?
bbt
Any suggestions please!!
Cheers Andy
Hi Guys,
Just done the following:
The issue appears to be a corrupted profile on the service user account, would recommend that you create a new Domain user to run the services as a member of local administrators and Qlikview Administrators
Yippee, thanks for the pointers guys!
Happy Andy
"Disconnected" usually means that accounts, permissions, or network connections have changed. When a service reports a "Disconnected" status, the real explanation of the problem is detailed in the corresponding log file.
It would be nice if we could take a peek in those three QlikView service log files...
Best,
Peter
BTW it's funny that the services are running on one server (first screenshot), but the configuration talks about another server (last screenshot, bottom field called "URL")...
Is your customer running a cluster, or trying to configure one?
Ha ha, the second URL is a screen shot from my PC, well spotted though
Andy
Hey Andrew,
Hmmm. Could be a DNS issue. Have you tried substituting IP address instead of servername in the URLs for each of the disconnected services? So, for example, for DSC, in QMC, navigate to System > Setup > Directory Service Connectors > DSC@ > General tab > URL.
Hope this helps
-Chip
Hi Chip,
not yet, I am just awaiting the log files to come back from the client.
Andy
Hi Peter / Chip
Please see log files in attached zip, I'm struggling to spot anything helpful in them...
Andy
Andrew,
Need the Management Service logs as well.
Chip
Chip is right. QMS is the one reporting problems.
However, the DSC log tells a good story. Apparently there appears to be a problem when trying to reach the domain controller (or LDAP server if that's what your client is using) If accounts are defined on server LDAP://bunzl.internal and that one cannot be reached, in an AD landscape all sorts of things start going wrong...
Maybe a track to investigate?