[WiX-users] Burn Bundle: Behavior of a mixed x86 / x64 bundle where both MSIs have same ProductCode + UpgradeCode
Hi all,
We use normally the same ProductCode + UpgradeCode for x86 and x64
packages and exclude them by using a launch condition. (I know not
Windows Installer recommended but due to sake of simplicity e.g. when
creating two MSIs from one InstallShield solution done that way). Same
as now for WiX packages as they are normally excluded as well by
launchCondition. In that configuration the below described issues
occur.
As already legacy packages exist in such "bad" configurations a
workaround in bundle.wxs would be mostly appreciated.
Thanks and best regards,
Tobias
---
Full description of behavior:
bundle.wxs:
...
...
- Install works fine (only Bootstrapper1_20120808165620_0_x86.log generated)
---
Repair (on x86):
- [PLATFORM].msi: Reinstalled to default INSTALLDIR from MSI (It works
if only one MSI x86.msi or x64.msi is included.)
- Bootstrapper1_20120808165751_0_x86.log +
Bootstrapper1_20120808165751_1_x64.log are generated. (Regular install
only *_x86.log)
- Log:
[085C:0284][2012-08-08T16:57:50]: Burn v3.6.3206.0, Windows v5.1
(Build 2600: Service Pack 3), path: C:\Documents and Settings\test\My
Documents\visual studio
10\Projects\Bootstrapper1\bin\Debug\Bootstrapper1.exe, cmdline: ''
[085C:0284][2012-08-08T16:57:51]: Setting string variable
'WixBundleLog' to value
'C:\DOCUME~1\test\LOCALS~1\Temp\Bootstrapper1_20120808165751.log'
[085C:0284][2012-08-08T16:57:51]: Setting string variable
'WixBundleOriginalSource' to value 'C:\Documents and Settings\test\My
Documents\visual studio
10\Projects\Bootstrapper1\bin\Debug\Bootstrapper1.exe'
[085C:0284][2012-08-08T16:57:51]: Detect 2 packages
[085C:0284][2012-08-08T16:57:51]: Detected partially cached package:
x64, invalid payload: x64, reason: 0x80070570
[085C:0284][2012-08-08T16:57:51]: Detected package: x86, state:
Present, cached: Complete
[085C:0284][2012-08-08T16:57:51]: Detected package: x64, state:
Present, cached: Partial
[085C:0284][2012-08-08T16:57:51]: Detect complete, result: 0x0
[085C:0284][2012-08-08T16:57:53]: Plan 2 packages, action: Repair
[085C:0284][2012-08-08T16:57:53]: Condition 'Not VersionNT64' evaluates to true.
[085C:0284][2012-08-08T16:57:53]: Setting string variable
'WixBundleLog_x86' to value
'C:\DOCUME~1\test\LOCALS~1\Temp\Bootstrapper1_20120808165751_0_x86.log'
[085C:0284][2012-08-08T16:57:53]: Condition 'VersionNT64' evaluates to false.
[085C:0284][2012-08-08T16:57:53]: Plan disabled rollback for package:
x64, due to incomplete cache: Partial, original rollback action:
Install
[085C:0284][2012-08-08T16:57:53]: Setting string variable
'WixBundleLog_x64' to value
'C:\DOCUME~1\test\LOCALS~1\Temp\Bootstrapper1_20120808165751_1_x64.log'
[085C:0284][2012-08-08T16:57:53]: Planned package: x86, state:
Present, default requested: Repair, ba requested: Repair, execute:
Repair, rollback: None, cache: No, uncache: No, dependency: Register
[085C:0284][2012-08-08T16:57:53]: Planned package: x64, state:
Present, default requested: Absent, ba requested: Absent, execute:
Uninstall, rollback: None, cache: No, uncache: Yes, dependency:
Unregister
[085C:0284][2012-08-08T16:57:53]: Plan complete, result: 0x0
[085C:0284][2012-08-08T16:57:53]: Apply begin
[0968:04F0][2012-08-08T16:57:53]: Creating a system restore point.
[0968:04F0][2012-08-08T16:58:01]: Created a system restore point.
[0968:0AD0][2012-08-08T16:58:01]: Verified existing payload: x86 at
path: C:\Documents and Settings\All Users\Application Data\Package
Cache\{----}v1.00.0001.1000\x86.msi.
[0968:04F0][2012-08-08T16:58:01]: Applying execute package: x86,
action: Repair, path: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{----}v1.00.0001.1000\x86.msi,
arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"
INSTALLDIR=""'
[0968:04F0][2012-08-08T16:58:04]: Registering package dependency
provider: {----}, version:
1.00.0001.1000, package: x86
[085C:0284][2012-08-08T16:58:04]: Applied execute package: x86,
result: 0x0, restart: None
[0968:04F0][2012-08-08T16:58:04]: Registering dependency:
{----} on package provider:
{----}, package: x86
[0968:04F0][2012-08-08T16:58:04]: Removed dependency:
{----} on package provider:
{----}, package x64
[0968:04F0][2012-08-08T16:58:04]: Applying execute package: x64,
action: Uninstall, path: C:\Documents and Settings\All
Users\Application Data\Package
Cache\{----}v1.00.0001.1000\x64.msi,
arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"
INSTALLDIR=""'
[0968:04F0][2012-08-08T16:58:05]: Removed package dependency provider:
{----}, package: x64
[085C:0284][2012-08-08T16:58:05]: Applied execute package: x64,
result: 0x0, restart: None
[0968:04F0][2012-08-08T16:58:05]: Removing cached pa
Re: [WiX-users] Burn Bundle: Behavior of a mixed x86 / x64 bundle where both MSIs have same ProductCode + UpgradeCode
On 08-Aug-12 11:30, Tobias S wrote: > We use normally the same ProductCode + UpgradeCode for x86 and x64 > packages and exclude them by using a launch condition. (I know not > Windows Installer recommended but due to sake of simplicity e.g. when It's not a recommendation; it's a requirement: "The 32-bit and 64-bit versions of an application's package must have different product codes." Burn uses the product code to detect products so duplicates will cause it to fail. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Managed bootstrapper; BootstrapperApplication.Engine.Elevate()
On 07-Aug-12 17:23, John M. Wright wrote: > Did a sourceforge bug get created from the below email? If so, can you > point me to it so I can monitor it's status? If not, can one be generated? No. Feel free to file one. > In my case, I'm performing custom prerequisite checks that require elevated > security before I show the user what features are available to install and Elevating explicitly won't give your BA elevated privileges; Windows only lets processes elevate when they're created. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: WixStdBA crashes wih Access violation
Hi,
I'm working with the latest WIX version (v3.6.3206.0).
Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
Access violation reading location 0x0018.
After downloading the symbols from Wixtoolset.org, Visual Studio pinpointed
the exception to WixStandardBootstrapperApplication.cpp, line 558:
virtual STDMETHODIMP_(int) OnExecutePackageBegin(
__in_z LPCWSTR wzPackageId,
__in BOOL fExecute
)
{
if (wzPackageId && *wzPackageId)
{
BAL_INFO_PACKAGE* pPackage = NULL;
HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
wzPackageId, &pPackage);
LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
pPackage->sczDisplayName : wzPackageId;
m_fShowingInternalUiThisPackage = pPackage->fDisplayInternalUI;
// Error occurs in this line
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
}
else
{
m_fShowingInternalUiThisPackage = FALSE;
}
return __super::OnExecutePackageBegin(wzPackageId, fExecute);
}
When I try to peek into the members of pPackage, the debugger says "Unable
to read memory". I can peek into other objects without problems.
The line in question was introduced in version v3.6.3130.0, and I guess it's
missing a guard condition. If hr is E_NOTFOUND, pPackage will be null and
the whole thing crashes.
Kind regards,
Henning
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
On 08-Aug-12 12:00, Henning Krause wrote: > Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005: > Access violation reading location 0x0018. Please file a bug so it doesn't get lost in e-mail. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
Hi Bob, done: https://sourceforge.net/tracker/index.php?func=detail&aid=3555380&group_id=105970&atid=642714 Kind regards, Henning > -Original Message- > From: Bob Arnson [mailto:b...@joyofsetup.com] > Sent: Wednesday, August 08, 2012 6:32 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation > > On 08-Aug-12 12:00, Henning Krause wrote: > > Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005: > > Access violation reading location 0x0018. > Please file a bug so it doesn't get lost in e-mail. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
Does this crash happen at the end of the install? My users have reported a
problem when upgrading today and I updated the build to 3.6.3206 yesterday and
wonder if this is the same issue.
Neil
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: 08 August 2012 17:00
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Burn: WixStdBA crashes wih Access violation
Hi,
I'm working with the latest WIX version (v3.6.3206.0).
Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
Access violation reading location 0x0018.
After downloading the symbols from Wixtoolset.org, Visual Studio pinpointed the
exception to WixStandardBootstrapperApplication.cpp, line 558:
virtual STDMETHODIMP_(int) OnExecutePackageBegin(
__in_z LPCWSTR wzPackageId,
__in BOOL fExecute
)
{
if (wzPackageId && *wzPackageId)
{
BAL_INFO_PACKAGE* pPackage = NULL;
HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
wzPackageId, &pPackage);
LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
pPackage->sczDisplayName : wzPackageId;
m_fShowingInternalUiThisPackage = pPackage->fDisplayInternalUI; //
Error occurs in this line
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
ThemeSetTextControl(m_pTheme,
WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
}
else
{
m_fShowingInternalUiThisPackage = FALSE;
}
return __super::OnExecutePackageBegin(wzPackageId, fExecute);
}
When I try to peek into the members of pPackage, the debugger says "Unable to
read memory". I can peek into other objects without problems.
The line in question was introduced in version v3.6.3130.0, and I guess it's
missing a guard condition. If hr is E_NOTFOUND, pPackage will be null and the
whole thing crashes.
Kind regards,
Henning
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
Hi Neil,
no, it happens rather in the middle of it...
Kind regards,
Henning
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, August 08, 2012 7:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Does this crash happen at the end of the install? My users have reported a
> problem when upgrading today and I updated the build to 3.6.3206 yesterday
> and wonder if this is the same issue.
>
> Neil
>
> -Original Message-
> From: Henning Krause [mailto:m...@henningkrause.eu]
> Sent: 08 August 2012 17:00
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Hi,
>
> I'm working with the latest WIX version (v3.6.3206.0).
>
> Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
> Access violation reading location 0x0018.
>
> After downloading the symbols from Wixtoolset.org, Visual Studio
> pinpointed the exception to WixStandardBootstrapperApplication.cpp, line
> 558:
>
> virtual STDMETHODIMP_(int) OnExecutePackageBegin(
> __in_z LPCWSTR wzPackageId,
> __in BOOL fExecute
> )
> {
> if (wzPackageId && *wzPackageId)
> {
> BAL_INFO_PACKAGE* pPackage = NULL;
> HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
> wzPackageId, &pPackage);
> LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
> pPackage->sczDisplayName : wzPackageId;
> m_fShowingInternalUiThisPackage =
pPackage->fDisplayInternalUI; //
> Error occurs in this line
>
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
> }
> else
> {
> m_fShowingInternalUiThisPackage = FALSE;
> }
>
> return __super::OnExecutePackageBegin(wzPackageId, fExecute);
> }
>
> When I try to peek into the members of pPackage, the debugger says
> "Unable to read memory". I can peek into other objects without problems.
>
> The line in question was introduced in version v3.6.3130.0, and I guess
it's
> missing a guard condition. If hr is E_NOTFOUND, pPackage will be null and
the
> whole thing crashes.
>
> Kind regards,
> Henning
>
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat
> landscape has changed and how IT managers can respond. Discussions will
> include endpoint security, mobile security and the latest in malware
threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
That could be similar - the user report was a little vague! (I find my msi is
installed but then the burn UI doesn't return. I think I'll rollback to an
earlier release.
Neil
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: 08 August 2012 18:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
Hi Neil,
no, it happens rather in the middle of it...
Kind regards,
Henning
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, August 08, 2012 7:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Does this crash happen at the end of the install? My users have
> reported a problem when upgrading today and I updated the build to
> 3.6.3206 yesterday and wonder if this is the same issue.
>
> Neil
>
> -Original Message-
> From: Henning Krause [mailto:m...@henningkrause.eu]
> Sent: 08 August 2012 17:00
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Hi,
>
> I'm working with the latest WIX version (v3.6.3206.0).
>
> Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
> Access violation reading location 0x0018.
>
> After downloading the symbols from Wixtoolset.org, Visual Studio
> pinpointed the exception to WixStandardBootstrapperApplication.cpp,
> line
> 558:
>
> virtual STDMETHODIMP_(int) OnExecutePackageBegin(
> __in_z LPCWSTR wzPackageId,
> __in BOOL fExecute
> )
> {
> if (wzPackageId && *wzPackageId)
> {
> BAL_INFO_PACKAGE* pPackage = NULL;
> HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
> wzPackageId, &pPackage);
> LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
> pPackage->sczDisplayName : wzPackageId;
> m_fShowingInternalUiThisPackage =
pPackage->fDisplayInternalUI; //
> Error occurs in this line
>
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
> }
> else
> {
> m_fShowingInternalUiThisPackage = FALSE;
> }
>
> return __super::OnExecutePackageBegin(wzPackageId, fExecute);
> }
>
> When I try to peek into the members of pPackage, the debugger says
> "Unable to read memory". I can peek into other objects without problems.
>
> The line in question was introduced in version v3.6.3130.0, and I
> guess
it's
> missing a guard condition. If hr is E_NOTFOUND, pPackage will be null
> and
the
> whole thing crashes.
>
> Kind regards,
> Henning
>
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware
threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
I managed to reproduce the problem and downgrading to v3.6.3109.0 fixes it.
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 08 August 2012 18:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
That could be similar - the user report was a little vague! (I find my msi is
installed but then the burn UI doesn't return. I think I'll rollback to an
earlier release.
Neil
-Original Message-
From: Henning Krause [mailto:m...@henningkrause.eu]
Sent: 08 August 2012 18:21
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
Hi Neil,
no, it happens rather in the middle of it...
Kind regards,
Henning
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: Wednesday, August 08, 2012 7:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Does this crash happen at the end of the install? My users have
> reported a problem when upgrading today and I updated the build to
> 3.6.3206 yesterday and wonder if this is the same issue.
>
> Neil
>
> -Original Message-
> From: Henning Krause [mailto:m...@henningkrause.eu]
> Sent: 08 August 2012 17:00
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Burn: WixStdBA crashes wih Access violation
>
> Hi,
>
> I'm working with the latest WIX version (v3.6.3206.0).
>
> Unhandled exception at 0x0FF45EE6 (wixstdba.dll) Setup.exe: 0xC005:
> Access violation reading location 0x0018.
>
> After downloading the symbols from Wixtoolset.org, Visual Studio
> pinpointed the exception to WixStandardBootstrapperApplication.cpp,
> line
> 558:
>
> virtual STDMETHODIMP_(int) OnExecutePackageBegin(
> __in_z LPCWSTR wzPackageId,
> __in BOOL fExecute
> )
> {
> if (wzPackageId && *wzPackageId)
> {
> BAL_INFO_PACKAGE* pPackage = NULL;
> HRESULT hr = BalInfoFindPackageById(&m_Bundle.packages,
> wzPackageId, &pPackage);
> LPCWSTR wz = (SUCCEEDED(hr) && pPackage->sczDisplayName) ?
> pPackage->sczDisplayName : wzPackageId;
> m_fShowingInternalUiThisPackage =
pPackage->fDisplayInternalUI; //
> Error occurs in this line
>
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_EXECUTE_PROGRESS_PACKAGE_TEXT, wz);
> ThemeSetTextControl(m_pTheme,
> WIXSTDBA_CONTROL_OVERALL_PROGRESS_PACKAGE_TEXT, wz);
> }
> else
> {
> m_fShowingInternalUiThisPackage = FALSE;
> }
>
> return __super::OnExecutePackageBegin(wzPackageId, fExecute);
> }
>
> When I try to peek into the members of pPackage, the debugger says
> "Unable to read memory". I can peek into other objects without problems.
>
> The line in question was introduced in version v3.6.3130.0, and I
> guess
it's
> missing a guard condition. If hr is E_NOTFOUND, pPackage will be null
> and
the
> whole thing crashes.
>
> Kind regards,
> Henning
>
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware
threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Live Secur
[WiX-users] Checking whether Windows roles and features is installed
Hello, I'm working on an installer that requires numerous roles and features to be enabled. If those components are not available, the system, consisting of web applications, MSMQ, and SMTP server will fail to install, never mind run. Does WIX 3.6 support checking whether a Windows feature is installed? If not, what is the most appropriate manner to implement such a check? What comes to mind is to create a WIX extension, with a custom action that reads a MSI table to check whether the feature is available or not and fail with an appropriate message when its not. Are there tutorials showing how to write a sample WIX extension? However, if one were to chain several such MSIs together, isn't it perhaps more appropriate that such checking be done by bootstrapper created using burn? If that is the case, are there any tutorials/samples how to check for prerequisites without checking the registry? In this case we can use WMI to query Win23_ServerFeature whether a feature/role is installed or not. Thanks, Werner -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Passing information from bootstrapper application to msi packages
Hello, I wrote a native bootstrapper (using std win32 dialogs, rather than themes) which requests some data from users before proceeding to install and configure the product. This includes requesting the top level domain for websites and keys used to encrypt registry entries. Without it, installing the product will be rather complex, error prone and frustrating. How do I pass this information to the numerous MSIs being installed? I called SetVariableString of the underlying engine. However, it doesn't seem to have any effect. Thanks, Werner -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
