Just figured I'd add this bit of insight - not sure if it will help get to the bottom of this or not. I'm getting the same error. I have to try a couple things mentioned here, but in researching the error I've determined the following:
1) all scripts in the 04.04.00.SqlDataProvider file appear to have executed correctly with no errors.
2) It appears that in the Install.aspx code (or in some function call it is making), there is some funky issue in handling the results sent back from SQL Server after executing these scripts which causes the Install.aspx to believe there was a serious error during the setup of one of the scripts.
3) Then, in turn, the code in Install.aspx is apparently not engineered to handle the particular error code that is getting returned as is evident by the apparent attempt of Install.aspx to convert the path string into an integer (you'll notice the slashes are missing in the string it was apparently trying to convert to an integer).
4) The abnormal error returned by SQL Server appears to get handled after all the scripts in that file execute, but before the log file gets written. The actual error hanging the installation is the error in Install.aspx in trying to convert the path string (possibly an unexpected / unanticipated value for what is supposed to only be an integer error code) to an integer. Thus, the log file never gets written.
I may take a look at the Install.aspx code to see if I can figure out how to modify it to handle this unexpected error...