Re: [WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-07 Thread Phill Hogland
I'm sorry, I do not quite understand what you mean by 'provided targets'.  I
used the following command in the Post Build event for the bundle project: 
(The certificate was previously imported into a local  catalog.  This is the
same command that I also use in the Post Build event for my MSI project,
which has been working without issue.)



VS2010 Post-build Event:
$(WindowsSDKDir)\signtool.exe sign /n cert name /d desc
$(TargetDir)$(TargetFileName)

The build log says:
C:\Program Files (x86)\Microsoft 
SDKs\Windows\v7.0A\Bin\signtool.exe
sign /n cert name /d desc path to bundle
project\bin\Debug\Mysetup.exe
Done Adding Additional Store
Successfully signed: path to bundle 
project\bin\Debug\Mysetup.exe

I saw in another thread an example that signed engine.exe but I did not
quite understand how to apply that to my project.

Thanks for the assistance.  Phill




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845p7587861.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-07 Thread Phill Hogland
I just read the doc for Insignia more carefully and I think I see what I am
doing wrong.  I had originally not used insignia because it seemed to be
needed for signing 'external CABs' and I am not using an external CAB.  But
I now see how it is use to extract the engine.exe from a bundle.  I will
work on implementing this approach.  sorry for the noise.  The 'unspecified
error' was a distraction for me, but will look at using insignia.
Thanks;
Phill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845p7587862.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-07 Thread Phill Hogland
Mission accomplished! thanks for the assistance.
Phill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845p7587864.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-06 Thread Phill Hogland
I have a bundle which has three EXE and 1 MSI, all third-party, and then my
MSI for a total of five packages.  This is my first bundle and it has been
installing on a Win 8 x64 test system successfully.  I install and uninstall
on this test box, rather than going back to a clean OS as I have WinDbg and
VS also installed so that I can step into the code.

I had figured out the MSI localization some time ago, but reset the VS
culture parameter to english, and removed the post build steps to embed the
mst files and sign the msi, to save time in doing test builds as I developed
the bundle.  Now I am happy with the bundle so I added those msi
localization and signing steps back into the build process, and I added
signing to the bundle for the first time.

Now the setup always fails while trying to process the first EXE package
(which is VC 2008 SP1), previously installed as permanent.  Even if I remove
VC 2008 SP1 the package fails with the same error 0x80004005 - Unspecified
Error

In WinDbg the failure happens at:
Wix37_source\src\burn\engine\core.cpp #1339 
::GetExitCodeThread(hCacheThread, (DWORD*)hr)
gets set to 0x80004005

Earlier a check for the cache path directory failed (as that GUID named dir
does not exist) but then I failed the figure out what it is trying to do
when it is failing.

As an experiment I rebuilt my bundle with all packages except the first one
commented out, and it still fails on that first package.  I suspect the fact
that it is marked as a 'permanent' package and the fact that I added bundle
signing is a factor in this issue.  The bundle is not installed when these
problems are happening.  Any thoughts on how I can get past this issue (or
narrow it down)?
Phill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-06 Thread Hoover, Jacob
Make sure you are signing your bundle using the provided targets.  If unsure, 
post what you are using.

-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com] 
Sent: Tuesday, August 06, 2013 4:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Burn 'Unspecified Error' after signing bundle

I have a bundle which has three EXE and 1 MSI, all third-party, and then my MSI 
for a total of five packages.  This is my first bundle and it has been 
installing on a Win 8 x64 test system successfully.  I install and uninstall on 
this test box, rather than going back to a clean OS as I have WinDbg and VS 
also installed so that I can step into the code.

I had figured out the MSI localization some time ago, but reset the VS culture 
parameter to english, and removed the post build steps to embed the mst files 
and sign the msi, to save time in doing test builds as I developed the bundle.  
Now I am happy with the bundle so I added those msi localization and signing 
steps back into the build process, and I added signing to the bundle for the 
first time.

