[wix-users] how to debug/locate LGHT0001 error?
Douglas, Keith (STATCAN/STATCAN)
keith.douglas at canada.ca
Tue Dec 1 13:38:27 PST 2015
On the first point:
Candle at least produces errors with line numbers. For example, the below says that the error took place in the file (C:\InstallerBuilder\ICOS\EQ\Wxs\aaaaaaaaaaaa-20151201161227.wxs) indicated at line 69.
C:\InstallerBuilder\ICOS\EQ\Wxs\aaaaaaaaaaaa-20151201161227.wxs(69) : error CNDL0123 : The Iis:WebAppPool/@MaxWorkerProcesses attribute's value, '500000', is not in the range of legal values. Legal values for this attribute are from 0 to 32767.
On the third:
Running your packages in verbose mode (/l*v) is very helpful, but learning to read the resulting logs is a challenge for sure - one I am still learning myself.
Programmer Analyst | Programmeur analyste
Questionnaire Development Services - CAI Social | Services de développement de questionnaires - IAO Social
Jean Talon Building | Immeuble Jean-Talon / Floor | Étage 4 A-3
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
Keith.Douglas at canada.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Ian Bell
Sent: December-01-15 4:10 PM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] how to debug/locate LGHT0001 error?
I am learning how to use WIX to create installation packages and have been
testing various options and configurations. In one particular test I
created a '.WXI' file for the purpose of defining variables in one spot that
would subsequently be included in the other .WXS fragment files. By
chance I defined a string variable and mistakenly added one to many quote
characters to the string. Attempting to build the WIX project generated
the error, "error LGHT0001: Illegal characters in path". No other details
were provided that identified where the error occurred. In this particular
case I was able to quickly identify the error source because I built the
project immediately after adding one to many quote characters. Had I not
immediately built the project but instead added additional information/data
to my WIX project files then it would not have been clear to me what caused
this particular error. A Google search of this error message returns only a
few hits, none of which offer any practical information. My questions are
1) Is it possible to configure the WIX build process in VS2015 to
provide more detailed debugging information such as the WXS/WXI filename and
line number where the error occurred? If so where/how do I configure the
2) If more detailed information regarding a build/link cannot be
generated then what are the recommended steps (i.e. best practices) for
debugging such an obscure error message?
3) Are there any documents or guidelines that offer suggestions on how
to debug/test WIX projects that fail at different times in the build/install
cycle? The reason I as is as follows. I have been building a variety of
WIX projects for testing purposes and have encountered several problems I
was unable to resolve. For example, in one case attempting to uninstall
the product failed to remove a few files and registry entries and I had to
manually delete them by hand. I believe this particular problem occurred
because I had incorrectly defined/configured my WIX project files.
Unfortunately, I could not make heads or tails out of the log file and, in
the end, my workaround solution was simply to rebuild the WIX projects from
scratch and then to rebuild/test after every change I made to it. As I
have just started learning WIX, having a set of debug/test
guidelines/suggestions would be extremely useful at this point.
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users