I've running it on a test server 2012 R2 with .Net 4.6.1
It was an upgrade from 2.2.3.
Perhaps you can verify your .Net setup.
.NET 4.5.2 is verified .
the time out settings has been changed without any change.
Just performed a new clean re-install, and the Proxy Service is not started. When i try to uninstall again, i cannot because i cannot manually stop the scheduler service - get error 1061 - (only by terminating the scheduler.exe from "details" in task mgr and disabling the automatic startup , can i stop the scheduler service).
What can i do to ensure i make a complete, clean uninstall? Any files i should manually remove? Would it help to install 2.1.1 instead perhaps? could .NET 4.6.1 make a difference?
The current proces for uninstall:
1. Enter Task Mgr,
2. Enter "Services"
3. Enter Properties of all Qlik Services and disable automatic startup
4. Enter "Details" in task mgr and stop all ".exe" files related to the sense services
5. Enter Sense.Exe and choose "uninstall"
The end - removal of folders/certificates etc. i am missing, to get "a fresh start" ?
I am not the admin on the server (and neither very knowledgeable on this topic): What exactly should the Service Account be, regarding authorization and rights? Usually this is not a problem, as it is just an admin of some sort, but is there a specific set of rights it should have? a specific "type" of admin?
The service account has to have local admin rights. So it has to be member of the local group Administrators.
If the user you are using to install doesn't have this rights and the service account hasn't either that is probably causing your installation problems.
If you follow the installation guide these requirement are mentioned.
Just out of curiosity I cleaned my test system en did a clean install of 2.2.4. It installed flawless.
So I'm puzzled why it's not installing in your enviroment....
This is my configuration:
2 W2k12 R2 servers, one AD controller, one member server. Both fully updated. .Net 4.6.1.
I've run the installation with a own service account with local admin right.
One of our tech-wizards (#MegaNerds) finally found a solution by trawling all the log files.
It seems that if we rename the old installation folder to "qlik_old", and move everything else to a new drive (d: in this case), the installation ran smoothly - at least it did so the 2nd time...
So it seems there was an error in the first installation (perhaps relating to the timeout time of only 30 seconds at that time), which caused a lot of trouble when trying to uninstall, and then the uninstall probably left som "ghosts" lying around which gave some error messages trying to reach some postgre files in the qlik folder, without any luck...
So not quite clear what the error was - but it is fixed, and next time i will change the default timeout time before beginning the first installation, and make sure to use a new drive for any next installations, should there be an error like this again (most probable)
Thanks to everyone who contributed and tried to same my day ! It is much appreciated guys!
Have you tried this for the timeout?:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. In the right pane, locate the ServicesPipeTimeout entry. Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER
4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 120000, and then click OK. This value represents the time in milliseconds before a service times out.
Note: 120000 milliseconds (2 minutes) is equal to what the default configuration should be. You may find you need increase this number. 300000 (5 minutes) may be more suitable.
6. Restart the computer.