Method and system for intelligent and adaptive exception handling

1. A method comprising:

receiving at a controller-node, an error message from a network node describing an error associated with the network node;

analyzing the error message to determine an error type for the error;

selecting a solution from a solution table to handle the error based on the error type, wherein the solution table maps error types to solutions;

handling the error based on the solution selected; and

logging the error with an administrative error-reporting application, wherein the administrative error-reporting application detects possible trends in network related activity by analyzing the error message.

2. The method of claim 1 , wherein handling the error based on the solution selected comprises:

communicating a response to the network node, the response including a script command to be executed by the network node, the script command at least partially implementing the solution.

3. The method of claim 2 , wherein the network node comprises a network-connected script engine, the network-connected script engine to:

receive script commands in a generic format;

translate the script commands from the generic format into a server-specific format; and

send the script commands in the server-specific format to a server for execution.

4. The method of claim 2 , wherein the response further comprises data.

5. The method of claim 2 , wherein the script command causes the network node to continue executing a script that initially caused the error.

6. The method of claim 1 , wherein handling the error based on the solution selected comprises:

communicating a response to a script engine executing at a second network node, the response including a script command implementing the solution, the script engine executing at the second network node to execute the script command on behalf of the first network node associated with the error.

7. The method of claim 1 , wherein logging the error with an administrative error-reporting application comprises:

logging the error with the administrative error-reporting application when no alternative solution for handling the error is available from the solution table.

8. The method of claim 1 , wherein analyzing the error message comprises:

comparing the error message with previously received error messages.

9. The method of claim 1 , further comprising:

analyzing previous solutions used for previous errors;

ranking each previous solution according to a solution selection algorithm; and

rearranging solutions in the solutions table based on the solution selection algorithm, the solutions arranged in order of rank, wherein the rank is based on which solutions successfully solved the previous errors.

10. The method of claim 1 , further comprising:

requesting data from a second controller-node, the second controller-node located on a sub-network separate from a sub-network associated with the first controller-node, the data relating to error messages and potential solutions for those error messages.

11. In a network environment having multiple nodes, a first adaptive controller-node for handling exceptions, the first adaptive controller-node comprising:

input logic to receive an error message from a network node, the error message including a request to handle an error associated with the network node; and

control logic to:

analyze the error message to determine an error type for the error,

request data from a second adaptive controller-node located on a sub-network of the network environment separate from a sub-network associated with the first adaptive controller-node, wherein the data relates to error messages and potential solutions for those error messages, and

select from a solution table, a solution to handle the error based on the error type and the data from the second adaptive controller-node, wherein the solution table to map error types to solutions.

12. The adaptive controller-node of claim 11 , wherein the control logic to further:

send a response to the network node, the response to include a script command for execution by the network node, the script command to at least partially implement the solution; and wherein

the network node comprises a network-connected script engine to execute the script command.

13. The adaptive controller-node of claim 11 , wherein the control logic to further:

send a response message to a script engine executing at a second network node, the response message including a script command to at least partially implement the solution, wherein the script engine executing at the second network node to execute the script command on behalf of the first network node associated with the error.

14. A controller-node comprising:

means for receiving an error message from a network node describing an error associated with the network node;

means for analyzing the error message to determine an error type for the error; and

means for selecting from a solution table a solution to handle the error based on the error type, wherein the solution table to map error types to solutions, and wherein the solution comprises means for sending a response message to a script engine separate from the network node, the response message including a script command at least partially implementing the solution, wherein the script engine to execute the script command on behalf of the network node associated with the error.

15. The controller-node of claim 14 , wherein the script command comprises means to cause the network node to continue executing a script that initially caused the error.

16. The controller-node of claim 14 , further comprising:

means for logging the error with an administrative error-reporting application when no alternative solution for handling the error is available from the solution table.

17. The controller-node of claim 16 , wherein the administrative error-reporting application comprises means for detecting possible trends in network related activity by analyzing the error message, wherein analyzing the error message comprises means for comparing the error message with previously received error messages.

18. The controller-node of claim 14 , further comprising:

means for analyzing previous solutions used for previous errors;

means for ranking each previous solution according to a solution selection algorithm; and

means for rearranging solutions in the solutions table based on the solution selection algorithm, the solutions arranged in order of rank, wherein the rank is based on which solutions successfully solved the previous errors.

19. The controller-node of claim 14 , further comprising:

means for requesting data from a second controller-node, the second controller-node located on a sub-network separate from a sub-network associated with the first controller-node, wherein the data relates to error messages and potential solutions for those error messages.