Support

Unless you are a time traveller, I assume you mean 2.2.0, not 2.2.1 :) This kind of installation issues can be worked around with our manual installation. Moreover, since you are on a virtual server, I'd recommend increasing the max_execution_time in your php.ini file to 90, so that Joomla! has ample time installing big software.

Did you try the manual installation instructions for which I gave you a link?

I wouldn't be so worried. First, let me explain what is the most likely cause of this issue. Admin Tools Professional is a big package with a lot of files. When you select "Upload & Install" the following have to take place:

1. PHP uploads the file to a temporary directory (not your site's tmp directory). The file will have to be copied to your site's tmp directory.
2. The ZIP archive will be read to memory
3. A new subdirectory will be created in your site's temp-directory
4. All of the files will be extracted to the temp-directory
5. The files will be copied to their final location
6. The database installation SQL script will run
7. The PHP post-installation script will run, copying some more files into libraries/fof
8. The temporary subdirectory and all contained files are removed

As you can see, there is a lot of file copying going on. File copying is a O(N) procedure, a geeky way to say that the amount of time it takes is directly proportional to the number of files being copied. Since so many file copy operation take place, it takes a LOT of time, leading to a timeout error on most shared hosts when installing moderately big packages (anything over 300-500Kb, the majority of Joomla! extensions). If you're using Joomla!'s FTP mode (every typical shared host requires this), things get even slower and the problem is more likely to occur. Moreover, step 2 may also cause a memory outage condition (the maximum amount of memory PHP can reserve is usually very limited on shared hosts). Each of these conditions will cause a blank page to show up, usually long before the installation had the chance to complete.

When you follow the manual procedure you skip steps 1, 2, 3, 4 and 8, reducing the necessary file operations by a whooping 75%. Moreover, you don't have to read the ZIP file into memory, therefore you don't run into memory outages. That's why the manual installation process has far more chances to run.

There is a lot of discussion going on in the Joomla! project these days about ways to circumvent these problems. I've made a proposal of my own, using the same method our Live Update software uses. The process is broken into multiple page loads. Each page load performs only one of the aforementioned steps, therefore minimising the chance of a timeout error. It doesn't deal with the memory outage condition, but it will be a good starting point. Hopefully this, or an equally competent solution, will be included by the time Joomla! 3.5 (the next long term support release) will be released in 18 months. Joomla! is scaling up as its components are also scaling up. With 2.7% of the Internet relying on its code being robust, I understand why the change process is slow. The first priority is making sure that every solution is well thought out and the proposed code is well tested before it hits the mainstream distribution :)