Sitecore package install never ends
After a lot of research in Sitecore.Kernel.dll I found the solution. After the "INFO Committing files." log entry there was another entry: "Job started: WatchStatus". This Job never ended.
The ItemInstaller
is responsible for the "Installing item:" logs and the BlobInstaller
is responsible for the "Installing of blob values has been finished" log.
In the InstallPackageForm
class, the function WatchForInstallationStatus()
is responsible for the "Job started: WatchStatus" logmessage. This function starts a new thread in which it checks the status of the package installation which is stored in the temp folder.
In my case, the IIS_IUSRS role did not have write rights on the temp folder. After I changed it, it worked.
This is what the log file should look like:
ManagedPoolThread #7 12:45:57 INFO Committing files.
ManagedPoolThread #11 12:45:57 INFO Job started: WatchStatus
ManagedPoolThread #7 12:45:57 INFO Job ended: Install (units processed: )
ManagedPoolThread #11 12:45:58 INFO Job ended: WatchStatus (units processed: )
ManagedPoolThread #8 12:45:58 INFO Job started: InstallSecurity
ManagedPoolThread #8 12:45:58 INFO Installing security from package: <package>
For anyone else that has this issue that might be in the same way that I had it. I had the exact same problem, but not quite with the same stack traces as defined above.
My problem was that I didn't have MongoDB installed/running, and that caused it to hang, throwing many errors in the logs. Doing a simple install and a couple setup commands with the pre-defined connection strings seemed to kick it into gear just fine.
After the default installation of 8.0 Update 4 you need to run mongo manually.
The easiest way is to install mongo by default and run it from command prompt as: mongod.exe --dbpath c:\example_of_my_mongo_database_dir
The best way is to install it as a windows service - http://mikerobbins.co.uk/2015/02/02/install-mongodb-as-a-windows-service-for-sitecore/
As soon as you do that - you'll be able to install the packages without any problem.
It worked for me after I have given write permissions to IIS_IUSRS for website folder on Inetpub.
Its bit strange as I already got full permissions to APPPooluser on website folder.