Controlling software failure data reporting and responses

• US 7,380,171 B2
• Filed: 12/06/2004
• Issued: 05/27/2008
• Est. Priority Date: 12/06/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Prescott, Allen K., Dinklocker, Ted E., Kashiramka, Komal, Punukollu, Shanti P., Chang, Su Chin
• Primary Examiner(s): Wilson; Yolanda L
• Application Number:
  US11/005,386
• Publication Number:
  US 20060136784A1
• Time in Patent Office: 1,268 Days
• Field of Search: 714/38, 714/48, 719/318
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level

Abstract

User input defines transmission filter rules to be met when sending an error report to a support provider. User input also defines collection filter rules to be met when including failure data within an error report. Error reports corresponding to crash failures at clients are filtered with the transmission filter rules to determine which of the error reports to send to the support provider, and each error report to be sent to the support provider is further filtered to remove any failure data that fails to satisfy the collection filter rules. Each error report that satisfies the transmission filter rules, along with the failure data satisfying the collection filter rules, is sent to the support provider for analysis. Standard and or custom failure responses corresponding to the failures at the clients may be retrieved and sent to the clients in accordance with the collection filter rules.

Claims

1. In a failure data management server connected to one or more clients and to one or more support providers, the one or more support providers receiving error reports containing failure data from the one or more clients and the one or more failure data management servers to use in determining one or more fixes for one or more failures occurring at the one or more clients, a method of controlling failure data reporting, the method comprising acts of:

receiving user input that defines one or more transmission filter rules to be met when sending an error report to a support provider;

receiving user input that defines one or more collection filter rules to be met when including failure data within an error report;

receiving one or more error reports corresponding to one or more failures at one or more clients;

filtering the one or more received error reports with the one or more transmission filter rules to determine which of the one or more received error reports to send to the support provider;

filtering each error report to be sent to the support provider to remove any failure data that fails to satisfy the one or more collection filter rules; and

sending each error report that satisfies the one or more transmission filter rules, with failure data that satisfies the one or more collection filter rules, to the support provider for analysis.

2. A method as recited in claim 1, wherein the one or more transmission filter rules comprise at least one of (i) an application name, (ii) a module name, (iii) a user name, (iv) a machine name, (v) a failure error type, or (vi) a generic event type.

3. A method as recited in claim 1, wherein the one or more collection filter rules allow for at least one of (i) a memory dump, (ii) application compatibility information, (iii) operating system version information, (iv) registry information, (v) hardware configuration information, or (vi) client file information.

4. A method as recited in claim 1, wherein each error report comprises a failure signature that identifies a program location where the failure occurred.

5. A method as recited in claim 4, wherein the one or more transmission filter rules comprise an indicator to send only the failure signature for each error report that satisfies the one or more transmission filter rules.

6. A method as recited in claim 4, wherein each error report comprises additional information, including at least one of (i) a memory dump, (ii) application compatibility information, (iii) operating system version information, (iv) registry information, (v) hardware configuration information, or (vi) client file information.

7. A method as recited in claim 6, wherein the additional information is stored in one or more individual files, and wherein each of the one or more individual files is compressed within a cabinet file.

8. A method as recited in claim 7, wherein multiple error reports are received and correspond to a single failure signature, the method further comprising acts of:

receiving user input that defines a cabinet file count for the single failure signature; and

eliminating any cabinet files in excess of the cabinet file count for the single failure signature.

9. A method as recited in claim 1, further comprising acts of:

retrieving one or more failure responses corresponding to the one or more failures at the one or more clients; and

sending the one or more failure responses to the one or more clients.

10. For a failure data management server connected to one or more clients and to one or more support providers, the one or more support providers receiving error reports containing failure data from the one or more clients and the one or more failure data management servers to use in determining one or more fixes for one or more failures occurring at the one or more clients, a computer program product comprising one or more computer readable storage media having stored computer executable instructions that implement a method of controlling failure data reporting, the method comprising acts of:

receiving user input that defines one or more transmission filter rules to be met when sending an error report to a support provider;

receiving user input that defines one or more collection filter rules to be met when including failure data within an error report;

receiving one or more error reports corresponding to one or more failures at one or more clients;

filtering the one or more received error reports with the one or more transmission filter rules to determine which of the received error reports to send to the support provider;

filtering each error report to be sent to the support provider to remove any failure data that fails to satisfy the one or more collection filter rules; and

sending each error report that satisfies the one or more transmission filter rules, with failure data that satisfies the one or more collection filter rules, to the support provider for analysis.

11. A computer program product as recited in claim 10, wherein the one or more transmission filter rules comprise one or more deny lists, each containing (i) one or more application names, (ii) one or more module names, (iii) one or more user names, (iv) one or more machine names, (v) one or more failure error types, or (vi) one or more generic event types.

12. A computer program product as recited in claim 10, wherein the one or more transmission filter rules comprise a simple error report type for uploading data from one or more applications to the support provider.

13. A computer program product as recited in claim 10, the method further comprising an act of maintaining status information for each of the one or more received error reports.

14. A computer program product as recited in claim 13, wherein the status information comprises at least one of (i) queued for transmission filtering, (ii) unreported, (iii) queued for transmission, (iv) retry, or (v) reported.

15. A computer program product as recited in claim 10, the method further comprising acts of:

retrieving one or more failure responses corresponding to the one or more failures at the one or more clients; and

