Yes.

You must find the reason why Native Client had failed. Based upon the discovered reason, you must take an action before attempting another install. The action you must take depends upon what C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log states is the error.

However, if C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is not the very first setup error (i.e. if the first setup error's date & time was not 2014-08-13T08:00:58), you must find the very first summary text file for the very first setup failure, under a folder that is named C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\YYYYMMDD_HHMMSS. The summary text file within that folder might point you to a sqlncli_Cpu64_1.log file. The log file will not be in the same folder as the sqlncli_Cpu64_1.log file (mentioned above). You must inspect those setup files, not the latest files, for the cause of the very first failure.

To state the above in another way:

{

If C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is the file for the earliest setup failure, than that is the file that needs to be inspected. You did not provide us with that file.

On the other hand, I\f C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is not the file being pointed to by the EARLIEST setup failure's summary text file, the log file is academically interesting but pragmatically useless - you must uncover the very first error.

}

For example, if that very first summary text file for the very first setup error reported that a reboot is required, and if you have not rebooted Windows since that time, then all subsequent setup attempts will fail and you must reboot Windows.

As another example, if you see a message that says setup was interrupted (please paste in complete and verbatim error messages, not colloquial summaries of them), you must address why the setup had been interrupted (my use of the past tense is intentional). The cause for that interruption will definitely not be within the latest setup files. You will only see a message about setup being interrupted when you try to run setup again, but without having addressed/fixed the cause of that interruption. In this example, the cause of the original setup error (the interrupted setup) will always be within an earlier setup file.