Re: [WiX-users] Error 2343
Which options did you pass to msiexec when debugging the msi with regards to logging? I use /l*vx as this logs absolutely everything. Sometimes it's a bit overkill but I find the more information I can get out of Windows Installer when debugging, the better. 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 ** 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: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 16 May 2012 05:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 Hi Rob, I don't believe you'd be able to catch this, based on my very limited understanding of WIX and the installer services. Since the directory path in question was supposed to be dynamically set, there would be no way to be sure at compile time that the directory will exist (or that the path var exists/is valid). And since the Windows Installer doesn't give any information about what was missing from where, the only way we could know what went wrong is if we had logged what we were trying to do just before we attempted to do it. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, 16 May 2012 13:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 What exactly needed to be caught? If we can catch it in the WiX toolset we should. On Tue, May 15, 2012 at 7:09 PM, Aaron Oxford < aaron.oxf...@objecttrading.com> wrote: > Regarding trying to find the cause of an Error 2343 - Specified path > is empty. > > The only way I discovered to deal with this problem was through a > process of elimination. Even having now found the exact location of > the problem I can see that there would have been nothing in any of the > logs that could have led me there any faster. > > It turned out that I was setting a flag incorrectly which caused this > to manifest somewhere within the thousands of lines of third-party > wixlib on which my project is built. (An extension directory was > unnecessarily declared, which would require me to show a custom > browser dialog in order to set its location. Having not done that, the > wixlib attempted to use an undefined directory, resulting in the > error.) > > The only thing that could have helped me here is if the MSI had logged > what it was trying to do before running into the error. I don't know > if that's even possible within the Windows Installer framework, but if > WIX could do this it would be incredibly helpful. > > Thanks for listening everyone. > > Aaron Oxford - Developer > E aaron.oxf...@objecttrading.com > T +61 2 9450 2999 > F +61 2 9245 2744 > W www.objecttrading.com > This message may contain privileged and confidential information > intended only for the use of the addressee(s) named above. If you are > not the intended recipient of this message you are hereby notified > that any use, dissemination, distribution or reproduction of this > message is prohibited. If you have received this message in error > please notify the sender immediately. > > > > > -Original Message- > From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] > Sent: Wednesday, 16 May 2012 09:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Error 2343 > > Hi Pally and thanks for the reply, > > I believe you've missed the point, and subject, of my post: Error 2343 > - Specified path is empty. I used the ICE error as an example of > getting too much information, as opposed to the Error 2343 which > couldn't really be less helpful, even with verbose logging. > > The other error actually came up as I was _troubleshooting_ Error 2343 > and attempting to remove all file deployment in entirety, so that I > could slowly eliminate possible causes of Error 2343. It is the Error > 2343 - Specified path is empty - that I am trying to solve. I need to > find out what path is empty. There are many, many paths, and none of
Re: [WiX-users] Error 2343
Hi Rob, I don't believe you'd be able to catch this, based on my very limited understanding of WIX and the installer services. Since the directory path in question was supposed to be dynamically set, there would be no way to be sure at compile time that the directory will exist (or that the path var exists/is valid). And since the Windows Installer doesn't give any information about what was missing from where, the only way we could know what went wrong is if we had logged what we were trying to do just before we attempted to do it. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, 16 May 2012 13:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 What exactly needed to be caught? If we can catch it in the WiX toolset we should. On Tue, May 15, 2012 at 7:09 PM, Aaron Oxford < aaron.oxf...@objecttrading.com> wrote: > Regarding trying to find the cause of an Error 2343 - Specified path > is empty. > > The only way I discovered to deal with this problem was through a > process of elimination. Even having now found the exact location of > the problem I can see that there would have been nothing in any of the > logs that could have led me there any faster. > > It turned out that I was setting a flag incorrectly which caused this > to manifest somewhere within the thousands of lines of third-party > wixlib on which my project is built. (An extension directory was > unnecessarily declared, which would require me to show a custom > browser dialog in order to set its location. Having not done that, the > wixlib attempted to use an undefined directory, resulting in the > error.) > > The only thing that could have helped me here is if the MSI had logged > what it was trying to do before running into the error. I don't know > if that's even possible within the Windows Installer framework, but if > WIX could do this it would be incredibly helpful. > > Thanks for listening everyone. > > Aaron Oxford - Developer > E aaron.oxf...@objecttrading.com > T +61 2 9450 2999 > F +61 2 9245 2744 > W www.objecttrading.com > This message may contain privileged and confidential information > intended only for the use of the addressee(s) named above. If you are > not the intended recipient of this message you are hereby notified > that any use, dissemination, distribution or reproduction of this > message is prohibited. If you have received this message in error > please notify the sender immediately. > > > > > -Original Message- > From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] > Sent: Wednesday, 16 May 2012 09:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Error 2343 > > Hi Pally and thanks for the reply, > > I believe you've missed the point, and subject, of my post: Error 2343 > - Specified path is empty. I used the ICE error as an example of > getting too much information, as opposed to the Error 2343 which > couldn't really be less helpful, even with verbose logging. > > The other error actually came up as I was _troubleshooting_ Error 2343 > and attempting to remove all file deployment in entirety, so that I > could slowly eliminate possible causes of Error 2343. It is the Error > 2343 - Specified path is empty - that I am trying to solve. I need to > find out what path is empty. There are many, many paths, and none of > them are listed as empty when I do a verbose log of Error 2343. > > By the way, it seems I need to explicitly state that I've looked up > Error code 2343 using Google. You can read up on Error 2343 here > http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. > 85%29.aspx before replying if you like. That way you won't be sharing > any information that's already available to me, just the new > information specific to this case that results from analysing the > question (about Error 2343) using your skill and experience. ;-) > > Perhaps it was the tone of my post about Error 2343 that led you > chastise me for not looking up "2343 - Specified path is empty" > myself, but I don't think my browser and search engine are goin
Re: [WiX-users] Error 2343
What exactly needed to be caught? If we can catch it in the WiX toolset we should. On Tue, May 15, 2012 at 7:09 PM, Aaron Oxford < aaron.oxf...@objecttrading.com> wrote: > Regarding trying to find the cause of an Error 2343 - Specified path is > empty. > > The only way I discovered to deal with this problem was through a > process of elimination. Even having now found the exact location of the > problem I can see that there would have been nothing in any of the logs > that could have led me there any faster. > > It turned out that I was setting a flag incorrectly which caused this to > manifest somewhere within the thousands of lines of third-party wixlib > on which my project is built. (An extension directory was unnecessarily > declared, which would require me to show a custom browser dialog in > order to set its location. Having not done that, the wixlib attempted to > use an undefined directory, resulting in the error.) > > The only thing that could have helped me here is if the MSI had logged > what it was trying to do before running into the error. I don't know if > that's even possible within the Windows Installer framework, but if WIX > could do this it would be incredibly helpful. > > Thanks for listening everyone. > > Aaron Oxford - Developer > E aaron.oxf...@objecttrading.com > T +61 2 9450 2999 > F +61 2 9245 2744 > W www.objecttrading.com > This message may contain privileged and confidential information > intended only for the use of the addressee(s) named above. If you are > not the intended recipient of this message you are hereby notified that > any use, dissemination, distribution or reproduction of this message is > prohibited. If you have received this message in error please notify the > sender immediately. > > > > > -Original Message- > From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] > Sent: Wednesday, 16 May 2012 09:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Error 2343 > > Hi Pally and thanks for the reply, > > I believe you've missed the point, and subject, of my post: Error 2343 - > Specified path is empty. I used the ICE error as an example of getting > too much information, as opposed to the Error 2343 which couldn't really > be less helpful, even with verbose logging. > > The other error actually came up as I was _troubleshooting_ Error 2343 > and attempting to remove all file deployment in entirety, so that I > could slowly eliminate possible causes of Error 2343. It is the Error > 2343 - Specified path is empty - that I am trying to solve. I need to > find out what path is empty. There are many, many paths, and none of > them are listed as empty when I do a verbose log of Error 2343. > > By the way, it seems I need to explicitly state that I've looked up > Error code 2343 using Google. You can read up on Error 2343 here > http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. > 85%29.aspx before replying if you like. That way you won't be sharing > any information that's already available to me, just the new information > specific to this case that results from analysing the question (about > Error 2343) using your skill and experience. ;-) > > Perhaps it was the tone of my post about Error 2343 that led you > chastise me for not looking up "2343 - Specified path is empty" myself, > but I don't think my browser and search engine are going to help me > extract information from Error 2343 that simply isn't there. What I need > to know is what the MSI is actually trying to do when this error occurs. > > > That is why I posted here asking if there is any other way to get > information out of the MSI about Error 2343 as it tries to 'get > installed' by the Windows Installer. ;-) > > > After even more reading, I also now understand that the lack of > information in Error 2343 probably isn't WIX's fault, even if the flawed > MSI is. This looks like standard Microsoft behaviour (in the Windows > Installer code), where you go to the trouble of allocating unique error > codes, like "2343", but never consider making the messages useful, like > "Specified path is empty". Looks like that one fell straight through the > code review; they couldn't even be bothered making it (the error message > for Error 2343) a sentence. > > In addition to that, unlike every other person with this problem on > every forum and code sharing site I could Google, I'm not playing with a > folder browser dialog when I get my Error 2343. I'm working on top of a > large pre-existing library (that I have tested separately as working) &g
Re: [WiX-users] Error 2343
Regarding trying to find the cause of an Error 2343 - Specified path is empty. The only way I discovered to deal with this problem was through a process of elimination. Even having now found the exact location of the problem I can see that there would have been nothing in any of the logs that could have led me there any faster. It turned out that I was setting a flag incorrectly which caused this to manifest somewhere within the thousands of lines of third-party wixlib on which my project is built. (An extension directory was unnecessarily declared, which would require me to show a custom browser dialog in order to set its location. Having not done that, the wixlib attempted to use an undefined directory, resulting in the error.) The only thing that could have helped me here is if the MSI had logged what it was trying to do before running into the error. I don't know if that's even possible within the Windows Installer framework, but if WIX could do this it would be incredibly helpful. Thanks for listening everyone. Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: Wednesday, 16 May 2012 09:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up "2343 - Specified path is empty" myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even more reading, I also now understand that the lack of information in Error 2343 probably isn't WIX's fault, even if the flawed MSI is. This looks like standard Microsoft behaviour (in the Windows Installer code), where you go to the trouble of allocating unique error codes, like "2343", but never consider making the messages useful, like "Specified path is empty". Looks like that one fell straight through the code review; they couldn't even be bothered making it (the error message for Error 2343) a sentence. In addition to that, unlike every other person with this problem on every forum and code sharing site I could Google, I'm not playing with a folder browser dialog when I get my Error 2343. I'm working on top of a large pre-existing library (that I have tested separately as working) and simply deploying a few files that are specific to my project, so I suspect that my "2343 - Specified path is empty" is not related to the root installer directory but one of the subdirectories I'm attempting to create. But, I'd have to know WHAT PATH IS EMPTY (Error 2343) to confirm that. :-D Not to worry, I've had to roll back a bunch of changes to a version of the scripts that work OK and don't crash with Error 2343. You live you learn I guess - after all, all the changes compiled (no Error 2343), and how could WIX create an MSI that doesn't install correctly if
Re: [WiX-users] Error 2343
Hi Pally and thanks for the reply, I believe you've missed the point, and subject, of my post: Error 2343 - Specified path is empty. I used the ICE error as an example of getting too much information, as opposed to the Error 2343 which couldn't really be less helpful, even with verbose logging. The other error actually came up as I was _troubleshooting_ Error 2343 and attempting to remove all file deployment in entirety, so that I could slowly eliminate possible causes of Error 2343. It is the Error 2343 - Specified path is empty - that I am trying to solve. I need to find out what path is empty. There are many, many paths, and none of them are listed as empty when I do a verbose log of Error 2343. By the way, it seems I need to explicitly state that I've looked up Error code 2343 using Google. You can read up on Error 2343 here http://msdn.microsoft.com/en-us/library/windows/desktop/aa372835%28v=vs. 85%29.aspx before replying if you like. That way you won't be sharing any information that's already available to me, just the new information specific to this case that results from analysing the question (about Error 2343) using your skill and experience. ;-) Perhaps it was the tone of my post about Error 2343 that led you chastise me for not looking up "2343 - Specified path is empty" myself, but I don't think my browser and search engine are going to help me extract information from Error 2343 that simply isn't there. What I need to know is what the MSI is actually trying to do when this error occurs. That is why I posted here asking if there is any other way to get information out of the MSI about Error 2343 as it tries to 'get installed' by the Windows Installer. ;-) After even more reading, I also now understand that the lack of information in Error 2343 probably isn't WIX's fault, even if the flawed MSI is. This looks like standard Microsoft behaviour (in the Windows Installer code), where you go to the trouble of allocating unique error codes, like "2343", but never consider making the messages useful, like "Specified path is empty". Looks like that one fell straight through the code review; they couldn't even be bothered making it (the error message for Error 2343) a sentence. In addition to that, unlike every other person with this problem on every forum and code sharing site I could Google, I'm not playing with a folder browser dialog when I get my Error 2343. I'm working on top of a large pre-existing library (that I have tested separately as working) and simply deploying a few files that are specific to my project, so I suspect that my "2343 - Specified path is empty" is not related to the root installer directory but one of the subdirectories I'm attempting to create. But, I'd have to know WHAT PATH IS EMPTY (Error 2343) to confirm that. :-D Not to worry, I've had to roll back a bunch of changes to a version of the scripts that work OK and don't crash with Error 2343. You live you learn I guess - after all, all the changes compiled (no Error 2343), and how could WIX create an MSI that doesn't install correctly if it compiles without warnings? Hahahaha [cry]. When I work out what caused my Error "2343 - Specified path is empty" I'll post back here with my fix in the hopes of maybe helping someone out. ;-) Error 2343 Aaron Oxford - Developer E aaron.oxf...@objecttrading.com T +61 2 9450 2999 F +61 2 9245 2744 W www.objecttrading.com This message may contain privileged and confidential information intended only for the use of the addressee(s) named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Tuesday, 15 May 2012 21:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Error 2343 ICE errors aren't WiX errors. Here's your hint as requested -> http://msdn.microsoft.com/en-us/library/windows/desktop/aa369206.aspx or if that's not enough how about http://msdn.microsoft.com/en-us/library/windows/desktop/aa369022.aspx I think what you may be missing is basic troubleshooting and a web browser with a search engine. 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 ** 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: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourc
Re: [WiX-users] Error 2343
Hi Aaron, If you get an error about no Media table, perhaps you are missing a line such as: in your product.wxs file. I haven't taken the time to verify what errors you get if this line is missing, since I've always included it, but that's a quick stab at it. I generally find the WiX errors (or ICE errors) give me enough information to figure out what's going on. If you give more details, such as the actual build output and excerpts from your product.wxs then I suspect you will get more help. This group is quite active. Sincerely, Daniel Madill -Original Message- From: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2343 Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my paths and they look fine, and it would really help to be able to narrow down WHAT file/directory is missing! WIX pops out with the most astonishing errors sometimes, e.g. "LGHT1076: ICE71: The Media table has no entries.", and yet for something simple like when a file was not built into the installer, we proceed to build the MSI and then get no idea whatsoever what file that might have been. So we get a fatal failure for something nobody gives a crap about but we can build an entire installer without actually putting the required files into it? This can't be right, I must be missing something. Can anyone give me hint? :-) Thanks, Aaron Oxford Object Trading Pty Ltd -- 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] Error 2343
ICE errors aren't WiX errors. Here's your hint as requested -> http://msdn.microsoft.com/en-us/library/windows/desktop/aa369206.aspx or if that's not enough how about http://msdn.microsoft.com/en-us/library/windows/desktop/aa369022.aspx I think what you may be missing is basic troubleshooting and a web browser with a search engine. 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 ** 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: Aaron Oxford [mailto:aaron.oxf...@objecttrading.com] Sent: 15 May 2012 05:26 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2343 Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my paths and they look fine, and it would really help to be able to narrow down WHAT file/directory is missing! WIX pops out with the most astonishing errors sometimes, e.g. "LGHT1076: ICE71: The Media table has no entries.", and yet for something simple like when a file was not built into the installer, we proceed to build the MSI and then get no idea whatsoever what file that might have been. So we get a fatal failure for something nobody gives a crap about but we can build an entire installer without actually putting the required files into it? This can't be right, I must be missing something. Can anyone give me hint? :-) Thanks, Aaron Oxford Object Trading Pty Ltd -- 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
[WiX-users] Error 2343
Hi WIX people, Is there any way to get more information when a path is supposedly empty? I've looked at all my paths and they look fine, and it would really help to be able to narrow down WHAT file/directory is missing! WIX pops out with the most astonishing errors sometimes, e.g. "LGHT1076: ICE71: The Media table has no entries.", and yet for something simple like when a file was not built into the installer, we proceed to build the MSI and then get no idea whatsoever what file that might have been. So we get a fatal failure for something nobody gives a crap about but we can build an entire installer without actually putting the required files into it? This can't be right, I must be missing something. Can anyone give me hint? :-) Thanks, Aaron Oxford Object Trading Pty Ltd -- 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] error 2343
Does the log file say "The parameters are..." and list a couple of parameters after error code 2343? If so these parameters could give you more information. You can also go to Control Panel -> Administrative Tools -> Event Viewer and click on Application in the left pane, and see if you can find the error there. It usually gives you the same info but can have additional details. Also check out the comments at the AppDeploy page: http://www.appdeploy.com/msierrors/detail.asp?id=134 If you get more error codes in the future you can search for it at http://www.appdeploy.com/msierrors/. Craig0ss wrote: > > > yep i got pretty much got that from the log file, however im not sure what > path its refering to, and im not sure what to do to fix it > > thanks > > > Rob Hamflett wrote: >> >> The error message for 2343 is 'Specified path is empty'. >> >> Rob >> >> Craig0ss wrote: >>> Hi >>> >>> If i put an edit box onto one of my dialogs, and then run the compiles >>> msi, >>> when i click the relavent button to take me to the dialog where the >>> edit/pathedit is the msi crashes with the error code 2343 >>> >>> Any ideas >>> >>> thanks >> >> >> - >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > > -- View this message in context: http://www.nabble.com/error-2343-tf4677831.html#a13369470 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error 2343
Presumably you need to pre-populate the path control with an actual path. Rob Craig0ss wrote: > > yep i got pretty much got that from the log file, however im not sure what > path its refering to, and im not sure what to do to fix it > > thanks > > > Rob Hamflett wrote: >> The error message for 2343 is 'Specified path is empty'. >> >> Rob >> >> Craig0ss wrote: >>> Hi >>> >>> If i put an edit box onto one of my dialogs, and then run the compiles >>> msi, >>> when i click the relavent button to take me to the dialog where the >>> edit/pathedit is the msi crashes with the error code 2343 >>> >>> Any ideas >>> >>> thanks >> >> - >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error 2343
yep i got pretty much got that from the log file, however im not sure what path its refering to, and im not sure what to do to fix it thanks Rob Hamflett wrote: > > The error message for 2343 is 'Specified path is empty'. > > Rob > > Craig0ss wrote: >> Hi >> >> If i put an edit box onto one of my dialogs, and then run the compiles >> msi, >> when i click the relavent button to take me to the dialog where the >> edit/pathedit is the msi crashes with the error code 2343 >> >> Any ideas >> >> thanks > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/error-2343-tf4677831.html#a13366228 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error 2343
The error message for 2343 is 'Specified path is empty'. Rob Craig0ss wrote: > Hi > > If i put an edit box onto one of my dialogs, and then run the compiles msi, > when i click the relavent button to take me to the dialog where the > edit/pathedit is the msi crashes with the error code 2343 > > Any ideas > > thanks - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] error 2343
Hi If i put an edit box onto one of my dialogs, and then run the compiles msi, when i click the relavent button to take me to the dialog where the edit/pathedit is the msi crashes with the error code 2343 Any ideas thanks -- View this message in context: http://www.nabble.com/error-2343-tf4677831.html#a13365454 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
Peter Bocej wrote: I don`t understand "Indirect" attribute. Now I thing that "Indirect" means: Correct. It lets you build a browse dialog (for example) that can browse any number of directories. Wix manual tells nothing about "Indirect" and my english is ugly :( Take a look at the MSI doc in the Platform SDK or Windows SDK (for Vista). -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
Thanx, it works! I don`t understand "Indirect" attribute. Now I thing that "Indirect" means: If I use: ... ... in the PathEdit control I need because the value of INSTALLDIR property is correct path string If I use: ... ... ... in the PathEdit control I need because the value of InstallDirProperty property is the name of property witch value has correct path string Wix manual tells nothing about "Indirect" and my english is ugly :( Peter Bocej Emtest a.s. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 5:37 PM To: Peter Bocej Cc: Wix-Users Subject: Re: [WiX-users] Error 2343 - Specified path is empty Peter Bocej wrote: > When the InstallDirDlg starts, INSTALLDIR property has value "C:\Program > Files\BaseUI\" > I don`t know how I could set initial value of the PathEdit control. > You can tie a PathEdit to a directory property, just don't use Indirect="yes" unless it's an indirect property. -- sig://boB http://bobs.org __ Informacia od NOD32 1.1810 (20061018) __ Tato sprava bola preverena antivirusovym systemom NOD32. http://www.eset.sk - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
Peter Bocej wrote: > When the InstallDirDlg starts, INSTALLDIR property has value "C:\Program > Files\BaseUI\" > I don`t know how I could set initial value of the PathEdit control. > You can tie a PathEdit to a directory property, just don't use Indirect="yes" unless it's an indirect property. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
My INSTALLDIR property is defined: When the InstallDirDlg starts, INSTALLDIR property has value "C:\Program Files\BaseUI\" I don`t know how I could set initial value of the PathEdit control. Peter Bocej Emtest a.s. -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 5:23 PM To: Peter Bocej Cc: Wix-Users Subject: Re: [WiX-users] Error 2343 - Specified path is empty Peter Bocej wrote: > Yes, INSTALLDIR property is set under the CostFinalize action: > MSI (c) (1C:B8) [10:04:42:715]: PROPERTY CHANGE: Adding INSTALLDIR property. > Its value is 'C:\Program Files\BaseUI\'. > When you use Indirect="yes" you're telling the PathEdit control that the property is the name of another property. Just omit it if the property is the actual directory path. -- sig://boB http://bobs.org __ Informacia od NOD32 1.1808 (20061017) __ Tato sprava bola preverena antivirusovym systemom NOD32. http://www.eset.sk - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
Peter Bocej wrote: > Yes, INSTALLDIR property is set under the CostFinalize action: > MSI (c) (1C:B8) [10:04:42:715]: PROPERTY CHANGE: Adding INSTALLDIR property. > Its value is 'C:\Program Files\BaseUI\'. > When you use Indirect="yes" you're telling the PathEdit control that the property is the name of another property. Just omit it if the property is the actual directory path. -- sig://boB http://bobs.org - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
Yes, INSTALLDIR property is set under the CostFinalize action: MSI (c) (1C:B8) [10:04:42:715]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'C:\Program Files\BaseUI\'. If I change the PathEdit control to Text: [INSTALLDIR] it shows correct path. Peter Bocej Emtest a.s. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rob Hamflett Sent: Tuesday, October 17, 2006 9:51 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Error 2343 - Specified path is empty If you log the install, what's the last reported value for INSTALLDIR before you get to this dialog? Quick sanity check; INSTALLDIR is the ID for one of your directories, right? Rob Peter Bocej wrote: > Hi all, > > I can assign initial install dir to PathEdit control`s initial value, > ... > Height="18" Property="INSTALLDIR" Indirect="yes" /> > ... > and in instalation process i get an error 2343 (Specified path is empty). > Could somebody explain me how the PathEdit control works? > > Thanx > > Full basic Wix xml attached. > > Peter Bocej > Emtest a.s. > > > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Informacia od NOD32 1.1806 (20061017) __ Tato sprava bola preverena antivirusovym systemom NOD32. http://www.eset.sk - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2343 - Specified path is empty
If you log the install, what's the last reported value for INSTALLDIR before you get to this dialog? Quick sanity check; INSTALLDIR is the ID for one of your directories, right? Rob Peter Bocej wrote: > Hi all, > > I can assign initial install dir to PathEdit control`s initial value, > ... > Height="18" Property="INSTALLDIR" Indirect="yes" /> > ... > and in instalation process i get an error 2343 (Specified path is empty). > Could somebody explain me how the PathEdit control works? > > Thanx > > Full basic Wix xml attached. > > Peter Bocej > Emtest a.s. > > > > > - > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error 2343 - Specified path is empty
Hi all, I can assign initial install dir to PathEdit control`s initial value, ... ... and in instalation process i get an error 2343 (Specified path is empty). Could somebody explain me how the PathEdit control works? Thanx Full basic Wix xml attached. Peter Bocej Emtest a.s. baseui.wix Description: Binary data - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
