Cannot Install 2008 R2 (Install_sqlncli_Cpu64_Action)

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 a
kb 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

Could you please unistall SQL Server Native client from Add/Remove program and try again?
If that still failes, please share the complete log folder with us. You can use any 3rd party file hosting sites to upload the data and share the link with us in next post.Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog: http://blogs.msdn.com/blakhani
Team Blog: http://blogs.msdn.com/sqlserverfaq

Similar Messages

Late 2008 mbp - installed new ssd - trying to boot from snow leopard iso on flash drive - says 'cannot install mac os on this computer'

Hello -
I just installed a new M500 Crucial ssd in my late 2008 mbp - everything was working fine on old hard drive (running snow leopard) but was getting slow and wanted to upgrade - i lost my snow leopard disk when moving from hawaii so i found an iso online - using a flash drive i partitioned the disk and made the bootable image on flash drive - formatted as extended/journaled - switched out the hard drives - plugged in the flash drive - started the comp - held option - install begins to boot - choose language - all is fine - choose english - next step window pops up saying 'cannot install os on this computer' - click on utility but all options are greyed out - disk util is greyed out - only options it gives is to start from backup or restart - real confused here - all help appreciated - thanks in advance and happy new year!

Snow Leopard comes in discs only. The USB drive may be a counterfeit and/or corrupt. There are two options for you:
Get replacement original OSX installation disks from Apple customer service. Have your MBP serial number ready and there is a charge.
Or two, purchase a Snow Leopard disk from the Apple online store:
http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard
Ciao.

Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

Xcelsius 2008 cannot install

Hi all,
A customer cannot install Xcelsius 2008 on XP Home 2002 with SP2, with Office 2003 installed. There error message are "Office XP application : Excel, Word, Outlook or Powerpoint must be pre-installed. Higher versions work fine". Anyone encounter this before?
Regards,
Derek

Per the supported platforms documentation (platforms.txt located in the installation files or media) the following is supported:
Supported Operating Systems
============================
Windows XP SP1   Professional
Windows XP SP2   Professional
Windows Server 2003   Enterprise Edition
Windows Server 2003   Standard Edition
Windows Server 2003 SP1 Enterprise Edition
Windows Server 2003 SP1 Standard Edition
Windows Vista
Windows Vista SP1
Windows Vista 64-bit
Other Tools
=============
Office      (Excel, PowerPoint, Outlook, Word)
Windows Office 2003
Windows Office 2003 SP1
Windows Office 2003 SP2
Windows Office XP SP3
Windows Office 2007
Unfortunately, your customer's XP Home version is not a supported operating system.

Cannot Install this Hardware - The system cannot find the file specified.

I got an 8G ipod touch last week. When I plug it into USB port on my PC, a Found New Hardware Wizard box pops up with "Cannot Install this Hardware", "There was a problem installing this hardware: Apple Mobile Device USB Driver", "An error occurred during the installation of the device", "The system cannot find the file specified.", "Click Finish to close the wizard.". If I go ahead and click finish, the device disappears and a couple of seconds later tries to install again and the box pops up again. However, if I leave the box alone, the ipod does actually appear in itunes and I can sync music to it, so all is not lost Any ideas though how to stop this error box popping up? The USBAAPL.SYS driver exists - I don't know what file it cannot find. Thanks.

Hi and welcome to Discussions,
if you have a Leopard OSX DVD you can use it to install the BootCamp 2.0 drivers and later use the BC Update 2.1 for XP to further update the drivers.
If not (still running OSX Tiger) there are two possibilities:
use this direct download link for the latest ATI/AMD Mobility Driver package http://ati.amd.com/online/mobilecatalyst/
or use the ModTool found here http://www.driverheaven.net/modtool.php in conjunction with the ATI/AMD Desktop Driver package.
You should also consider getting and installing the latest (June 2008) DirectX 9 package from Microsoft.
Hope it helps with your gaming problems.
Stefan

Cannot Install CS4 IM GOING CRAZY!

