Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I've developed a QVW using QlikView 11 SR2 64 bit (Version 11.00.11414.0). This QVW has a report. However, when I view the QVW using QlikView Server, the Select Report drop down from the top menu bar is greyed out. Any ideas why?
Thanks !
I don't know why, but this solves it:
Go to Settings > Document Properties > Server and check "Allow Server Reports".
Could it be the user?
Have you shared the reports when creating them?
Doesn't appear to be the user, as I've tried using different users. As for sharing, the Share checkbox in the Edit Reports window in QlikView Developer is not checked (but I can't even check that box, which might be a different issue or bug altogether).
What's really odd is that it works in QlikView 9 SR4. The Server Reports checkbox in the Document Properties window...that doesn't need to be checked for users to view a QlikView report, right?
I met the same problem only on QV desktop.
I rebooted my computer and printed reports.
I don't know why, but this solves it:
Go to Settings > Document Properties > Server and check "Allow Server Reports".
That did it ! But yeah I don't know why that works either.
Oops forgot to reply to your message ! Glad rebooting worked there. Seems like a really strange bug !
Hello,
In my case the option "Allow Server Reports" has already been checked, un- und recheck didn't solve the problem.
The reason was, that there was no PDF-printer installed on the server, so installing PDF Creator did it for me.
Best regards,
Daniel
I figured why reboot seems to be working for many, I noticed the same problem a few days ago and was not sure what was wrong. Rebooting didn't work, however, this is what I noticed:
1. Print in the File menu was also disabled
2. I could not find any printers in control panel
3. My PDF printer was still installed but couldnt see in control panel.
Solution
1. Opened services.msc in Windows, searched for Printer Spooler service. Started this.
Everything worked from there on, as this service was set as Manual, the reboot had not also resolved it.