Home Dashboard Directory Help
Search

Error during install SQL Server 2008 R2 Express (Local setup100.exe returned exit code: 0x3906094D) by pb_dev


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 770618
Opened: 11/9/2012 7:49:03 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Hello, I have problem with MSSQL 2008 R2 Express installation. setup100.exe always returned exit code: 0x3906094D. I need solution, but I don't found it. Please, help me. Thank you for your suggestion.

=== SqlSetup_Local.log ===
Setup launched
Attempting to determine media source
Media source: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\
Attempt to determine media layout based on file 'C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\mediainfo.xml'.
Media layout is detected as: Core
Setup.exe is running locally no check for a slip stream media
/? or /HELP or /ACTION=HELP specified: false
Help display: false
Checking to see if we need to install .Net version 2.0
Checking to see if we need to install MSI version 4.5
RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
Attempting to get Windows Installer version
Windows Installer version detected: 4.5.6001.22159
RedistMSI::IsVistaRTM - Not Vista RTM build
Required version of Windows Installer is already installed
.Net version 2.0 is already installed.
Windows Installer version 4.5 is already installed.
Strong name verification disabling is not required
/? or /HELP or /ACTION=HELP specified: false
Help display: false
Attempting to launch landing page workflow
Attempting to set setup mutex
Setup mutex has been set
Attempting to launch global rules workflow
Media source: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\
Install media path: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\x86\setup\
Media layout: Core
Attempting to get execution timestamp
Timestamp: 20121107_165145
Attempting to run workflow RUNRULES /RULES=GlobalRules
Attempting to launch process C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
Process returned exit code: 0x00000000
Workflow RUNRULES /RULES=GlobalRules returned exit code: 0x00000000
Attempting to launch component update workflow
Media source: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\
Install media path: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\x86\setup\
Media layout: Core
Attempting to get execution timestamp
Timestamp: 20121107_165145
Attempting to run workflow COMPONENTUPDATE
Attempting to launch process C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
Process returned exit code: 0x00000000
Workflow COMPONENTUPDATE returned exit code: 0x00000000
Attempting to launch user requested workflow locally
Attempting to find local setup.exe
Local bootstrap folder path: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\
Local setup100.exe full path: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
Media source: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\
Install media path: C:\Documents and Settings\Haltmar\Local Settings\Temp\is-4Q68G.tmp\MSSQL2008Express\x86\setup\
Media layout: Core
Attempting to get execution timestamp
Timestamp: 20121107_165145
Attempting to run user requested action from local setup100.exe
Attempting to launch process C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
Process returned exit code: 0x3906094D
Local setup100.exe returned exit code: 0x3906094D
Attempting to release setup mutex
Setup mutex has been released
Setup closed with exit code: 0x84C40013
Details
Sign in to post a comment.
Posted by Microsoft on 11/13/2012 at 6:28 AM
Thank pb_dev, we will take a look.

thanks,
[SQL Server Team]
Posted by pb_dev on 11/13/2012 at 12:35 AM
Hallo, logs was attached, thank tou.
Posted by Microsoft on 11/12/2012 at 3:22 PM
Hi pb_dev, thanks for taking the time to report this issue. In order to facilitate further investigation could you attach setup logs to the connect item?

thanks,
[SQL Server Team]
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
SqlSetup_Local.log 11/13/2012 9 KB
SqlSetup.log 11/13/2012 6 KB
HW_Info.xml 11/13/2012 18 KB
InnoSetup Log 2012-11-07.txt 11/13/2012 2 KB
SqlSetup_Local.log 11/13/2012 9 KB
SqlSetup.log 11/13/2012 6 KB
HW_Info.xml 11/13/2012 18 KB
InnoSetup Log 2012-11-07.txt 11/13/2012 2 KB