Looking for an software activity logger

>Are you using MS Visual Studio as development environment?

No, I do not have MS Visual Studio installed on this machine. This software is installed on a basic Windows 7 (64 bit) computer. The operator is not a programmer and it would be inappropriate to install anything more than some form of activity logger that can record activity specifically related to this Windows app.

I have looked at several key loggers but none have the ability to focus on one problem.

This issue has been plaguing me for weeks and the Windows system logs say the same thing every time... I need to gather more information in a more unorthodox way.

Hello John,

Cool idea. I have never looked at the Windows Reliability Monitor until now.
The only errors on this computer are all from my program. :(

But the only consistency is that mscorlib appears at the center of this failure, each time.

It's cool to look at but it won't help me gather anything more than the app logs already record.  Expect perhaps, I have learned that my program is keeping this computer from achieving a 10 reliability rating. :(

But still, thanks for this!

>Do you get a detailed .net error screen (with the option, more details, continue, quit )

Do you mean at the point of failure?

No, according to user. Just your typical "xxx app has stopped working" error.

However, just today (this user is great for getting screen caps)... the error message was a bit different. It stated: "System.Runtime.InteropServices.COMException (0x80070008): Not enough storage is available to process this command"

That is more revealing than the other errors...suggests possible memory fragmentation. ??

>Use .NET Framework Verifier to see if elements are not working.

Thanks for that. Very useful tool.
I have confirmed that there are no problems detected with the .NET framework v4.5.1.

>Can you install .NET Framework and reinstall it?   That might help.

That was already done.

I think that if I can just find some form of system logger that can target one program, I might see a pattern to the crashes. There must be something out there that can do that?

update:
Well... there are tools but everyone that I have found is designed to watch employees over a corporate network. Way too much for my requirements. :(

Then I broadened my research to 'simple' key loggers and discovered that many of them, according to their feature list, might actually do the job. Problem is... how can I trust these? I am not about to install a key logger made by some unknown company off the Interweeb!  The next step is to look for reputable companies and reviews.

Okay, I am testing "All In One Keylogger" http://www.relytec.com

It seems to have basic filtering, I can create white lists to the program in focus for text and screen capture recording. Pretty cool.

I am still willing to consider other solutions or ideas.

Thanks

Actually, while you do all the difficult research and work, did you actually factor in that the error coulde be in the source code, and even if you find out more (for instance about who/what/why), that you're still not much closer to a solution (since you never mentioned contacting the original developer, I'm assuming you won't, even after you find out more information).

I agree with Kimputer.
I would still prefer using VS environment if possible. You can set up remote debugging session on affected computer.
Another way would be testing application in question on another machine with debugging environment.
I do not think any key logger is going to tell you what is wrong.

>did you actually factor in that the error coulde be in the source code

Of course.

But also, it could be the specific environment or an obscure .Net problem.

Either way, the purpose of the key logger to to determine whether or not a pattern exists. It isn't going to magically point to the cause of the problem, however, if a pattern emerges, it will..uh... er... "may" help to potentially narrow down the cause.

It is just a 'better than nothing' diagnostic step because no other apparent cause has been found. This is one of those weird errors on one-off products that cannot be replicated in the lab.

Fortunately, the customer is not really concerned but the desire for quality and curiosity are driving this intense effort to find a solution.

If you uninstall the problem software, does Windows 7 behave properly?

Try a couple of other avenues for Windows 7.

1. Run System File Checker. Run SFC /SCANNOW and allow to complete. Restart and check your problem again.

2. If no luck, consider running a Windows 7 Repair Install. Here is a good article with screenshots to do that.

http://www.sevenforums.com/tutorials/3413-repair-install.html

Then if all your efforts fail, then consider backing up and re-installing Windows 7. If you do this, make sure all software EXCEPT the problem software has been installed and Windows is working very well. Then try the problem software.

Hello John,

I think you may have misunderstood the nature of this problem. :)

There are no issues with the Windows 7 installation. It is only our program that crashes (maybe once per day and always after running for several hours).

Hello John,

Thanks. The debugging code was already present but it never revealed anything.

Update: I was able to narrow down the issue to one particular part of the code (a built-in mini text editor).

The 'solution' was to disable this functionality and call up an external text editor. No crashes since doing this.

Thanks for your assistance.

@sconnell - Thank you and I was happy to help.