Now the setup always fails while trying to process the first EXE package (which 
is VC 2008 SP1), previously installed as permanent.  Even if I remove VC 2008 
SP1 the package fails with the same error 0x80004005 - Unspecified Error

In WinDbg the failure happens at:
Wix37_source\src\burn\engine\core.cpp #1339 ::GetExitCodeThread(hCacheThread, 
(DWORD*)hr) gets set to 0x80004005

Earlier a check for the cache path directory failed (as that GUID named dir 
does not exist) but then I failed the figure out what it is trying to do when 
it is failing.

As an experiment I rebuilt my bundle with all packages except the first one 
commented out, and it still fails on that first package.  I suspect the fact 
that it is marked as a 'permanent' package and the fact that I added bundle 
signing is a factor in this issue.  The bundle is not installed when these 
problems are happening.  Any thoughts on how I can get past this issue (or 
narrow it down)?
Phill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Burn 'Unspecified Error' after signing bundle

2013-08-06 Thread Blair Murri
Realize that signing a bundle requires two signatures in a row. Make sure you 
are signing the right thing in each target.
 
 From: jacob.hoo...@greenheck.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 6 Aug 2013 21:37:45 +
 Subject: Re: [WiX-users] Burn 'Unspecified Error' after signing bundle
 
 Make sure you are signing your bundle using the provided targets.  If unsure, 
 post what you are using.
 
 -Original Message-
 From: Phill Hogland [mailto:phogl...@rimage.com] 
 Sent: Tuesday, August 06, 2013 4:29 PM
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Burn 'Unspecified Error' after signing bundle
 
 I have a bundle which has three EXE and 1 MSI, all third-party, and then my 
 MSI for a total of five packages.  This is my first bundle and it has been 
 installing on a Win 8 x64 test system successfully.  I install and uninstall 
 on this test box, rather than going back to a clean OS as I have WinDbg and 
 VS also installed so that I can step into the code.
 
 I had figured out the MSI localization some time ago, but reset the VS 
 culture parameter to english, and removed the post build steps to embed the 
 mst files and sign the msi, to save time in doing test builds as I developed 
 the bundle.  Now I am happy with the bundle so I added those msi localization 
 and signing steps back into the build process, and I added signing to the 
 bundle for the first time.
 
 Now the setup always fails while trying to process the first EXE package 
 (which is VC 2008 SP1), previously installed as permanent.  Even if I remove 
 VC 2008 SP1 the package fails with the same error 0x80004005 - Unspecified 
 Error
 
 In WinDbg the failure happens at:
 Wix37_source\src\burn\engine\core.cpp #1339 ::GetExitCodeThread(hCacheThread, 
 (DWORD*)hr) gets set to 0x80004005
 
 Earlier a check for the cache path directory failed (as that GUID named dir 
 does not exist) but then I failed the figure out what it is trying to do when 
 it is failing.
 
 As an experiment I rebuilt my bundle with all packages except the first one 
 commented out, and it still fails on that first package.  I suspect the fact 
 that it is marked as a 'permanent' package and the fact that I added bundle 
 signing is a factor in this issue.  The bundle is not installed when these 
 problems are happening.  Any thoughts on how I can get past this issue (or 
 narrow it down)?
 Phill
 
 
 
 --
 View this message in context: 
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845.html
 Sent from the wix-users mailing list archive at Nabble.com.
 
 --
 Get 100% visibility into Java/.NET code with AppDynamics Lite!
 It's a free troubleshooting tool designed for production.
 Get down to code-level detail for bottlenecks, with 2% overhead. 
 Download for free and get started troubleshooting in minutes. 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 Get 100% visibility into Java/.NET code with AppDynamics Lite!
 It's a free troubleshooting tool designed for production.
 Get down to code-level detail for bottlenecks, with 2% overhead. 
 Download for free and get started troubleshooting in minutes. 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users