Hey everyone,
My problem is as follows: I cannot install any program in the CS4 Design Suite on my computer. This is not an upgrade, this is a fresh install.I know the packages are good because I installed them on my laptop with the same installers and it worked flawlessly.
I've encountered a few different issues, most of which I was able to resolve with a few minutes on google, but now I'm stuck on the same issue.
When I attempt to install, it goes through all of the steps, and once the progress bar reaches 100% it tells me the installation has failed.
The error message I receive is (this is what I get in Dreamweaver, however its essentially the same for all programs):
Adobe Dreamweaver CS4
Error:
Error 1603. Error 1335.The cabinet file 'AdobeDreamweaver10-mul1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Adobe Bridge CS4
Error:
Error 1603. Error 1335.The cabinet file 'AdobeBridge3All1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Adobe Device Central CS4
Error:
Error 1603. Error 1335.The cabinet file 'AdobeDeviceCentral2-mul1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Adobe ExtendScript Toolkit CS4
Error:
Error 1603. Error 1335.The cabinet file 'AdobeExtendScriptToolkit3.0.0All1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Adobe Extension Manager CS4
Error:
Error 1603. Error 1335.The cabinet file 'AdobeExtensionManager2All1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
I've tried clearing out my temp folder, uninstalling, then using both the Windows Install Clean Up Utility, and the CS4 Clean Up Script. I also installed a newer version of Windows Installer. I see this is a fairly common problem, but no solution I have found in various forums, sites, etc has worked for me. I've done essentially everything I can think of short of reformatting, which I'm not totally opposed to except for the fact I lost my Vista disk a few months ago.
Any help is greatly appreciated.

I had a very similar issue on a fresh installation of Windows 7, which I've detailed here. What worked for me:
Downloaded a fresh copy of the install package (mine was from Nov 2008) and unpacked it to the default location on the desktop
Deactivated and removed the registration number from one of the suite products that was installed (which deactivates the entire suite)
Uninstalled the entire CS4 suite
Rebooted
Ran the new install package from the default location (as Administrator)
Chose the default installation options
Did not enter the registration number during install
Did not touch the computer until it was done

Cannot install itunes 7.7 with Vista due to bonjour service issues

(I do have itunes version 7.6.2.9 working fine with no issues on vista)Cannot install itunes 7.7 becoz vista doesnt let bonjour service to run, While trying to start the Bonjour service from the Windows Services console gives an other error: "Windows could not start the Bonjour service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -65549." Is there any way I can get Bonjour to install and run as a service? tried switching off windows defender and Norton Internet security along with norton firewall too, still it doesnt let me install ,even tried downloading the windows version of bonjour but it too doesnt get installed as the service cannot start
Event report:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1013</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-07-11T12:32:31.000Z" />
<EventRecordID>69102</EventRecordID>
<Channel>Application</Channel>
<Computer>Revelations</Computer>
<Security UserID="S-1-5-21-216963075-3724653442-2767649758-1000" />
</System>
- <EventData>
<Data>Product: iTunes -- Service 'Bonjour Service' (Bonjour Service) failed to start. Verify that you have sufficient privileges to start system services.</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data />
<Data /> <Binary>7B45463643343630302D333036442D344636412D413131392D433241383737443235423 4417D</Binary>
</EventData>
</Event>
The Bonjour Service service terminated with service-specific error 4294901747 (0xFFFEFFF3).
Any comments and advice would be higly appreciated
regards
Message was edited by: Vistacrap
Message was edited by: Vistacrap
Message was edited by: Vistacrap
null

Apple offer this advice which I guess is not much help to you as you have Norton:
http://support.apple.com/kb/TS1609?viewlocale=en_US
I wonder if it is worth looking in the your firewall configuration>>Programs and deleting any entry for Bonjour - in the hope that you will be prompted to allow it or not when you do the install, or maybe adding it back with permit all.
But someone came up with another possible solution at the end of this thread:
http://discussions.apple.com/thread.jspa?threadID=1540617&tstart=0

Cannot install any version of IE

