Re: [WiX-users] Burn errors
What version of Burn are you using? Those sound like old errors that I think were fixed in more recent builds of Burn. The security ID issue could be a problem if they mucked up the permissions of %ProgramData% or certain parts of the registry. The full line from the log file would probably help. smile/ On Wed, May 23, 2012 at 3:01 PM, Kelly Graus kelly.gr...@toltech.netwrote: Hello all, I am seeing a couple different errors on a customers machine when running a burn based setup. The setup is about as simple as you can get - the bootstrapper just wraps a single MSI. Initially the customer was getting the following error: 0x800705ib - This security ID may not be assigned as the owner of this object. Then the customer changed something related to permissions (their computer is run by an IT group, and they wouldn't give us more details than that). After the change, he then received the following error: 0x800700e8 - The pipe is being closed. He passed along a screenshot of the log file (I have no idea why he couldn't send the actual log file, but anyway, see attached). Having him install the MSI file without the bootstrapper worked, although it's not something we want to do if we can help it. So my question is: Without any additional information, can anyone shed some light on the situation? I realize that I don't have much to go on (since this is a customers machine I don't have access to it, and we haven't been able to duplicate the problem on any of our machines). If it helps I can pass along any of the .wxs files. Thanks for any help! Kelly -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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 errors
Kelly I saw those same errors a while back which were caused by our AV (Symantec Endpoint Protection v12) heuristic detection blocking Burn from extracting stuff from itself when it was unsigned. We reported it to Symantec but other AV products may have similar issues. Have you tried signing your Bundle MSI? This fixed it for me before Symantec updated their heuristic detection engine to be a little less overzealous. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 24 May 2012 07:34 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn errors What version of Burn are you using? Those sound like old errors that I think were fixed in more recent builds of Burn. The security ID issue could be a problem if they mucked up the permissions of %ProgramData% or certain parts of the registry. The full line from the log file would probably help. smile/ On Wed, May 23, 2012 at 3:01 PM, Kelly Graus kelly.gr...@toltech.netwrote: Hello all, I am seeing a couple different errors on a customers machine when running a burn based setup. The setup is about as simple as you can get - the bootstrapper just wraps a single MSI. Initially the customer was getting the following error: 0x800705ib - This security ID may not be assigned as the owner of this object. Then the customer changed something related to permissions (their computer is run by an IT group, and they wouldn't give us more details than that). After the change, he then received the following error: 0x800700e8 - The pipe is being closed. He passed along a screenshot of the log file (I have no idea why he couldn't send the actual log file, but anyway, see attached). Having him install the MSI file without the bootstrapper worked, although it's not something we want to do if we can help it. So my question is: Without any additional information, can anyone shed some light on the situation? I realize that I don't have much to go on (since this is a customers machine I don't have access to it, and we haven't been able to duplicate the problem on any of our machines). If it helps I can pass along any of the .wxs files. Thanks for any help! Kelly -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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 errors
I'd recommend using the latest weekly build over RC0 - http://wixtoolset.org/releases If you're still getting those issues after updating I would try it with AV disabled to make sure it's not getting in the way. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Kelly Graus [mailto:kelly.gr...@toltech.net] Sent: 24 May 2012 18:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn errors Thanks for the replies! Rob: I'm using version 3.6.2221.0. I'll update to RC0 (the latest as far as I can tell) and see if we can get the customer to try again. Pally: We are signing the bundle, the bundle engine, and the MSI file. Hopefully that should take care of any problems with AV. Kelly On May 24, 2012, at 3:38 AM, Pally Sandher wrote: Kelly I saw those same errors a while back which were caused by our AV (Symantec Endpoint Protection v12) heuristic detection blocking Burn from extracting stuff from itself when it was unsigned. We reported it to Symantec but other AV products may have similar issues. Have you tried signing your Bundle MSI? This fixed it for me before Symantec updated their heuristic detection engine to be a little less overzealous. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 24 May 2012 07:34 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn errors What version of Burn are you using? Those sound like old errors that I think were fixed in more recent builds of Burn. The security ID issue could be a problem if they mucked up the permissions of %ProgramData% or certain parts of the registry. The full line from the log file would probably help. smile/ On Wed, May 23, 2012 at 3:01 PM, Kelly Graus kelly.gr...@toltech.netwrote: Hello all, I am seeing a couple different errors on a customers machine when running a burn based setup. The setup is about as simple as you can get - the bootstrapper just wraps a single MSI. Initially the customer was getting the following error: 0x800705ib - This security ID may not be assigned as the owner of this object. Then the customer changed something related to permissions (their computer is run by an IT group, and they wouldn't give us more details than that). After the change, he then received the following error: 0x800700e8 - The pipe is being closed. He passed along a screenshot of the log file (I have no idea why he couldn't send the actual log file, but anyway, see attached). Having him install the MSI file without the bootstrapper worked, although it's not something we want to do if we can help it. So my question is: Without any additional information, can anyone shed some light on the situation? I realize that I don't have much to go on (since this is a customers machine I don't have access to it, and we haven't been able to duplicate the problem on any of our machines). If it helps I can pass along any of the .wxs files. Thanks for any help! Kelly -- 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 -- virtually, Rob Mensching - http://RobMensching.com LLC -- 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 errors
Hello all, I am seeing a couple different errors on a customers machine when running a burn based setup. The setup is about as simple as you can get - the bootstrapper just wraps a single MSI. Initially the customer was getting the following error: 0x800705ib - This security ID may not be assigned as the owner of this object. Then the customer changed something related to permissions (their computer is run by an IT group, and they wouldn't give us more details than that). After the change, he then received the following error: 0x800700e8 - The pipe is being closed. He passed along a screenshot of the log file (I have no idea why he couldn't send the actual log file, but anyway, see attached). Having him install the MSI file without the bootstrapper worked, although it's not something we want to do if we can help it. So my question is: Without any additional information, can anyone shed some light on the situation? I realize that I don't have much to go on (since this is a customers machine I don't have access to it, and we haven't been able to duplicate the problem on any of our machines). If it helps I can pass along any of the .wxs files. Thanks for any help! Kelly -- 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
