Click the picture above to return to the main article "How to troubleshoot the 32-bit Console"
Error messages in the 32-bit console usually come in two flavors: Errors that pop-up on the screen and errors that are recorded in the logs. There are a lot of similarities on how these errors are troubleshot but there are also some differences. One key to troubleshooting any errors in the 32-bit console is to look for uniqueness. That is...a portion of the error that will probably show up very little when entered into a search engine. The 32-bit console is a 32-bit windows application and just like other 32-bit applications it is susceptible to windows wide error messages. Performing a general search using www.google.com for different parts of the error message can help in identification and finding the source of the problem.
Errors that Pop-up
Screen shots of these errors are very helpful as they often contain long strings or memory addresses that are tedious to record manually. Usually...but not always...these messages happen at a particular time or event so analyzing what happens during that event is a good start. Occasionally a series of events or mouse clicks can trigger the problem as well so keeping track of what was done before the error happened will help in troubleshooting. Errors that pop-up have a history of being more fatal to the application. Checking the Windows Event Logs can shed some light as usually these errors are caught by OS.
Log Reported Errors
These errors are primarily located in the console.exe.log. The error may take on several different forms and some errors are actually expected or normal. For more information on reading/interpreting the console.exe.log and expected error messages please see DOC-9940.
Unfortunately there are too many types of errors in the console.exe.log to list in one article. It's therefore important to first perform searches as discussed in the Introduction above in www.google.com and community.landesk.com. If the search results don't produce anything helpful then breaking down the error would be the next step. The first step in breaking down errors in the console.exe.log is to realize that the log is a chain of events. Problems that happen early on in the log may cause other errors later in the log. Starting with the first reported error is usually the best idea but analyzing each error may help as well.