Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all articles
Browse latest Browse all 7696

Cannot Install 2008 R2 (Install_sqlncli_Cpu64_Action)

$
0
0

On my Windows 7 x64 SP1 box I already have installed the following:

  • Office 2010 x64
  • Visual Studio 2008 / SQL Server 2005 Express / .net 3.5 SP1
  • Visual Studio 2010 SP1 / .net 4 SP1 / MVC 3 tools

I then chose to install 2008 R2 Enterprise as an unnamed (default) new instance.  I added all features, except full-text search and (DTS) bacwards compatibility tools.  The system requirements test indicated everything was ready.  However, the entire installation failed within a couple minutes.  The only thing that installed successfully was the documentation.

For the installation, I had chosen mixed authentication and Latin1_General_100_BIN2 collation for the engine and SSAS. I used network and local service accounts for the installed services.

My summary.txt file contained:

  Exit code (Decimal):           -2068643839
  Exit facility code:            1203
  Exit error code:               1

Unlike examples of log output I've seen online, my summary file did not indicate any sub-log file to find additional error information within.  Following advice from akb article, I searched for "bucket," "exception" and "error:" in all .\setup bootstrap\log\*.txt files as such:

findstr -i -s -m error: *.txt

That search found the following:

Detail.txt: Slp: Error: Action "Install_sqlncli_Cpu64_Action" failed during execution.
Detail_ComponentUpdate.txt: Slp: Error: Action "PreMsiTimingConfigAction" failed during execution.
Detail_ComponentUpdate.txt: Slp: Error: Action "PostMsiTimingConfigAction" failed during execution.

When I do the same search, but for "exception," I find numerous messages like these:

  Detail.txt: Slp: Unable to mark feature SQL_Engine_Core_Inst as failed due to exception

At first I thought the problem might be with my installation media.  So I switched from a burned DVD, to using "Daemon Tools" to connect directly to the ISO on disk.  Didn't make any difference - the result and errors were the same.

What might be the problem?


-Brent Arias

Viewing all articles
Browse latest Browse all 7696

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>