Hi Folks,

I started noticing that my add-in installs were painfully slow on my server. Given how many times I installed/uninstalled the HP updates and PP1 betas, and now with the 1.3 and PP1 releases, I was concerned that I perhaps missed a defect somewhere in the HP software. But even without the HP software on the server, it was still painfully slow (we're talking 10minutes for a small add-in install).

I finally used procmon to see what was going on and I quickly found the problem. My %QLOGS%/Additions.log file was MASSIVE and I saw WHS logging doing all sorts of lock/write/unlock operations on it. I removed the log file, and lo and behold, my add-in installation is back to its snappy self.

So why is the log file so huge? By the look of the log contents, Microsoft enables verbose msiexec logging when starting the add-in installs. A simple add-in install generates about 200K of log info; given how much I had been messing with add-ins on my server throughout the year, it's not wonder it was so massive (the first entries in the log dated back to December!) This will be an issue for pretty much any WHS user that has been installing and uninstalling add-ins.

So, if you've been doing lots of add-in installs/uninstalls, cleanup your Additions.log file -- you can either use the WHS Toolkit on the server to clean the logs, or RDP to the server, and move or remove %QLOGS%/Additions.log.

Jerry