Rank: Advanced Member
Joined: 6/24/2011(UTC)
Posts: 147
Location: New York, NY
|
On two occasions over the last month or so, when I have gone to review my time, I have noticed that Manictime has been completely off for several days (tracker and client). I couldn't chalk it up to anything the fist time, but wrote it off as "user error". Perhaps I was trying to reconfigure it, and forgot to turn it back on.
This latest time, though, it was mid-week, but sometime after the work day was over.
I see no errors in the event viewer over that time that are related to Manictime, and the only logging that manictime itself registers are these:
ManicTime.log:
10/07/2013 15:14:31.672 1 3908 18 Clearing process cache
12/07/2013 13:30:13.137 2 15828 1 ManicTime 2.4.0.3 started.
ManicTimeClient.log:
10/07/2013 16:16:27.639 2 4488 47 Disconnected from tracker.
12/07/2013 13:30:38.167 2 15448 1 ManicTimeClient 2.4.0.3 started.
The client event at 16:16 is about :30 after the last thing I see registered on any timeline until I restart. The only application exception that I recall seeing that I didn't recognize was for something called SSDC (or some such thing). I don't know if that was over the same period.
This is new behavior for ManicTime, for me. It's installed on a new workstation, at a new company, so I'm not sure what interactions there might be. Is there any way to monitor things more closely to determine what might be happening?
|
|
|
|
|
|
Rank: Administration
Joined: 4/13/2010(UTC)
Posts: 872
|
I'd start with the dump files.
Download this file
cdn.manictime.com/setup/custom/ManicTime_debug_tools.zip
Then run
ManicTime_debug_tools\registry_settings_for_crash_dumps\EnableLocalDumps.reg
This will save crash data form the apps, the one windows usually sends to Microsoft to your local drive. Dumps will be in
c:\Users\username\AppData\Local\CrashDumps\
When it crashes please send me the dump file.
Once we are done you can also run the DisableLocalDumps.reg to stop writing crash data to disk.
|
|
|
|
|
|
Rank: Administration
Joined: 4/13/2010(UTC)
Posts: 872
|
You can also use ManicTime Process Monitor, which monitors Tracker and restarts it if it crashes.
To enable it, you need to change the settings file in the database folder: c:\Users\username\AppData\Local\Finkit\ManicTime\ManicTime.xml.
Look for line with ProcessMonitorEnabled and change the value from false to true.
Then restart ManicTime.
|
|
|
|
|
|
Rank: Advanced Member
Joined: 6/24/2011(UTC)
Posts: 147
Location: New York, NY
|
I enabled the dumps when it was first suggested, and have had a few isolated crashes, since, but it never produces any output that I can find.
|
|
|
|
|
|
Rank: Administration
Joined: 4/13/2010(UTC)
Posts: 872
|
Usually the dump is recorded if you get a "send crash report to Microsoft" window. It sends the dump file, then it deletes it. The registry setting makes sure that it is not deleted.
Which windows are you using?
|
|
|
|
|
|
Rank: Advanced Member
Joined: 6/24/2011(UTC)
Posts: 147
Location: New York, NY
|
I have not been prompted to send a crash report. The program just goes away.
Sometimes the ManicTimeProcessMonitor.exe itself generates a JIT exception, prompting to bring up VisualStudio. In fact, as I look, that itself is not running now.
I use Windows XP, SP3
|
|
|
|
|
|
Rank: Administration
Joined: 4/13/2010(UTC)
Posts: 872
|
Try this https://support.kaspersk...2010/error?qid=193238603There are some pictures missing, but basically if I remember correctly you just need to set up dr watson so it catches the crashes.
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
