Log produced by msiexec unreadable
Hello Guys,
I've been packaging things for quite a while now and I very rarely get log files that can't be read.
I was never able to reproduce it so I can't even give a hint about it.
Actually the log file is filled with squares that once copy/pasted become à ´Šà ´Šà ´Šà ´Šà ´Šà ´Šà ´Š
The only info I have is that msiexec is executed from a WiseScript EXE file.
Has anyone ever encountered this issue ?
Thank you
I've been packaging things for quite a while now and I very rarely get log files that can't be read.
I was never able to reproduce it so I can't even give a hint about it.
Actually the log file is filled with squares that once copy/pasted become à ´Šà ´Šà ´Šà ´Šà ´Šà ´Šà ´Š
The only info I have is that msiexec is executed from a WiseScript EXE file.
Has anyone ever encountered this issue ?
Thank you
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
pjgeutjens
14 years ago
I have once actually seen something similar. it happened when I tried to open an MSI log file in a vbs for adding things to it. The reason was that an MSI log by default is written in Unicode encoding, and my VBS wanted to add to it in ASCII.
Could you be experiencing something similar?
Could you be experiencing something similar?
Posted by:
dynek
14 years ago
We are using WiseScript to write things to the same log file MSIEXEC writes to.
It's not yet clear why and how it happens but this is a good start. Thank you very much for your input!
I'll check it and reply in this thread if I actually find something around this.
It's not yet clear why and how it happens but this is a good start. Thank you very much for your input!
I'll check it and reply in this thread if I actually find something around this.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.