
We had a similar issue this morning. The cause (found from looking in the installation log) was a full database (for some reason it was set to 100MB max size with no autogrow) - this was also causing other issues which have now been resolved. I had to use the 103302.sql query after fixing the problem and before trying the update again.
As ||||||| said, post your errors from the log file
