Discussion:
[WiX-users] Simple MSI failing: Error 3: -2147287038
JoeMarks
2014-02-19 10:50:03 UTC
Permalink
Hi everyone!

I was doing some changes to an existing installer, and I needed to enable
.Net 3.5 on Windows 8.
This can easily done with the comand "dism.exe /online /enable-feature
/featurename:NetFX3 /all /NoRestart".

So I was doing a simple Installer to add to my Bootstrapper that would run
this command.
The code is below:



The problem is that the setup keeps failing when installing... log is below:






Google didn't show much, tried some custom UI, running as Admin (I already
am Administrator)

I'm testing this on a VM with windows 8.1, running the setupo from the
Desktop. Also I'm using Wix 3.8 with Visual Studio 2012

Any help will be much appreciated.

PS: Sorry if you received this topic more than once, I had some issues with
the mailing list subscription.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771.html
Sent from the wix-users mailing list archive at Nabble.com.
Phil Wilson
2014-02-19 17:06:11 UTC
Permalink
That error is just a "%1 could not be found.", implying that something
(most likely dism.exe?) could not be found.

I see no trace of the code you used - didn't make it into your post.
---------------
Phil Wilson
Post by JoeMarks
Hi everyone!
I was doing some changes to an existing installer, and I needed to enable
.Net 3.5 on Windows 8.
This can easily done with the comand "dism.exe /online /enable-feature
/featurename:NetFX3 /all /NoRestart".
So I was doing a simple Installer to add to my Bootstrapper that would run
this command.
Google didn't show much, tried some custom UI, running as Admin (I already
am Administrator)
I'm testing this on a VM with windows 8.1, running the setupo from the
Desktop. Also I'm using Wix 3.8 with Visual Studio 2012
Any help will be much appreciated.
PS: Sorry if you received this topic more than once, I had some issues with
the mailing list subscription.
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
JoeMarks
2014-02-19 17:51:11 UTC
Permalink
I thing the mailing list hides the "raw" text, it's only visible on the
thread in here
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-td7592771.html>

Even if I remove the CustomAction from the installer i get the same log
file, so I guess it might not be the CustomAction. But I still don't know
what it is...

The command exists, and executing it on the Command Prompt works
beautifully, but it never gets executed on my installer.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592781.html
Sent from the wix-users mailing list archive at Nabble.com.
Carter Young
2014-02-19 18:06:59 UTC
Permalink
See:
http://support.microsoft.com/kb/834484

Is the dsim tool your executing meet the criteria discussed in the
article. If the tool is mapped as a Network drive:

* The drive that contains the folder that you are trying to install
the Windows Installer package to is accessed as a substitute drive.

is TRUE

Carter
Post by JoeMarks
I thing the mailing list hides the "raw" text, it's only visible on the
thread in here
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-td7592771.html>
Even if I remove the CustomAction from the installer i get the same log
file, so I guess it might not be the CustomAction. But I still don't know
what it is...
The command exists, and executing it on the Command Prompt works
beautifully, but it never gets executed on my installer.
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592781.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Phil Wilson
2014-02-19 18:37:23 UTC
Permalink
The log is available on stackoverflow, has no evidence that it is
trying to run a custom action, and contains this line:

MSI (s) (04:D4) [17:20:10:936]: PROPERTY CHANGE: Adding REMOVE
property. Its value is 'ALL'.

So it does not appear to be the failing install log, I think the same
MSI is being run again, and maybe going into automatic uninstall for
some reason.
---------------
Phil Wilson
Post by JoeMarks
I thing the mailing list hides the "raw" text, it's only visible on the
thread in here
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-td7592771.html>
Even if I remove the CustomAction from the installer i get the same log
file, so I guess it might not be the CustomAction. But I still don't know
what it is...
The command exists, and executing it on the Command Prompt works
beautifully, but it never gets executed on my installer.
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592781.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
JoeMarks
2014-02-19 18:53:19 UTC
Permalink
@eyoung100: So it mean I can't test this on a Virtual Machine?

@Phill: Yes, I also posted this question on stackoverflow to improve my
chances of getting an answer :)
That sounds interesting, any way to check if the installer is indeed being
run again?

