MS Access Forum / Developer Toolkits / February 2007
I want to find CER v2.0
|
|
Thread rating:  |
George - 16 Feb 2007 21:44 GMT I request help locating a download of Corporate Error Reporting tool CER, version 2.0. According to docs I have found it is the only current tool Microsoft has that is WER aware, even though its intended use was with Office development.
The CER tool is discussed in the following links: http://www.microsoft.com/resources/satech/cer/InstallationMNU.asp http://www.microsoft.com/technet/prodtechnol/Visio/visio2002/reskit/CH11.mspx
It supports BOTH WER and CER. CER is for Office, but WER is other products. It is only tool I know of that supports Windows Error Reporting (WER) configuration, which is why I want it. I intend to spy on it as I change WER reporting configuration so I can send crash dumps to my organization. (There is no WER documentation I know of that shows how to configure beyond very simple.)
The download link http://office.microsoft.com/en-us/orkXP/HA011362771033.aspx does not work for me because they want a volume license and I only have a Visual Studio 2005 Pro license.
MSDN Concierge couldn't help.
Thanks in advance ...
Charles Wang[MSFT] - 19 Feb 2007 04:39 GMT Hi, Per my understanding, you would like to download the CER tool which requires a volume license; however you just had VS 2005 Pro license. If I have misunderstood, please let me know.
Since the question is a license issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations.
Best regards, Charles Wang Microsoft Online Community Support
====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
George - 19 Feb 2007 15:29 GMT Charles,
Sounds that way the way I said it.
The docs, articles, etc. that I have found indicate that CER used to be distributed with Ofice and with Windows XP and even with pre XP Office SDKs, all of which I can have based on my licenses. However, I have been unsuccessful in actually finding it, even with these distributions. The one site reference I found that refers to a download site takes me to the volume licensing site. I think this may be an error, but I don't know.
I AM NOT asking for something that I don't have licensing for, but rather how to get a tool that I think I do have licensing for. Alternatively, good enough documentation on Windows Error Reporting (WER) to actually use it.
Thank you,
George
> Hi, > Per my understanding, you would like to download the CER tool which [quoted text clipped - 19 lines] > rights. > ====================================================== Charles Wang[MSFT] - 20 Feb 2007 11:22 GMT Hi George, Thanks for your response.
I am sorry that I misunderstood your meaning. Your problem is that you could not find the tool CER V2.0, right?
From my research, it seems to be here: 1. Click Start, click Run..., input gpedit.msc, and type enter; 2. Expand Computer Configuration, expand Administrative Templates, expand System, select Error Reporting; 3. Double click the displayed items and enable them.
Since I never use this tool before, I am not sure if the above information is your want; however if that is not right, please feel free to let me know. I will consult the product team for confirmation.
Have a good day!
Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications
If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
George - 20 Feb 2007 18:49 GMT Charles,
"I am sorry that I misunderstood your meaning. Your problem is that you could not find the tool CER V2.0, right?"
Right - and it is my fault for forming my question poorly.
The procedure you gave me got the info I wanted from CER, whether it is cer.exe or not. Thank you very much.
And now a follow up question, if I may: I thought that the registry key HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW\Installed = path to program to create the error report files (cabs, etc.) for error reporting. Apparently it is not, or it is over-ruled elsewhere. Do you know where the error reporting program is specified?
Any clues on documentation for Windows Error Reporting would be appreciated.
Thank you again, George
> Hi George, > Thanks for your response. [quoted text clipped - 45 lines] > rights. > ====================================================== Charles Wang[MSFT] - 21 Feb 2007 09:50 GMT Hi, George, I can see a registry key DW0200 under the Installed key, from which I found that the DW20.exe is located in the directory: C:\Program Files\Common Files\Microsoft Shared\DW
For the documentation regarding Windows Error Reporting, please refer to: Windows Error Reporting: Getting Started http://www.microsoft.com/whdc/maintain/StartWER.mspx How Windows Error Reporting Works http://www.microsoft.com/whdc/maintain/WER/WERWorks.mspx How To Configure and Use Error Reporting in Windows XP http://support.microsoft.com/kb/310414/ Description of the Windows Error Reporting tool (Dw20.exe) http://support.microsoft.com/kb/841477 Windows Error Reporting http://msdn2.microsoft.com/en-us/library/ms681662.aspx
Hope this helps. If you have any other questions or concerns, please feel free to let me know.
Best regards, Charles Wang Microsoft Online Community Support
George - 21 Feb 2007 16:04 GMT Charles,
Yes, using a regedit search I found that key HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW\Installed\DW0200 with value as you said. I even changed this to point to a program of my own choosing with no observable effect on error reporting.
I have used regmon, procmon and/or process explorer to watch while I introduced an intentional crash, and I don't think DW20.exe generates the crash dialog. I believe one of the reporters is dwwin.exe, but it also depends on other error reporting options. The only place I find dwwin.exe in the registry seems to be in some cache, so I guess I cannot preempt it there. And it seems windows won't let me replace dwwin.exe with my own.
Thank you for all the links to docs. Some I had found, some I had not. I will chase them down.
Thank you for your help, George
> Hi, George, > I can see a registry key DW0200 under the Installed key, from which I [quoted text clipped - 20 lines] > Charles Wang > Microsoft Online Community Support Charles Wang[MSFT] - 22 Feb 2007 12:09 GMT Hi, George, Thanks for your updating and response.
You are right. From my research, dwwin.exe is named as "Microsoft Application Error Reporting". It is in the system direcotry: C:\Windows\System32. From the KB841477, I think that the tool DW20.exe should be only for Office program.
For the other error reporting options that dwwin.exe depends, I checked the Service list on my computer and found that "Error Reporting Service" refers to "C:\WINDOWS\System32\svchost.exe -k netsvcs". From the introduction of "Display Error Notification" in gpedit.msc, I believe that the error reporting service also depends on System Event Notification, which executable path is also "C:\WINDOWS\system32\svchost.exe -k netsvcs". Hope this can give you some hints!
However I am a little confused why you would like to know them, since I think that it seemed no relations with your question, "And now a follow up question, if I may: I thought that the registry key HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW\Installed = path to program to create the error report files (cabs, etc.) for error reporting. ". The error messages are automatically writen into a report and sent to a corporate upload file path, why did you need to program to create the error report files?
Could you please describe me your needs more detailed so that I can understand your requirements and try to find a resolution?
Have a good day!
Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications
If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
George - 22 Feb 2007 16:53 GMT Charles,
I appreciate your interest. We have wondered far from the original question and I hope there is general interest in the subject of error reporting and crash analysis. It has certainly been a learning process for me.
My company builds a data acquisition product wherein a PC with special DMA interface cards serves as the main controller and console. For security and other reasons there is no network connection to these machines which are in remote locations.
Sometimes the software crashes ;o) When this happens we want to generate a crash dump and alert the operator to take steps to get the dump to us for analysis. Windows will make an error report and put it in a cab file, but I have found this not as useful as a regular ntsd minidump (probably my own lack of knowledge or experience here).
Making my own dump was simple. I just set the value of Debugger to "C:\WINDOWS\system32\ntsd" -p %ld -e %ld -g -c ".dump c:\CRASH.DMP;q" , replacing the jit debugger in [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug]. If I also set Auto to 1, then I get a crash dump every time and no error notification at all.
The problem is with notification. I thought I could bend the Windows or Corporate Error Reporting to the task, but for the simple screens the options are ambiguous to the operators ("Debug or close" with a "click here for more information" option for one set of options, and "OK to terminate, CANCEL to debug" for another set of options) and the Windows screen to report via e-mail, even with the queuing option to replace e-mail and the ability to rename the entity, still falls short. The three choices are "Debug", "Send Error Report" and "Don't Send", and the "To see what data this error report contains, click here" option leads to screens that still identify Microsoft and other stuff which is confusing to the operators.
Ideally, if a crash occurs we would ALWAYS make a crash dump and then prompt the operator to get the file to us however he can. No other options.
I seem to have exhausted the possibility of using existing Windows error notification. I am now considering two possibilities:
1. Somehow using a command line that not only spawns ntsd, but also spawns my own program to do notification. I have not figured out how to do this. Does ntsd support something like a .spawn command?
2. Running a background process that watches for a crash dump and notifies the operator and does housekeeping for the dumps.
At the moment my money is on option 2, but I think option 1 would be better.
By the way, kudos for the Microsoft symbol server scheme. That is really slick.
Thank you for your help, George
> Hi, George, > Thanks for your updating and response. [quoted text clipped - 59 lines] > rights. > ====================================================== George - 22 Feb 2007 23:46 GMT Charles,
Late breaking news ...
I find that if I set the registry AeDebug key Debugger value to
"C:\WINDOWS\system32\ntsd" -p %ld -e %ld -g -c ".dump c:\CRASH.DMP;.shell C:\MyPath\MyProgram.exe -i- -x"
and Auto to 1 that I can run MyProgram which can do the dialog I want.
The problem is that it leaves ntsd running. I suppose I could terminate that process from MyProgram.exe?
George
> Hi, George, > Thanks for your updating and response. [quoted text clipped - 59 lines] > rights. > ====================================================== Charles Wang[MSFT] - 26 Feb 2007 08:02 GMT Hi, George, Thanks for your response.
>The problem is that it leaves ntsd running. I suppose I could terminate that process from MyProgram.exe?
Yes, you can terminate the process however you may need to have your application running with administrator permission. Please refer to: How to Kill an Orphaned Process http://support.microsoft.com/kb/197155 KILL http://msdn2.microsoft.com/en-us/library/aa933230(SQL.80).aspx
If you have any other questions or concerns, please feel free to let me know.
Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications
If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
George - 26 Feb 2007 15:15 GMT Charles,
Thanks for your help.
George
> Hi, George, > Thanks for your response. [quoted text clipped - 43 lines] > rights. > ======================================================
|
|
|