Hi there,
I am having some issues with one of our Terminal Servers, which is running Windows Server 2008 R2 64bit. It did have IE9 installed and when tried to upgrade this to IE10 or IE11 it was failing with the error "Internet Explorer did not finish installing".
There is no much helpful info in the event logs either.
So, following some other advice on here, I was pointed to the fact it could be that IE9 was corrupt and could be upgraded. I was advised to remove IE9 and try installing it again and then go through the upgrade process. However, there is an issue here. Once
IE9 was removed (through Uninstall an update in Control Panel), IE8 wasn't there. I still cannot install IE 9, 10 or 11 on this server now. What's also a concern is that now I cannot open Event Viewer or any other MMC as it shows an error about MMC will not
run with a version of Internet Explorer earlier than IE 5.5.
Any tips or ideas on how to resolve this?

You can ask them in IE forum: https://social.technet.microsoft.com/Forums/ie/en-US/home?forum=ieitprocurrentver
They are more familiar with this.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Cannot install hotfix kb2254157

Hello,
a customer is experiencing the exact problem as described below:
http://support.microsoft.com/kb/2254157
His laptop is running on windows 7 Professional SP 1 x64, windows updates are fully updated.
Using Outlook 2007 (12.0.6691.5000) SP3 MSO (12.0.6683.5000)
I've downloaded the correct hotfix: Windows 7/Windows 2008 R2 - All languages - x64
Since they also have a terminal server, running on windows 2008 R2, where they're having the same issue, I've also installed the hotfix there, without any problems.
I just cannot seem to install the hotfix on this laptop.
The error says: 'this update is not applicable for your system'
Windows logs are showing an error in the 'setup' section:
Event: 3, source: WUSA
Translated from dutch:
'Cannot install windows update due to error 2149842967 (path: "C:\windows\system32\wusa.exe" "C:\temp\Windows6.1-KB2254157-x64")
So I figure that there is some problem with wusa.exe not being able to install the hotfix (the c:\temp path).
The strange thing is that the laptop is able to install regular/normal windows updates, since the laptop is fully up to date.
I've already performed these steps:
http://support.microsoft.com/kb/971058/en
Still having the same issue installing the hotfix..
Any ideas? I'm quite stuck now.

Hi
Try resetting Windows
Update components and check if that
helps. To do so run the Fixit form
the link provided below.
http://support.microsoft.com/kb/971058
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Cannot install on 10.7.4 2x3 quad core Intel Xeon 16gb ram?

Cannot install on 10.7.4 2x3 quad core Intel Xeon16gb ram? any suggestions? Error Message "Mountain Lion not compatible with computer"
Thanks in advance

Welcome to Apple Communities
Open System Information and type the model identifier. With it, we can check if your computer is supported in 10.8. You can use OS X 10.8 if you use an Early 2008 or newer Mac Pro. If not, you can't use Mountain Lion

MOF syntax error occurred while installing 2008 SQL server Express on Vista Ultimate

I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.
Any ideas?
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htm

Similar error (not SQL Express but Enterprise) on my network reveals the following issue (still prevalent after removing and re-adding the machine to the network):
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/machinename.domainname.local. The target name used was cifs/MACHINENAME. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DOMAINNAME.LOCAL), and the client realm. Please contact your system administrator.
ALSO: The session setup from the computer MACHINENAME failed to authenticate. The name(s) of the account(s) referenced in the security database is MACHINENAME$. The following error occurred: Access is denied.
This default instance (Ent SQL 2008 on Ent Server 64 bit 2003 R2 SP2) failed with the MOF error using a service account to install SQL 2008. Repair does not work.   "The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature."
I expected to have more luck with the information here: http://mark.michaelis.net/Blog/CategoryView.aspx?category=.Net but wound up with result seen in my next post.
Of note, tried the removal of leftover registry entries after a failed install as in link above, also removed sql folders prior to re-install. Error is the same and rather than list entire log here, there is a portion available below but as is evident, there is a permission error in the registry which verifies what mark michaelis has pointed out:
"Sco: Compile operation for mof file \etcls.mof.transformed failed. Exit code 3" "Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC." "A MOF syntax error occurred." "Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC." Here is more: at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof() 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.EtwSetup.Install(String strInstanceName, Guid guidInstance, String strPath) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.SetupETW(EffectiveProperties properties) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install_ConfigNonRC_Prepare(EffectiveProperties properties) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream) 2009-03-31 10:51:19 Slp: Exception: Microsoft.SqlServer.Configuration.Sco.ScoException. 2009-03-31 10:51:19 Slp: Source: Microsoft.SqlServer.Configuration.Sco. 2009-03-31 10:51:19 Slp: Message: A MOF syntax error occurred.. 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key
(And so on - cannot read or write the registry key)...

