Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I am new to Qlikview and am attempting to access the existing reports we have on a dedicated machine, but are running into some serious challenges. We are running Qlikview Personal Edition 9 and have it installed on a dedicated machine that is only accessed by the account that is registered to Qlikview; AccountQ. Our issue is that there are two of us that may access that computer to work on the reports; User1 and User2.
User1 accesses the computer through his local machine using RDP (Remote Desktop Connection), but runs his RDP session as a network administrator account. He then logs into the Qlikview machine using the registered account AccountQ. He is then able to login to Qlikview and access the QV application and modify/create reports as needed.
User2 access the computer through his local machine using RDP and then logs into Qlikview using the registered account AccountQ. He is able to launch the QV application, but receives the error message below:
"Your installation of QlikView has exceeded the maximum number of document recoveries allowed for a Personal Edition license. To continue using QlikView you will need to purchase a full QlikView license..."
Options attempted:
Somehow, even though both users are logging into the remote machine that runs the QV reports as the registered account (AccountQ), it is still tied to some level of network account that is being used to run Remote Desktop Connection. But, it is only accepting a very specific user's network admin account (both users' network admin accounts have the same level of access to this server and the network). This poses several concerns as to what kind of tie QV has with users since this poses risks going forward; User1 is unavailable to work on reports as requested (vacation, illness, leave of absence, exit from the company, etc...), the ability to modify or create new requests is immediately stopped.
I am hoping we can get this resolved rapidly as this issue really puts us in a bind with our ability to move forward.
Ok, so I was able to figure out the issue and it is very simplistic in its resolution, but something that would not normally be thought of as an issue. Apparently QV when it is registered with an Active Directory user, it is case-sensitive; whereas, AD does not care. In case someone else runs into this issue, I wanted to list out what we did to resolve the issue:
AD Username: Admin
QV registered name (same AD account as above): admin
It does not matter the login used to execute the RDP session, what matters is the account logged into the remote server (and does not require a console or admin login, it can just be a remote session).
launch RDP and observe workstation login prompt:
Login as "Admin":
Login as "admin":
So, even though it is using the same AD account (which AD does not care about case sensitivity on username), QV requires the exact login typed when the application was registered/installed on the machine (which does care about case sensitivity).
Hi Chris,
With what you are doing, it sounds like you should strongly considering purchasing a QlikView license. Personal Edition is intended for private/personal use. I'm not sure why the scenario above is producing those results since the document is saved with information tied to the document creator (which appears to be User 1's network admin account instead of AccountQ), but it ultimately sounds like you're attempting to share an account to get around the license limitations of the free personal edition.
Simply put, QlikView Personal Edition is the full QlikView Desktop product that is run on a machine without a customer or partner license assigned to it. With the QlikView Personal Edition license, everyone is free to create QlikView documents for personal use. If at any point you or your organization decides to acquire a full QlikView license, this Personal Edition installation will automatically become a full QlikView client without requiring any additional software.
If you have never licensed QlikView before and want to use the tool to perform analysis on any sort of business or personal data set, or have an existing QlikView installation and want to try out our latest release, QlikView Personal Edition is for you; download and start connecting to all of your data sources and building your analysis applications.
If you have data available in an Excel file, starting up QlikView will take you through a simple process to get your data loaded and your first QlikView built within 5 minutes. There are several video tutorials available to help you get up an running quickly.
There are only two limitations while using QlikView with the Personal Edition license:
Yes, but you need Mac software that will allow you to install and emulate a Windows environment, before you install QlikView within that environment. As an alternative, Mac users can access QlikView apps deployed on a server through Safari and other supported browsers. You can access one of our demo apps to experience the power of QlikView.
Please read carefully: Technically, every document is now saved with a user key -- information that ties that file to the file's creator. In Personal Edition, users can only open files that they have created.
We recognize that it may be necessary to install QlikView on a different computer (i.e. computer upgrade, replacement, etc.). In order to open documents created using the previous installation of QlikView, you will need to "recover" the files. Recovering files simply means that you are assigning an updated user key (old machine -> new machine) to these documents. When you recover a file, you are telling QlikView that you are moving this file to your new installation, and you will no longer be using it on your previous installation.
IMPORTANT: QlikView Personal Edition is limited to four recoveries per installation. When you recover a QlikView file created with a previous installation, it will apply your new user key to ALL documents created using the previous installation, not just that particular file.
DO NOT attempt to open QlikView files that you did not create (from the forums, created by a colleague, etc.) Doing so will use one of your remaining recovery attempts, and once you have exhausted all 4 of the attempts, you will no longer be able to access documents that you have created and, from that point on, you will only be able to create new documents using your current QlikView installation.
As mentioned above, QlikView Personal Edition can only open files created locally by that same installation.
Yes. We post new releases on the web using our QlikView download page. You can re-download QlikView at any point and install an updated version on your existing machine and continue working with documents that you have already created. NOTE: If you have exhausted your recovery attempts, downloading a new version or re-downloading the same version will not reset the counter.
Personal Edition users do not qualify for telephone or email support from QlikTech. As a Personal Edition user, you can gain excellent QlikView support through our active user community, QlikCommunity. We've created the dedicatedNew to QlikView area of QlikCommunity for Personal Edition users to get to information on how to start using QlikView as well as allow you to interact with other members of the community.
Hi Chris,
With what you are doing, it sounds like you should strongly considering purchasing a QlikView license. Personal Edition is intended for private/personal use. I'm not sure why the scenario above is producing those results since the document is saved with information tied to the document creator (which appears to be User 1's network admin account instead of AccountQ), but it ultimately sounds like you're attempting to share an account to get around the license limitations of the free personal edition.
Hello Josh,
Thanks for the reply, but this is not a licensing issue; or at least it should not be based on how we access and utilize the program/machine.
Down to its basic form, we have a machine that is ONLY accessed by the account registered to the QV application. Because we have this machine only accessible remotely, we RDP into the machine. The oddness listed in my initial post is the scenario of running RDP from our workstations. Once the login screen appears for the destination machine, it is only ever accessed by the single account (AccountQ). This is the oddness that there is some part of the application is still pulling in the domained account that is running the RDP session and not the AD account used to access the machine.
As far as licensing, we have purchased licenses in the past and assign and remove them as needed; so again, this is (or should not be) a licensing issue. Just as an additional step, we rebooted the machine during our maintenance window this weekend but are still receiving the errors.
Thanks in advance for any assistance.
- Chris
Ok, so I was able to figure out the issue and it is very simplistic in its resolution, but something that would not normally be thought of as an issue. Apparently QV when it is registered with an Active Directory user, it is case-sensitive; whereas, AD does not care. In case someone else runs into this issue, I wanted to list out what we did to resolve the issue:
AD Username: Admin
QV registered name (same AD account as above): admin
It does not matter the login used to execute the RDP session, what matters is the account logged into the remote server (and does not require a console or admin login, it can just be a remote session).
launch RDP and observe workstation login prompt:
Login as "Admin":
Login as "admin":
So, even though it is using the same AD account (which AD does not care about case sensitivity on username), QV requires the exact login typed when the application was registered/installed on the machine (which does care about case sensitivity).
How will I know the login type when the application was registered/installed on the machine