BI Publisher desktop won’t install

I’m running windows 7, 8 with office 2010, 2013 respectively.  Have oracle 11G client.  I’m using this machine for some Report development.

But, I keep getting: “Template Builder Installer failed": Unexpected Error”

People are putting all sorts of stuff on forums that look like pot shots.  “Try uninstall and install again” – huh???,  but computers generally do the same thing given the same input.

How about I find some log files and go from there.

C:\Users\AmitGupta\AppData\Local\Temp has TemplateBuilderInstaller.log – WOW!  direct hit.

This has:

Word process check start
Error No.: 339
Description: Component 'MSCOMCTL.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

WOW again, direct hit.

I need to install this file, mscomctl.ocx does not exist on my machine

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=25437d98-51d0-41c1-bb14-64662f5f62fe&displaylang=en

download this file, and install it.  You can install this on 64 windows.

Right…  That did not work, even when I tried the repair…  Damn!

I tried a few other things, and then.

http://www.ascentive.com/support/new/support_dll.phtml?dllname=MSCOMCTL.OCX

Downloaded this file (MSCOMCTL.OCX)

And then put this file C:\Windows\SysWOW64 location.

Restart the installation!

tar: 0511-195 An error occurred while writing to the storage media.

tar: 0511-195 An error occurred while writing to the storage media. There is an input or output error.

The error log is always descriptive on what the problem is, so it is helpful to take a look. 
similar issues that I have seen, have been caused by the following errors:

Firmware issues: You need to look and insure you have the most up to date firmware for your drive. 
Media: Bad media can create similar issues, but this would show up on the error log. You can verify by trying a different tape. 
Cleaning: This will also show up on the error logs, but this is one of the most common problems with tape drives. 

This error can be media or tape but is generally an incorrect setting in the backup. 

File Size Issue: See if any file is over 8GB that you are trying to tar. If any individual file is over 8GB then exclude it from getting tar-ed.

Command Issue: This error occurred when you type /dev/rmto instead of /dev/rmt0 (wrongly used alphabet ‘o’ instead of digit’0’).