Cannot install osx

Having followed Apple supports guidance s to how to begin to restore my early 2008 iMac in readiness to sell, I am now unable to install Snow Leopard OS from the original Apple DVD.. I select install from Disk Utility and then select the language which then immediately tells me that I cannot install OSX on this computer.
any suggestions please ?

Are you using a retail version of OS X or a machine-specific one? If you are using a Tiger disc for an iBook, and eMac, etc, it will not work.
iSMH

Cannot install new itunes

I cannot install new itunes, requires mac os x 10.6.8 and I do not know if this Mac OS version can run on my MacBook (2008 model)

Lion requires
Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor
2GB of memory
OS X v10.6.6 or later (v10.6.8 recommended)
7GB of available space
If not listed in the on-line store you will have to call Apple to order it

Cannot install Azure SDK2013 on Windows7

Dear Sir or Madam,
I cannot install Azure SDK 2013 on my laptop that is Windows7. Below is the failed photo. Please help me out!
Thanks a lot in advance,

hi Mike,
Thanks for your psoting!
Which version of Win7 installed on your laptop? Base on my experience, Windows 7 Home Basic is not supported. I suggest you could refer to those system information(http://www.microsoft.com/en-us/download/details.aspx?id=42317):
Supported Operating System
                    Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012, Windows
Server 2012 R2
                    Note: Windows 7 Home Basic is not supported.
Required Software:
Microsoft Visual Studio 2012/Microsoft Visual Studio 2013 OR
Microsoft Visual Web Developer 2012/Microsoft Visual Web Developer 2013 (only when installing the Windows Azure Tools).
IIS7 with ASP.NET and WCF HTTP Activation, Static Content, IIS Management Console and HTTP Redirection.
And the Azure tool could support the VS express 2013 for Web (http://msdn.microsoft.com/en-us/library/azure/ee405484.aspx). Please make sure your system is right.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Cannot install program after begin removed from Group Policy published programs

Hello,
We recently attempted to publish a program through Group Policy to allow users to install it but due to some requirements of the installer, it did not work. We removed it as a published program and now someone who attempted to install it through that method
cannot install the program at all. When they attempt to run the MSI from their local machine (not from a server share) they get an error saying "The feature you are trying to use is on a network resource that is unavailable". We tried putting a copy
of the MSI in the network location it was looking for (which is where it was when it was a published program) and ran in to the same errors as before when it was a published program.
When we ran the installer as a different user that had admin access the program installed correctly and without issue. To avoid having to run as a different user in case the computer only has one admin account, is there a way to clear the user account's
memory of the msi or something?
Thanks.

Hi,
Based on my knowledge, deployed msi application will be installed before the computer allows a user to logon if you choose Assign. Otherwise, you need to use Control Panel\Programs\Programs and Features\install a program from internet to get the msi
installed.
Did you mean to deploy a MSI file to each computers? Is it not the method written in this KB?
How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003
https://support.microsoft.com/kb/816102?wa=wsignin1.0#method6
If you just deploy a file from a shared network location, make sure that all your users has the permission to access the Network location.
Also, please check the policy under Applocker if there is any policy block the installation of MSI for your domain user except the admin account.
Kate Li
TechNet Community Support

Cannot Install 2008 R2 (Install_sqlncli_Cpu64_Action)

Similar Messages

Maybe you are looking for