Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Diagnosing Strange and Generic Errors | ||||||||
Changed: | ||||||||
< < | To diagnose strange or generic errors (such as bus errors, seg faults, attempting to free freed memory errors, or "an internal error has been detected" errors), run through the following checklist:
| |||||||
> > | To diagnose strange or generic errors (such as bus errors, seg faults, attempting to free freed memory errors, or "an internal error has been detected" errors), run through the following checklist:
| |||||||
Comments:Read what other users have said about this page or add your own comments. | ||||||||
Deleted: | ||||||||
< < | ||||||||
\ No newline at end of file | ||||||||
Added: | ||||||||
> > |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Diagnosing Strange and Generic ErrorsTo diagnose strange or generic errors (such as bus errors, seg faults, attempting to free freed memory errors, or "an internal error has been detected" errors), run through the following checklist: | ||||||||
Line: 8 to 8 | ||||||||
| ||||||||
Changed: | ||||||||
< < | In Release 4.2 and newer, using GUI client (Java) Log into Appx and click <Design an Application>, then select the application that was running when the error occurred. The Application Design menu will be displayed. Click on the <Utilities> tab. The following functions can be found under the Design Repair Tools heading on the Utilities menu. Click <Check for Design Orphans>. The Orphan Detection menu will be displayed. Click <Run Each of the Above>. A report will be created for any processes that contain orphan related errors. Otherwise you will see “No Lines Were Output” if there were no orphan errors. You might want to print any report(s) that show errors. When all the processes have been checked and/or printed, return to the Utilities menu. From the Utilities menu, Click on Verify ANO’s and EM’s. Similar to the above check, a report may be created listing errors. "No Lines Were Output" means the Application passes this test. If any processes fails either of these tests, perform the following: | |||||||
> > | In Release 4.2 and newer, using GUI client (Java)
Log into Appx and click <Design an Application>, then select the application that was running when the error occurred. The Application Design menu will be displayed. Click on the <Utilities> tab. The following functions can be found under the Design Repair Tools heading on the Utilities menu.
Click <Check for Design Orphans>. The Orphan Detection menu will be displayed. Click <Run Each of the Above>. A report will be created for any processes that contain orphan related errors. Otherwise you will see “No Lines Were Output” if there were no orphan errors. You might want to print any report(s) that show errors. When all the processes have been checked and/or printed, return to the Utilities menu.
From the Utilities menu, Click on Verify ANO’s and EM’s. Similar to the above check, a report may be created listing errors. "No Lines Were Output" means the Application passes this test.
If any processes fails either of these tests, perform the following: | |||||||
| ||||||||
Line: 16 to 25 | ||||||||
| ||||||||
Added: | ||||||||
> > | Comments:Read what other users have said about this page or add your own comments. | |||||||
\ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Diagnosing Strange and Generic ErrorsTo diagnose strange or generic errors (such as bus errors, seg faults, attempting to free freed memory errors, or "an internal error has been detected" errors), run through the following checklist:
In Release 4.2 and newer, using GUI client (Java) Log into Appx and click <Design an Application>, then select the application that was running when the error occurred. The Application Design menu will be displayed. Click on the <Utilities> tab. The following functions can be found under the Design Repair Tools heading on the Utilities menu. Click <Check for Design Orphans>. The Orphan Detection menu will be displayed. Click <Run Each of the Above>. A report will be created for any processes that contain orphan related errors. Otherwise you will see “No Lines Were Output” if there were no orphan errors. You might want to print any report(s) that show errors. When all the processes have been checked and/or printed, return to the Utilities menu. From the Utilities menu, Click on Verify ANO’s and EM’s. Similar to the above check, a report may be created listing errors. "No Lines Were Output" means the Application passes this test. If any processes fails either of these tests, perform the following:
|