Thank you for your replies.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592786.html
Sent from the wix-users mailing list archive at Nabble.com.
Carter Young
2014-02-19 19:06:55 UTC
Permalink
AFAIK, you can test this on a virtual machin as long as the installer
is started from a non networked drive. IE, on the Virtualbox Virtual
Disk, but none of the shared folders you mapped as Drives...

Carter
Post by JoeMarks
@eyoung100: So it mean I can't test this on a Virtual Machine?
@Phill: Yes, I also posted this question on stackoverflow to improve my
chances of getting an answer :)
That sounds interesting, any way to check if the installer is indeed being
run again?
Thank you for your replies.
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592786.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
JoeMarks
2014-02-19 19:21:40 UTC
Permalink
I'm running the installer on Desktop, so it's not on a Networked drive.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592788.html
Sent from the wix-users mailing list archive at Nabble.com.
Phill Hogland
2014-02-19 19:24:40 UTC
Permalink
Your call to dism has the path '[WindowsFolder]SysWOW64\dism.exe'. If you
open an Admin CMD box and type your full command you will get a better
explanation of the error. SysWOW64 specifies the 32 bit operating system
files. Error 11 is returned which indicates that you cannot service a
running 64 bit image with the 32 bit version of dism.exe.

On a 64 bit system you would want to use [System64Folder]dism.exe.

I have also been working on this issue and find that it is not uncommon to
come across Windows 8 installations which have the NetFx3 feature 'payload
removed', which also causes dism.exe to fail. However in this situation I
find that "[System64Folder]fondue.exe" /enable-feature:NetFx3 /hide-ux:all
succeeds.

fondue.exe is not available pre VersionNT < 602.

I am still researching some of these issues, but I hope this infor helps.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592789.html
Sent from the wix-users mailing list archive at Nabble.com.
JoeMarks
2014-02-19 19:53:36 UTC
Permalink
Yes, you are correct, after some search I got to this thread
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-dism-exe-in-my-custom-action-td3667299.html>

So by setting the command to [WindowsFolder]Sysnative\dism.exe would fix
that, but my problem persists...



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592790.html
Sent from the wix-users mailing list archive at Nabble.com.
Carter Young
2014-02-19 20:15:32 UTC
Permalink
Is your Desktop mapped to a roaming profile??
Post by JoeMarks
Yes, you are correct, after some search I got to this thread
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/using-dism-exe-in-my-custom-action-td3667299.html>
So by setting the command to [WindowsFolder]Sysnative\dism.exe would fix
that, but my problem persists...
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592790.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Phill Hogland
2014-02-19 20:21:27 UTC
Permalink
Did you type that command in a Admin CMD box and see what happens? It does
not work for me either.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592792.html
Sent from the wix-users mailing list archive at Nabble.com.
JoeMarks
2014-02-20 10:24:56 UTC
Permalink
@eyoung100: no, I dont have any roaming profile.

@Phill Higland: the command prompt recognizes de command dism on any
directory, so maybe we don't even have to specify a directory to it. It
works for me just as "dism.exe /online /enable-feature /featurename:NetFX3
/all /NoRestart"



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592801.html
Sent from the wix-users mailing list archive at Nabble.com.
Phil Wilson
2014-02-20 17:52:22 UTC
Permalink
Just jump in with a reminder that there is an MSI log for this issue
and there is no custom action being called for dism.exe, so based on
that log this is not a CA issue with running dism.exe.

The VersionDatabase property is 100, so it's pretty old.

InstallInitialize fails, the error in the vicinity is 2205, indicating
a required table may be missing. It seems to indicate there is no
Component table in the MSI file. If that's the case it may explain the
strange behavior. Yes, this MSI file may have no Component table!
---------------
Phil Wilson
Post by JoeMarks
@eyoung100: no, I dont have any roaming profile.
@Phill Higland: the command prompt recognizes de command dism on any
directory, so maybe we don't even have to specify a directory to it. It
works for me just as "dism.exe /online /enable-feature /featurename:NetFX3
/all /NoRestart"
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Simple-MSI-failing-Error-3-2147287038-tp7592771p7592801.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Loading...