Capturing resman.exe errors

[On a Quest]

Simply, what is the most effective way to capture and report errors from resman.exe.  

I run resman silently with a log file.  Currently I do not parse log file or anything else.  Sometimes, due to cabling issues,etc, I suspect resman is failing but  I do not know if that is the case.  How do I find out if resman is trying to tell me about errors when I'm running siliently?

[Chris_R.]

Hello,
The easiest way to report the status of a resman run is to use the command Windows prompt.  Just browse to the directory where the resman.exe file is and type "resman -l".  That is the small letter L, not a 1.  This will create a resmanX.out file in that folder.  X is the number of your VXI system.  You can then open these files in notepad or any other word processing program.  So, instead of running resman, run resman -l and these files should be created.  I hope this is what you are needing to do, but let me know if you have any questions!

Chris R.
Applications Engineer
National Instruments

[On a Quest]

Chris_R, thanks for your response.

I should have been more specific with my question.  First, manually opening the log file is not practical for our solution, we have an automated process using a c# program.   What I'm trying to figure out is if I run resman 'programmatically' using the the -o -l command arguments, can I using software to search for errors in the log file.  In other words, has the format of the resmanX.out file been defined such that I could make a program search for a word that signifys an error occured during the execuation of resman.exe?  If so, what are the keywords I need to look for?  If you suggest another way all together to do this, please let me know your suggestions.  Perhaps Resman.exe has exit codes that I need to watch out for -   If so, what are their definitions?

Thanks for you help or any one else help in advance!

[Chris_R.]

Hello,
I am currently trying to find a good solution for you.  The resman.out files were never meant to be parsable, so it might not be trivial to extract any information from them.  I am currently still trying to see if there are any keywords that can be searched for to check to see if an error occurred.  I will let you know as soon as I find something for you.

Thanks!

Chris R.

[On a Quest]

Any ideas?

[MichaelChaney]

Hello,

I've asked R&D for an update on this issue.  I'll post a reply here as soon as I hear from them.

[MichaelChaney]

Hello,

R&D has discovered that indeed Resman always prints out "Resource Manager completed sucessfully" or "Resource Manager failed", however this is only replrted on fatal errors.  Device errors typically aren't fatal to Resman.  Resman just logs these device errors, but with no standard string that can be parsed.  So pass/fail can be detected, but not particular device errors.

[On a Quest]

Thanks for your effort -