Click the picture above to return to the main article "How to troubleshoot the 32-bit Console"
The console.exe.log is the central location for many events and errors that happen when using LANDesk. The purpose of this article is to advise on how to read and understand the messages contained in the log. This document will be continually updated as new messages are found and explanations for those messages discovered. For ease of use the messages themselves will be in color. In order to keep this document as short and usable as possible some log entries are being skipped
Location: C:\Program Files\LANDesk\ManagementSuite\Log\Console.exe.log
The detail in the console.exe.log was greatly expanded from 8.8 although many of these messages and errors will translate directly to 8.8 and previous builds as well. Attempts will be made to list these messages in chronological order that they should appear in the log. Chronological order will help determine when/where the console application may experience difficulties.Also, not all messages may appear below as some message are self-describing.
FormMain: Enter constructor: This message is perhaps always the first message you should look for. It is the first entry placed in the log when the console begins to load. A typical console.exe.log will have several loads of the console before the log is renamed to console.exe.log.old so determining the start of the load is important. Another common step is to rename the console.exe.log and reload. The log will be recreated on the fly.
Creating current user and resolving scope: This message is typically followed by several other messages that note the specific user and the time it takes to resolve scopes and rights.
Initializing the network tree: This step is building the Network View in the 32-bit console. It is usually followed by several messages that show AMP rights and the loading of the different nodes. (MyDevcies, PublicDevices, etc)
[FormMain_Activated] Object reference not set to an instance of an object: This message is unknown at this time although it should be noted that the message has been seen on many cores and doesn't appear to cause any problems.
OSDPresenter.cs...: These messages are an update script where OSD is attempting to update scripts from 8.8 to 9.0. This task should only be performed once during the initial login of the console on the core. However, errors have been noticed on remote consoles and have resulted in longer login times. If you see errors in this log then a patch may be needed. Talk to support for patch: LD-4340790
FormMain: Leave FormMain_Load: This is generally the last message recorded when the console finishes loading.
Troubleshooting Unknown Console.exe.log Error Messages:
Critical Exception: System.NullReferenceException: Object reference not set to an instance of an object.
The error above contains a lot more information than what is shown but the first few lines are generally the most important. When troubleshooting this type of error much of the wording will produce a lot of results so searching on the right key words is very important. Here are portions of the error explained...
NullReferenceException = This portion of the error is the definition of the problem itself. If you are familiar with databases then the first impression is that this is a NULL entry in one of the database tables where NULL's are prevented. While a NULL entry can definitely be the cause it is seldom the primary source of this error. NULL entries are usually contained by contraints and other settings in the database itself. Most likely a previous application call couldn't load information correctly so the default in memory is NULL.
Object reference not set to an instance of an object = Usually this error occurs when an application is trying to call information that is supposed to be in memory but failed due to other reasons. The most common reason is corruption in the database tables.
at LANDesk.ManagementSuite.PatchManagement.ComputerVulnerabilitiesForm = This is the GUI form where the problem took place. Given the name of the form most likely a previous SQL call to retreive information from the Patch Management or Vulnerabilities tables failed which resulted in the form being unable to load and display the data. See the "Corrupted Database Tables" section in DOC-10924.
Summation: Most like there is database corruption in tables relating to Patch Management. This could be a dependant or related table.
LANDesk.ManagementSuite.RBA.ADIntegration.ActiveDirectory.CheckADAvailable(String path, DirectoryEntry entry)
COMException = The COM+ objects in windows are experiencing a problem.
System.DirectoryServices.DirectoryEntry.Bind = This function is trying to connect to previously retrieved information.
System.DirectoryServices.DirectorySearcher.Find = This is a search function used to retreive information
LANDesk.ManagementSuite.RBA.ADIntegration.ActiveDirectory.CheckADAvailable = This is the primary function that starts the process. It is attempting to verify rights.
Summation: The COM+ objects probably don't have enough rights to fully traverse active directory. This may or may not be a fatal error. There are several cases where a failure to access a certain portion of AD may not be necessary for the action taking place.
Violation of UNIQUE KEY contraint 'UQ_GroupID'. Cannot insert duplicate key in object 'dbo.DEVICEGROUPINFO'
UNIQUE KEY = A unique index value used in relational databases.
UQ_GroupID = The name of the particular constrait (rule) that defines the unique key.
Cannot insert duplicate key = An insert SQL statement is trying to take place but failed because the index/key already exists.
dbo.DEVICEGROUPINFO = The name of the table where the insert is taking place.
Summation: Console.exe is trying to perform an insert SQL statement but the statement failed because data already exists. Comparing this table to a working table should show the error.