![]() |
#1
|
|||
|
|||
Corrupt Log File
Hi,
I have project level logging enabled, and the xml log file is being corrupted with the attached .bld file. Any help would be appreciated. Thanks, Greg |
#2
|
|||
|
|||
#3
|
|||
|
|||
Thank you for the links. I had previously read these links and found my problem to be most related to thread 314, in which the xml file does not get written to until a subsequent logging call. The developer was trying to use a macro that has not yet been expanded. In this case the recommendation is to create the macro in script on startup.
I don't believe this is my problem, but I do see the same error message, and I am not trying to use a project level macro that needs expansion. Certainly something is corrupting the log file, but I can't determine what this is. The previous post contains the .bld file for examination. |
#4
|
|||
|
|||
I did look at your log file, and the same issue seems to apply. The project LOGFILE macro references %WORK_ROOT%, which is not defined at the project level, and the global macro WORK_ROOT gets created by the 'Prepare LocalHost Work Root' step during the build. The WORK_ROOT macro cannot change during the build when using XML logging, or part of log file will get written in one place and the rest somewhere else, resulting in two incomplete XML documents.
|
![]() |
|
|