This ticket is not about the reason for the message.
Several times recently on Windows 7 I have seen a window appear with a title of "Errors occurred" containing and "OK" button and the text
See the logfile 'C:\Program Files (x86)\TaskCoach\TaskCoach.exe.log' for
details
The specified file doesn't exist. Either the file isn't being created, or it is being created in a different location. In either case the message is incorrect.
(I know it is standard, but the "OK" button really bugs me. It's not okay with me that errors occurred, and I don't want to agree that the file exists since it doesn't. At least the window has an "X" so I don't have to click "OK" when I don't feel okay. Couldn't you make it a "Sorry" button?)
Unfortunately this message is not part of Task Coach per se, it's a py2exe mechanism... We have our own implementation for OS X but it's not as complete...
The location the window mentions is correct. But when using e.g. Windows 7 SP1 x64, Taskcoach runs with User access rights, which means it has no write access to the Directory "C:\Program Files (x86)\TaskCoach".
There are possible solutions for this:
Run TaskCoach With Admin Rights.
Write the log file to a location where an Application with User rights is allowed to write.
I would say option 2.1 makes the most sense as that directory is already being used by TaskCoach.
Unfortunately this particular log is not written by Task Coach itself, it's a py2exe mechanism...
Would it be possible to circumvent that by running Taskcoach with the UserData dir as the working dir?
Either chdir`ing to that directory during runtime, or just setting it to be the working dir in the Desktop/Start Menu shortcut.
That warrants a try. I thought py2exe used the path to the executable but now I'm not so sure.
Nah, it uses the executable path. But according to http://www.py2exe.org/index.cgi/StderrLog it just redirects stdout and stderr at the Python level so we won't loose anything if we enable our own handling on Windows (like we do on Mac and Linux). I'll try that.
A fix was made and checked into the source code repository of Task Coach. The fix will be part of the next release. You will get another notification when that release is available with the request to install the new release and confirm that your issue has indeed been fixed.
If you like, you can download a recent build from http://www.fraca7.net/TaskCoach-packages/latest_bugfixes.py to test the fix.
Because a fix has been made for this bug report, the priority of this report has been lowered to 1 and its resolution has been set to 'Fixed'.
Thanks, Task Coach development team
Downloaded TaskCoach-1.3.29.6220-win32.exe
It is getting a (false positive) warning by Norton: http://www.symantec.com/security_response/writeup.jsp?docid=2010-051308-1854-99
I can still use that build by ignoring the file, just wanted to let you know.
Thanks. I guess any newly built binary gets a false positive with this system...
Ok, tested the new build 1.3.29.6220, on Exception a log file "taskcoachlog.txt" is saved under "My Documents".
Last edit: Florian George 2013-06-18
This bug should be fixed in the latest release of Task Coach. Can you please install the latest release of Task Coach and confirm that this bug has indeed been fixed?
Thanks, Task Coach development team
Unfortunately I received another error message and I am able to verify the log file is created in the my home directory.
(I will investigate the message in the log file and file another report on that issue if appropriate.)
Sorry, I can't test this. I can't crash TaskCoach because you've fixed
all the bugs I've found (and more).
Thanks for providing, and supporting, a useful tool.
--
B.J. Herbison / bj@herbison.com / http://www.herbison.com/herbison/bj.html
The Next Asylum / 203 Long Hill Road / Bolton, MA 01740-1421 / +1 978
634-1061
On 07/07/2013 11:47 AM, "Jérome Laheurte" wrote:
Let's close this then :)