Desktop error repair tool

Patent metadata

Field	Value
Publication number	US-10601939-B2
Application number	US-201715695764-A
Country	US
Kind code	B2
Filing date	Sep 5, 2017
Priority date	Sep 5, 2017
Publication date	Mar 24, 2020
Grant date	Mar 24, 2020

Abstract

An apparatus includes a scanner and a resolution engine. The scanner detects first and second software exceptions. The scanner also determines that the first software exception occurred previously in a plurality of desktops and that the second software exception did not occur previously in the plurality of desktops. The resolution engine determines a first solution and a second solution for resolving the first software exception and that the first solution has a higher ranking than the second solution. The resolution engine also generates a software patch that implements the first solution and deploys the software patch. The resolution engine further determines a series of steps implemented to resolve the second software exception and records the series of steps to prepare a second software patch if the second software exception occurs again in the plurality of desktops.

First claim

What is claimed is:

1. An apparatus comprising:
a memory; and
a hardware processor communicatively coupled to the memory, the hardware processor configured to:
detect, in a desktop of a plurality of desktops, a first software exception occurring in a first application of a plurality of executing applications;
detect, in a desktop of the plurality of desktops, a second software exception occurring in a second application of the plurality of executing applications, the second application different from the first application;
determine that the first software exception occurred previously in the plurality of desktops by querying a database using keywords from the first software exception;
determine that the second software exception did not occur previously in the plurality of desktops by querying the database using keywords from the second software exception;
determine a first solution and a second solution for resolving the first software exception;
determine that the first solution has a higher ranking than the second solution;
generate a first software patch that implements the first solution in response to the determination that the first solution has a higher ranking than the second solution;
deploy the first software patch;
identify and record a line of code in the second application that was the source of the second software exception;
determine a series of steps implemented to resolve the second software exception;
record the series of steps;
determine that the software patch did not fix the first software exception;
in response to determining that the software patch did not fix the first software exception:
roll back the deployment of the first software patch;
determine that the second solution has the next highest ranking after the first solution;
in response to the determination that the second solution has the next highest ranking after the first solution, generate a second software patch that implements the second solution; and
deploy the second software patch

detect, in a desktop of the plurality of desktops, a third software exception occurring in a third application of the plurality of executing applications, the third application different from the second application;
determine that the third software exception is the same as the second software exception;
in response to determining that the third software exception is the same as the second software exception, prepare a third software patch using the recorded series of steps and the recorded line of code;
deploy the third software patch;
determine a fourth software exception occurring in a fourth application of the plurality of executing applications;
determine that there is no solution for the fourth software exception; and
in response to determining that there is no solution to the fourth software exception, record the fourth software exception as unsolvable;
add, to a log, an indication that the first software exception was resolved using the software patch; and
add, to the log, the series of steps that resolved the second software exception.

2. The apparatus of claim 1 , wherein the hardware processor is further configured to communicate an alert indicating that the first software exception can be resolved through the first software patch.

3. The apparatus of claim 1 , wherein the hardware processor is further configured to monitor the plurality of desktops to detect when exceptions have been thrown.

4. The apparatus of claim 1 , wherein the first solution has a higher ranking than the second solution because the first solution has a higher success rate of resolving the first software exception than the second solution.

5. The apparatus of claim 1 , wherein the hardware processor is further configured to monitor the desktop in which the second exception occurred to determine the series of steps.

6. The apparatus of claim 1 , wherein determining the series of steps implemented to resolve the second software exception is performed in response to determining that the second software exception did not occur previously in the plurality of desktops.

7. The apparatus of claim 1 , wherein deploying the third software patch fixes the third software exception.

8. A method comprising:
detecting, in a desktop of a plurality of desktops, a first software exception occurring in a first application of a plurality of executing applications;
detecting, in a desktop of the plurality of desktops, a second software exception occurring in a second application of the plurality of executing applications, the second application different from the first application;
determining that the first software exception occurred previously in the plurality of desktops by querying a database using keywords from the first software exception;
determining that the second software exception did not occur previously in the plurality of desktops by querying the database using keywords from the second software exception;
determining a first solution and a second solution for resolving the first software exception;
determining that the first solution has a higher ranking than the second solution;
generating a first software patch that implements the first solution in response to the determination that the first solution has a higher ranking than the second solution;
deploying the first software patch;
identifying and recording a line of code in the second application that was the source of the second software exception;
determining a series of steps implemented to resolve the second software exception; and
recording the series of steps;
determining that the software patch did not fix the first software exception;
in response to determining that the software patch did not fix the first software exception:
rolling back the deployment of the first software patch;
determining that the second solution has the next highest ranking after the first solution;
in response to determining that the second solution has the next highest ranking after the first solution, generating a second software patch that implements the second solution; and
deploying the second software patch

detecting, in a desktop of the plurality of desktops, a third software exception occurring in a third application of the plurality of executing applications the third application different from the second application;
determining that the third software exception is the same as the second software exception;
in response to determining that the third software exception is the same as the second software exception, preparing a third software patch using the recorded series of steps and the recorded line of code;
deploying the third software patch;
determining a fourth software exception occurring in a fourth application of the plurality of executing applications;
determining that there is no solution for the fourth software exception; and
in response to determining that there is no solution to the fourth software exception, recording the fourth software exception as unsolvable
adding, to a log, an indication that the first software exception was resolved using the software patch; and
adding, to the log, the series of steps that resolved the second software exception.

9. The method of claim 8 , further comprising communicating an alert indicating that the first software exception can be resolved through the first software patch.

10. The method of claim 8 , further comprising monitoring the plurality of desktops to detect when exceptions have been thrown.

11. The method of claim 8 , wherein the first solution has a higher ranking than the second solution because the first solution has a higher success rate of resolving the first softw

Assignees

• Bank Of America

Inventors

• Agarwal Ankit
• Patil Amol
• Dabodiya Shailender
• Chauhan Sandeep Kumar

Classifications

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F8/61

  Installation · CPC title

• G06F11/0715

  in a system implementing multitasking (multitasking per se G06F9/46) · CPC title

• G06F11/0748

  in a remote unit communicating with a single-box computer node experiencing an error/fault (remote testing G06F11/2294) · CPC title