Installation error for Exchange Server-2013

I am trying to install exchange server-2013 on my Windows server-2012
machine. I have configured per-requisite applications and develop the server environment with active directory roles.
At my readiness check option, it shows the following error:-
"An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later and windows server-2012".
I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
Regard
Azad
Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through the
exchange 2013 management shell
"Get-Exchangeserver"
However still not able to connect to https://localhost/eac and when i re-run setup
01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
[01-28-2014 21:10:16.0804] [0] **********************************************
[01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
[01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
[01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
[01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
[01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
[01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
[01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
[01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked:
[01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
[01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
[01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
[01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
[01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
[01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
[01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
[01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
[01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[01-28-2014 21:10:39.0664] [0] Applying default role selection state
[01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
[01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
[01-28-2014 21:15:30.0513] [0] End of Setup
[01-28-2014 21:15:30.0513] [0] **********************************************

Similar Messages

If the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

if the Microsoft Forefront Protection 2010 for Exchange Server can use for exchange server 2013?

thanks for your reply!
what's protection software can use for exchange server 2013?
Hi,
Most (if not all) of the bigger vendors has a product that supports Exchange 2013, so look them up.
Exchange 2013 has some Anti-Spam and Anti-Malware Protection functionality that you can read about here:
http://technet.microsoft.com/en-us/library/jj150481(v=exchg.150).aspx
Martina Miskovic

Sizing IIS ARR for Exchange Server 2013

Hi Everyone,..
I planned to publish Exchange 2013 through IIS ARR server, but I've had trouble finding any data on CPU / memory usage for a dedicated ARR server based on Microsoft recommendation. There are 8000 users that will be access from ARR server.
Hopefully you can help for sizing so
there isn't bottleneck on that server.
Thanks
~IH~

Hi Irfan
The concurrent connections depends upon appConcurrentRequestLimit which has a default value of 5000. I think you need to increase this if in your case the concurrent connections exceed 5000
I have found few articles for your reference
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/achieving-high-availability-and-scalability-arr-and-nlb
http://blogs.technet.com/b/tristank/archive/2008/03/11/maxuserport-what-it-is-what-it-does-when-it-s-important.aspx
https://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
https://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
Its better to submit this to http://forums.iis.net/ since this is more kind of IIS related issue and you will get better response
Good Luck !!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Why is installation file for Exchange Server CU7 much smaller than SP1.iso?

I was wondering why is the ISO-Image for Exchange Server 2013 with SP1 4.5 GB in size and the CU7.EXE only 1.6 GB? I thought CU7 contains everything SP1 contains. Is it because one is a disk image and an other an executable?

The EXE is compressed. When you extract it, it should be close to the same size (probably bigger) than the SP1 iso.
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

Cumulative Update 5 for Exchange Server 2013 (KB2936880)

Hi,
i have installed exchange server 2013 on separate servers, I deployed the Mailbox role on the first server, and the CAS role on the second server.
I checked the edition using the exchange management shell on the mailbox server and on the CAS server:
>>>
[PS] C:\Windows\system32>Get-ExchangeServer | fl name,edition,admindisplayversion
Name : EXMBX
Edition : Standard
AdminDisplayVersion : Version 15.0 (Build 516.32)
Name : EXCAS
Edition : Standard
AdminDisplayVersion : Version 15.0 (Build 516.32)
<<<
My question is, is it possible to update this current edition to the "Cumulative update 5 for Exchange Server 2013 (KB293688) ?
if it is, in my case, on which servers should i install this update ? on the Mailbox server ? or on the CAS server ?
i appreciate you fast response,
Thanks.

Hello,
It doesn't matter which build you choose: you should first update the mailbox role and then CAS. The best option is to have same version of all your Exchange servers (e.g. CU5).
It is not necessary to install Exchange binaries on DC.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Autoinstaller for Exchange Server 2013

Hi folks,
We are developed exchange installation package (save time purpose) for internal usage but release public now.
this tool will install automatically exchange 2013 CU7 on server. All requirments include this setup for exchange. We are be inspired from Michel de Rooij's powershell script.
Package Setup
http://maestropanel.cubecdn.net/A1/PackageMsExchange2013.exe
Sorry documentation is Turkish currently.
http://wiki.maestropanel.com/maestropanel-paketi-ile-exchange-server-2013-kurulumu/
Thanks ;)
www.maestropanel.com Web Hosting Control Panel

Hi
Thanks for sharing but what kind of error reporting do you have if the installation fails?
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.

Cumulative Update for Exchange Server 2013

Dear All,
I have installed exchange server 2013 RTM version , I want to install the
Cumulative Update on my exchange server , i need to know all
Cumulative Update are required for the my Exchange 2013. or just last one is get all 1 to 7 Cumulative Update.

Exchange Update Rollups are cumulative. Cumulative Updates include all previous cumulative updates. so CU7 is enough.
Regards
John

SOFS support for Exchange Server 2013

Hi all,
I am aware of the following factors:
1. Exchange only supports block-level storage
2. Using SoFS as DAG FSW is not supported.
But may I confirm whether Microsoft supports the scenario below?
==============================================
My client has one set of Windows 2012 R2 Scale-Out File Servers to support their hyper-V farm. Storage is Dell MD3000 with Windows 2012 R2 Storage Space. Is it supported by Microsoft to run Exchange Server 2013 and Exchange Server 2010 in the virtual machines
which are running on SoFS? Assume IOPS has been properly sized.
==============================================
Regards,
William
William Yang

Hi,
There is no official documents talked about whether the Windows server 2012
Scale-Out File Server is supported for Exchange 2013 and Exchange 2010.
Generally, the supported storage configuration in Exchange 2013 is listed in the article below:
https://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
Hope it helps.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Package files of Installation SBA for Lync Server 2013

Hi everyone,
It´s my first post and would like know where can found the files of installation for Lync Server 2013 SBA (Survivable Branch Appliance).
My appliance is a module SRE-910 with Router 2911
I contacted the microsoft and they said that the files are provided from cisco.
The Guide that I´m following is this:
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=28555
Question posted in forum Microsoft:
http://social.technet.microsoft.com/Forums/en-US/lyncvoice/thread/81a0d1e2-39f2-45ad-9908-f4162e9d302f
Quote of Site Microsoft about software and Hardware requeriments to SBA:
"Required hardware and software is built into the Survivable Branch Appliance"
Someone can give a light ?
Thanks in advance!

http://blogs.technet.com/b/xdot509/archive/2012/10/24/installing-a-two-tier-pki-hierarchy-in-windows-server-2012-part-ii-installing-a-root-certification-authority-with-the-gui.aspx

Error when trying to configure Lync to be a partner application for Exchange Server 2013

When I attempt to run the Configure-EnterprisePartnerApplication.ps1 script I get the following error:
The address 'LyncEnterprise-ApplicationAccount@*.domain.com' is invalid:
"LyncEnterprise-ApplicationAccount@*.domain.com" isn't a valid SMTP address. The domain name can't contain spaces and it has to have a prefix and a suffix, such as example.com.
The error continues with some more things, but what I can't understand is why it is adding a *. after the @ when it is trying to create the account.
Any help would be appreciated, thanks!

Hi ADrake04,
I found that the script was configured as below:
$acceptedDomains = Get-AcceptedDomain;
if ($acceptedDomains -eq $null)
WriteError ("There is no accepted domain so user can not be created.")
$acceptedDomain = $acceptedDomains[0].Name;
if($UseDomainController -eq $true)
$user = New-MailUser -Name $username -DomainController $DomainController -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true -DomainController $DomainController
else
$user = New-MailUser -Name $username -ExternalEmailAddress $username@$acceptedDomain;
set-mailuser -Identity $user.Identity -HiddenFromAddressListsEnabled $true;
WriteInformation ("Created User <$($user.Identity)> for Partner Application.");
return $user;
Please note the variable “$acceptedDomain”,
this is a very important point.
(Note: The acceptdomain is used in Exchange, and can be created in Exchange EAC )
Now what you need to do is to run the following command in Exchange Powershell and see the result.
$acceptedDomains
= Get-AcceptedDomain
$acceptedDomains[0].Name
If you see the result “*.Domain.com”, then you should check your Exchange Configuration.
Best regards,
Eric

Copiar bases de datos Error en Exchange Server 2013

. Hola a todos
Estoy Tratando de Copiar las bases de Datos de Buzones de Exchange 2013 Llegue Cuando El Estado de la copia con el comando get-MailboxDatabaseCopyStatus
error tengo el siguiente:
[PS] C: \ Windows \ system32> Get-MailboxDatabaseCopyStatus *
Nombre Estado CopyQueue ReplayQueue LastInspectedLogTime Contentin
Longitud Longitud Estado ---- ------ --------- ----------- ------------- ----- - ---------
DAG_DB001_Nivel0 \ PROBMMCDTEXC001 Error 11707 0
DAG_DB002_Nivel1 \ PROBMMCDTEXC002 Error 11585 0
IncomingLogCopyingNetwork: {PROBMMCDTEXC002, ReplicationDagNetwork01, error de la ONU ha Producido Durante la Comunicación
. Con El Servidor 'PROBMMCDTEXC002'
Error: No Se Puede Escribir Datos en el transporte de
Conexión: Con La Conexión establecida FUE abortada
Por software el en su Anfitrión .
Máquina} ?
Cualquier del Sugerencia Saludos.
Hello everyone
Trying to solve the problem ran the following command update-MailboxDatabaseCopy Database -Identity \ MBX2 -DeleteExistingfiles
but it generates the following error message.
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: An error occurred while Communicating with server 'PROBMMCDTEXC002'. Error: Unable to read data from the transport connection: A connection Attempt failed Because
the connected party did not answer-Properly after a period of time, or established connection failed Because connected host has failed to respond.
i appreciate your collaboration

Hi,
Based on this error, I suggest to manually seed the databases by copying the databases over to the passive node.
Or try the following method.
Remove the server from the DAG with this command:
Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer ServerName –ConfigurationOnly
Then did a node eviction from the Windows Failover Cluster:
Import-Module FailoverClusters
Get-ClusterNode EX2 | Remove-ClusterNode –Force
Then mounted the DB's outside the DAG
Then built a new DAG from scratch, made new DB's and started a migration of the users from the evicted node to the new DAG.
Similar thread:
https://social.technet.microsoft.com/Forums/windows/en-US/5f975863-fd85-4d88-9df6-739d320f7b54/database-seeding-failed-as-exchange-dr-side
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Installation Error for SQL Server 2008 R2 on windows vista

2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: TIMESTAMP
2014-09-20 07:49:26 Slp: Value specified: 20140920_074907
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: LOGMARKER
2014-09-20 07:49:26 Slp: Value specified: _ComponentUpdate
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: INSTALLMEDIAPATH
2014-09-20 07:49:26 Slp: Value specified: C:\Downloaded\SQL Server 2008\x86\setup\
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Setting: MEDIALAYOUT
2014-09-20 07:49:26 Slp: Value specified: Full
2014-09-20 07:49:26 Slp: New setting source: CommandLine; previous setting source: Default
2014-09-20 07:49:26 Slp: ----------------------------------------
2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessMediaChainerConfigFileArguments
2014-09-20 07:49:26 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessChainerConfigFileArguments
2014-09-20 07:49:26 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ProcessSlipstreamParameters
2014-09-20 07:49:26 Slp: Completed Action: ProcessSlipstreamParameters, returned True
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
2014-09-20 07:49:26 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:26 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
2014-09-20 07:49:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:26 Slp: Running Action: ValidateChainerSetting
2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
2014-09-20 07:49:26 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : NormalizePid found null or empty pid
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
2014-09-20 07:49:26 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=EVAL(0x2467BCA1)
2014-09-20 07:49:27 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
2014-09-20 07:49:27 Slp: Completed Action: ValidateChainerSetting, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureCommandLineArguments
2014-09-20 07:49:27 Slp: ----------------------------------------
2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
2014-09-20 07:49:27 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ProcessFeatureConfigFileArguments
2014-09-20 07:49:27 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: StartSqmSession
2014-09-20 07:49:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:49:27 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2014-09-20 07:49:27 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
2014-09-20 07:49:27 Slp: Completed Action: StartSqmSession, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ValidateSettingsAgainstScenario
2014-09-20 07:49:27 Slp: Scenario: ComponentUpdate
2014-09-20 07:49:27 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
2014-09-20 07:49:27 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: SetComponentUpdateScenarioFlags
2014-09-20 07:49:27 Slp: Completed Action: SetComponentUpdateScenarioFlags, returned True
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: ExecuteInitWorkflow
2014-09-20 07:49:27 Slp: Workflow to execute: 'INITIALIZATION'
2014-09-20 07:49:27 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:27 Slp: Running Action: InitializeMsiExtension
2014-09-20 07:49:29 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:49:29 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100\Bootstrap
2014-09-20 07:49:29 Slp: Completed Action: InitializeMsiExtension, returned True
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Skipping Action: InitializeConfigAction
2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableExternalMsiConfiguration set" did not pass as it returned false and true was expected.
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Skipping Action: RunDiscoveryAction
2014-09-20 07:49:29 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:49:29 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
2014-09-20 07:49:29 Slp: Completed Action: ExecuteInitWorkflow, returned True
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Running Action: ExecuteStartUiWorkflow
2014-09-20 07:49:29 Slp: Workflow to execute: 'STARTUI'
2014-09-20 07:49:29 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:29 Slp: Running Action: InstallWizard
2014-09-20 07:49:29 Slp: Start Action: ComponentUpdate
2014-09-20 07:49:29 Slp: Configuration file: C:\Downloaded\SQL Server 2008\x86\configuration.uicfg
2014-09-20 07:49:30 Slp: Adding registration information 'ShowWizard' for type 'Microsoft.SqlServer.Management.ActionHandlerInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'InstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'InstallClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'AddNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RemoveNode' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PrepareClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'CompleteClusterWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'UninstallWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'UpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'ComponentUpdate' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RepairWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RunRulesUI' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'EditionUpgradeWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'RemovePatchWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'PrepareImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: Adding registration information 'CompleteImageWizard' for type 'Microsoft.SqlServer.Management.ActionInfo'
2014-09-20 07:49:30 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
2014-09-20 07:49:31 Slp: Completed Action: InstallWizard, returned True
2014-09-20 07:49:31 Slp: ----------------------------------------------------------------------
2014-09-20 07:49:31 Slp: Running Action: GatherUserSettings
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize is initializing using input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Read lcid 1033 from CultureInfo
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Pid validation of input pid '[PID value hidden]' succeeded, resulting edition is 'DATA_CENTER' channel 'OEM'
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : Initialize called ValidatePid, output is pid=[PID value hidden] validateSuccess=True output editionId=DATA_CENTER(0xC5AA9665)
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings initialized private object, result is initializeResult=Success
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid is normalizing input pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPrivateConfigObject : NormalizePid added dashes to pid, output pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings proceeding with normalized pid=[PID value hidden]
2014-09-20 07:50:22 Slp: -- PidPublicConfigObject : ValidateSettings found pid=[PID value hidden] is already validated and initialized.
2014-09-20 07:50:22 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
2014-09-20 07:50:25 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:25 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2014-09-20 07:50:25 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
2014-09-20 07:50:25 Slp: License file: C:\Downloaded\SQL Server 2008\1033_ENU_LP\x86\1033\License_DC_OEM.rtf
2014-09-20 07:50:25 Slp: Completed Action: GatherUserSettings, returned True
2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:25 Slp: Running Action: RegisterRetryHandler
2014-09-20 07:50:25 Slp: Completed Action: RegisterRetryHandler, returned True
2014-09-20 07:50:25 Slp: Completed Action: ExecuteStartUiWorkflow, returned True
2014-09-20 07:50:25 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:25 Slp: Running Action: NotifyProgressCountDisplay
2014-09-20 07:50:26 Slp: Completed Action: NotifyProgressCountDisplay, returned True
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: ExecuteCalculateScenarioWorkflow
2014-09-20 07:50:26 Slp: Workflow to execute: 'CALCULATESCENARIO'
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: ClearCalculatedState
2014-09-20 07:50:26 Slp: Completed Action: ClearCalculatedState, returned True
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping Action: SetUninstallEnableInstallMatchingByInstanceId
2014-09-20 07:50:26 Slp: Action is being skipped due to the following restrictions:
2014-09-20 07:50:26 Slp: Condition "Is the user's scenario set to Uninstall" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgInstanceName of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableDiscoverableProducts set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgSqlInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgASInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Skipping property ArgRSInstanceId of class: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Input of property will not be set due to the following failed restriction(s):
2014-09-20 07:50:26 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/EnableInstallMatchingByInstanceId set" did not pass as it returned false and true was expected.
2014-09-20 07:50:26 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:26 Slp: Running Action: SetFeatureInstallStateAction
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_Cpu32: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:26 Slp: Package ID sql_engine_core_inst_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_fulltext_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_engine_core_shared_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_as_spi_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_Cpu32: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:27 Slp: Package ID sql_rs_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_rs_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_is_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_tools_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_Cpu32: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:28 Slp: Package ID sql_bids_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_bids_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_Cpu32: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_ssms_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_Cpu32: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1028: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1031: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1033: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1036: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1040: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1041: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1042: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1046: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1049: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_2052: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_3082: NotInstalled
2014-09-20 07:50:29 Slp: Package ID sql_common_core_loc_Cpu32_1053: NotInstalled
2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction" threw an exception during execution.
2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: --- End of inner exception stack trace ---
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2014-09-20 07:50:29 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2014-09-20 07:50:29 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion ---> System.ArgumentNullException: Value cannot be null.
2014-09-20 07:50:29 Slp: Parameter name: productVersion
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: --- End of inner exception stack trace ---
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-09-20 07:50:29 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-09-20 07:50:33 Slp: Received request to add the following file to Watson reporting: C:\Users\Kimi Raikkonen\AppData\Local\Temp\tmpB4ED.tmp
2014-09-20 07:50:33 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-09-20 07:50:33 Slp: Inner exceptions are being indented
2014-09-20 07:50:33 Slp:
2014-09-20 07:50:33 Slp: Exception type: System.ArgumentNullException
2014-09-20 07:50:33 Slp: Message:
2014-09-20 07:50:33 Slp: Value cannot be null.
2014-09-20 07:50:33 Slp: Parameter name: productVersion
2014-09-20 07:50:33 Slp: Stack:
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion(String value)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallPropertyByProductCode(PackageInstallProperty pkg, String prodCode)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.FillInstallProperty(PackageInstallProperty pkg)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.ExecuteAction(String actionId)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2014-09-20 07:50:33 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2014-09-20 07:50:43 Slp: Watson Bucket 1
Original Parameter Values
2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2014-09-20 07:50:43 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion
2014-09-20 07:50:43 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallProperty.set_ProductVersion
2014-09-20 07:50:43 Slp: Parameter 3 : System.ArgumentNullException@-2147467261
2014-09-20 07:50:43 Slp: Parameter 4 : System.ArgumentNullException@-2147467261
2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction
2014-09-20 07:50:43 Slp:
Final Parameter Values
2014-09-20 07:50:43 Slp: Parameter 0 : SQL Server 2008 R2@RTM@
2014-09-20 07:50:43 Slp: Parameter 1 : 0x2AA348CC
2014-09-20 07:50:43 Slp: Parameter 2 : 0x2AA348CC
2014-09-20 07:50:43 Slp: Parameter 3 : 0xF15156D0
2014-09-20 07:50:43 Slp: Parameter 4 : 0xF15156D0
2014-09-20 07:50:43 Slp: Parameter 5 : SetFeatureInstallStateAction
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
2
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
2014-09-20 07:50:44 Slp: Value cannot be null.
Parameter name: productVersion
2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: Error result: 1269611253
2014-09-20 07:50:46 Slp: Result facility code: 940
2014-09-20 07:50:46 Slp: Result error code: 47861

2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32
error 2
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-09-20 07:50:43 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-09-20 07:50:43 Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
2014-09-20 07:50:44 Slp: Value cannot be null.
Parameter name: productVersion
2014-09-20 07:50:44 Slp: Watson bucket for exception based failure has been created
2014-09-20 07:50:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey
2014-09-20 07:50:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2014-09-20 07:50:44 Slp: Sco: Attempting to get registry value DW0200
2014-09-20 07:50:46 Slp: Submitted 1 of 1 failures to the Watson data repository
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: ----------------------------------------------------------------------
2014-09-20 07:50:46 Slp:
2014-09-20 07:50:46 Slp: Error result: 1269611253
2014-09-20 07:50:46 Slp: Result facility code: 940
2014-09-20 07:50:46 Slp: Result error code: 47861
Hi,
For above error the error code is 2 which means system cannot find the file specified. It is saying it is unable to write at location which means SQL server account does not have access to
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140920_074907\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
You can manually go to the location and add required rights may be installable is corrupt
Now did you ran SQL server setup as administrator. Always right click on setup.exe file and select run as administrator.
Please make sure you disable antivirus running on machine. Also if you have any registry scanner software which scans registry remove it as well.
Below thread might be helpful
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/d425791a-9a7c-4c16-9e93-d348ecde3a3f/sql-server-2008-r2-install-fails-on-win-2008-r2-x64-std-server-with-workflowxmltext-msg-error-help?forum=sqlsetupandupgrade
Can you also post summary.txt file
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Installation error for security update 2013-004 version 1.0

Hi,
I receive a 'unexpected error' message when I try to install security update 2013-004 version 1.0. I have tried updating from computer and manually downloading 'security update 2013-004', but still receive the exact same error message. I'm on a macbook pro mid 2011, Mac OS X Lion 10.7.5.

Try verifying your hard disk with Disk Utility in the Utilities folder.
After launching Disk Utility, in the left pane, click on the name of your hard disk.
In the right pane, click the First Aid tab and then click the Verify Disk button.
If the result is OK, then click the button to Repair Disk Permissions.
If the Verify Disk test result reports errors, you will need to reboot the computer in Recovery HD and use Disk Utility there to repair the disk. See instructions by Kappy.
Afterwards, try installing the security update again.
As for the cause of the unexpected error, look at the log reports with Console in the Utilities folder.
HTH

BAM Portal configuration error in BizTalk Server 2013 R2

I have tried 2 attempts to build out a BizTalk Server 2013 R2, I have followed the MSDN Install instructions, and I keep on getting an error when configuring BAM Portal. I have the logfile available, I need to know what the experts need to see in order to
give me an answer. Understand that we have been using BizTalk Server 2013 for the last two years, and a new developer wants the R2 version and BAM Portal configured. As an administrator I have fought this to no end, and now I have enough evidence to go back
to our project manager and explain why you do not install every feature on a server. Prove me wrong EXPERTS!

" I need to know what the experts need to see in order to give me an answer."
Experts needs:
1) Little background of the issue you are facing.
2) The log file generated.
3) The configuration of your server.
"now I have enough evidence to go back to our project manager and explain why you do not install every
feature on a server."
Disagree, It is indeed possible to install all the components and feature on a server. Somewhere someone would have installed BizTalk 2013 R2 and all its components in exactly same server configuration successfully in which you are trying to achieve, the
only difference could be a missing Package, Patch, Cumulative Update, Service or any configuration miss at your end.
Pls read more about BizTalk 2013R2 installation on Installation Overview for BizTalk Server 2013 and 2013 R2.
Review the Hardware
and Software Requirements for BizTalk Server 2013 and 2013 R2.
Understand the Considerations
Before Installing BizTalk Server 2013 and 2013 R2.
Prepare Your Computer for Installation.
Specifically for BAM Portal. Microsoft has documented Prerequisites, Permissions and Considerations.
Planning for the BAM Portal
I would advice you to refer this post by Sandro . BAM Portal configuration error
Rachit

Messaging tracking logs filename format changed in Exchange Server 2013 sp1

Hi,
I have noticed that the file name format is changed for exchange server 2013 sp1.
Now it will have hh attached to it like
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
So the "hh" will goes from 00 to 23 for single day.
So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
And also how it will be decided to create the first file @ 7.30 AM.
Can anyone explain to me about this ? Why it is happening like this?
Thanks
Sandeep Gupta

Hi Sandeep,
This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
were created on 20140411.
Also, as you mentioned, the file name format is as:
MSGTRKMSyyyymmddhh-n.log;
MSGTRKMDyyyymmddhh-n.log:
MSGTRKyyyymmddhh-n.log.
However as I know, the format is like
MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
and the date/time information of the file to verify.
Title: Message Tracking
Link:
http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
Regards, Eric Zou

Installation error for Exchange Server-2013

Similar Messages

Maybe you are looking for