sending the one or more failure responses to the one or more clients.

16. A computer program product as recited in claim 15, wherein the one or more failure responses are received from the support provider.

17. A computer program product as recited in claim 16, further comprising an act of filtering each of the one or more failure responses to remove any requests for failure data that fails to satisfy the one or more collection filter rules.

18. A computer program product as recited in claim 15, the method further comprising an act of receiving user input that defines the one or more failure responses at the failure data management server.

19. A computer program product as recited in claim 18, the method further comprising an act of publishing the one or more failure responses to the support provider for use by one or more other failure data management servers.

20. A computer program product as recited in claim 15, wherein the one or more failures at the one or more clients comprise one or more setup failures.

21. For a failure data management server connected to one or more clients and to one or more support providers, the one or more support providers receiving error reports containing failure data from the one or more clients and the one or more failure data management servers to use in determining one or more fixes for one or more failures occurring at the one or more clients, a computer program product comprising one or more computer readable storage media having stored computer executable instructions that implement a method of controlling failure data reporting, the method comprising steps for:

storing one or more transmission filter rules containing one or more transmission criteria to be met when sending an error report to a support provider;

storing one or more collection filter rules containing one or more collection criteria to be met when including failure data within an error report;

collecting one or more error reports corresponding to one or more failures at one or more clients;

determining which of the one or more error reports to send to the support provider based on the one or more transmission filter rules;

for each error report to be sent to the support provider, applying the one or more collection filter rules so that only failure data satisfying the one or more collection filter rules remains within the error report; and

submitting each error report that satisfies the one or more transmission filter rules, with failure data satisfying the one or more collection filter rules, to the support provider for analysis.

22. A computer program product as recited in claim 21, wherein the one or more transmission filter criteria comprise one or more allow lists, each containing (i) one or more application names, (ii) one or more module names, (iii) one or more user names, (iv) one or more machine names, (v) one or more failure error types, or (vi) one or more generic event types.

23. A computer program product as recited in claim 21, wherein the one or more content filter criteria allow for at least one of (i) a memory dump, (ii) application compatibility information, (iii) operating system version information, (iv) registry information, (v) hardware configuration information, or (vi) client file information.

24. A computer program product as recited in claim 21, the method further comprising an act of receiving user input that defines an interval for collecting any new error reports.

25. A computer program product as recited in claim 21, the method further comprising an act of receiving user input that defines an interval for transmitting new error reports to the support provider for analysis.

26. A computer program product as recited in claim 21, the method further comprising acts of:

retrieving one or more failure responses corresponding to the one or more failures at the one or more clients; and

sending the one or more failure responses to the one or more clients.

27. A computer program product as recited in claim 26, wherein the one or more failure responses comprise one or more requests for additional information.

28. A computer program product as recited in claim 27, the method further comprising an act of receiving the additional information requested in the one or more requests from the one or more clients.

29. A computer program product as recited in claim 28, further comprising an act of sending the additional information requested in the one or more requests to the support provider.

30. A computer program product as recited in claim 27, wherein the additional information requested in the one or more requests comprises at least one of (i) a memory dump, (ii) application compatibility information, (iii) operating system version information, (iv) registry information, (v) hardware configuration information, or (vi) client file information.

31. A computer program product as recited in claim 26, wherein the one or more failure responses comprise one or more fixes for the one or more failures at the one or more clients.

32. A computer program product as recited in claim 31, wherein the one or more fixes comprise one or more instructions indicating how to prevent the one or more failures at the one or more clients from occurring.

33. A computer program product as recited in claim 31, wherein the one or more fixes comprise one or more software updates that prevent the one or more failures at the one or more clients from occurring.

34. A computer program product as recited in claim 21, wherein the step for applying the one or more collection filter rules so that only failure data satisfying the one or more collection filter rules remains within the error report comprises removing additional information that fails to satisfy the one or more collection filter rules.

35. A failure data management server that controls failure data reporting from one or more clients to a support provider for use in determining one or more causes for one or more failures occurring at the one or more clients, the failure data management server comprising:

an administrative console interface that receives user input to define;

one or more transmission filter rules containing one or more transmission criteria to be met when sending an error report to a support provider;

one or more collection filter rules containing one or more collection criteria to be met when including failure data within an error report; and

one or more custom failure responses;

a local data store that stores;

the one or more transmission filter rules;

the one or more collection filter rules;

the one or more custom failure responses;

one or more standard failure responses; and

one or more error reports;

an agent that;

collects one or more error reports corresponding to one or more failures at one or more clients; and

provides the one or more custom and the one or more standard failure responses to the one or more clients;

an error report manager that;

filters the one or more error reports with the one or more transmission filter rules to determine which of the one or more error reports to send to the support provider;

filters each error report to be sent to the support provider to remove any failure data that fails to satisfy the one or more collection filter rules; and

sends each error report that satisfies the one or more transmission filter rules, with failure data satisfying the one or more collection filter rules, to the support provider for analysis; and

a response manager that;

retrieves the one or more custom failure responses and the one or more standard failure responses corresponding to the one or more failures at the one or more clients for the agent.

36. A failure data management server as recited in claim 35, wherein the response manager publishes the one or more custom failure responses to the support provider for use by one or more other failure data management servers.

37. A failure data management server as recited in claim 35, wherein the error report manager maintains status information for each of the one or more error reports.