Problem:

Console shows this error when trying to log in:

Resolution:

Start the LDAppWeb Application Pool on the Core Server.

1. To start the LDAppWeb Application Pool, open The IIS Manager, expand your core server and select the Application Pool dropdown:

2. Right-Click LDAppWeb and select Start:

Introduction:

Throughout the use of the 32-bit or Web Console various icons are displayed. Sometimes the definition of those icons isn't 100% clear. Listed below are icons and their corresponding definitions.

This icon means that HTML5 Remote Control is available (present only after applying LD95-CP_BASE-2014-0625 patch LDMS 9.5 SP2).

Standard Client Icon. This includes Windows clients as well as Linux clients and Unix servers.

Server Icon. This icon represents Windows server based OS's.

Macintosh Icon.

Agent Status Icon with Remote Control and Common Based Agent. This icon indicates that the Management Agent as well as Remote Control on the client have been contacted and should be available. The binoculars represent the Management Agent while the Remote Control icon is for the Remote Control Service.

Agent Status Icon with Remote Control Only. This device could only reach the Remote Control portion of the installed agent. This could indicate a problem with the Management Agent on the device or the Management Agent service is stopped.

Agent Status Unknown Icon. This icon is usually present when Agent Status/Discovery is taking place.

     *** Possible Fixes***

               *Verify communication is working over port 9595. In console, open web browser and navigate to http://(IP of client):9595. If successful, you'll see the LANDesk banner across the top.

               *In LDMS, go to Configure - Agent Status Options - Make sure that "For selected visible items only" is selected. NOT "For all visible items".

Agent Status Failed Icon. The device couldn't be contacted on either Remote Control or the Management Agent.

Scheduled Task Not Started Icon.

Scheduled Task Re-Occurring Icon. This task will launch over and over at a designated time.

Scheduled Task Successful Icon. The scheduled task finished without any reported problems.

Scheduled Task Problem Icon. The scheduled task finished but at least some of the devices reported problems.

Scheduled Task Active Icon. The scheduled task is currently running.

Critical Alert Icon. The device has an alert or condition that is affecting health. This requires monitoring to be configured and installed on the client. Example: A device is configured to alert when the hard drive becomes too full. Alerting is configured to fire a warning alert when the drive is at 80% full and a critical alert at 90% full. Once the device crosses 90% an alert is sent to the core and the device's health state is marked as critical.

Warning Alert Icon. Similar to the critical icon above but the alert is in a warning state. See previous critical example...the device has crossed the 80% warning so an alert was fired to the core and the health state was marked as warning.

Empty Device Icon. This icon represents a device that is discovered by UDD (in inventory) but does not yet have an agent.

Description: The following error is displayed when launching a remote console and attempting to connect to a core server.

Console Initialization Error: Value cannot be null. Parameter name: userId

Resolution: Check the following registry key on the core server. The value for isNTLM needs to be set to "False". This setting is not currently used and will cause problems if it's enabled.

HKLM\Software\LANDESK\ManagementSuite\Core\Connections\Local

When logging in to console on one machine, an error appears which says: Console initialization error: The type initializer for "Computer" threw an exception. This error occurs after changing the password on the domain. After clearing the error, there is nothing listed under "All Devices". Logging into another computer with the remote console results in no problem. Other users can log into the console on the effected machine without a problem.

Cause License cookie for the current user is either damaged or incorrect.

Use the following steps to resolve the issue.  If one step does not fix the problem, continue on to the next step.

Step 1:

Open the registry editor on the machine affected and navigate to:

HKEY_CURRENT_USER\Software\LANDesk\ManagementSuite\Core\

Delete the LicenseCookie value.

Logging back into the console will recreate the license cookie.

Step 2:

Open a command prompt on the computer the console is installed on and run the following commands:

cd \program files\common files\system\ado

regsvr32.exe msado15.dll

cd \winnt\system32

dir atl*.dll

regsvr32.exe atl71.dll (or whichever atl.dll you have)

cd \program files\landesk\managementsuite

regsvr32.exe parser.dll

regsvr32.exe ldcache.dll

regsvr32.exe msinterp2.dll

regsvr32.exe idal.dll

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.

Step 3:
Run C:\Windows\Microsoft.net\framework\<.NET VERSION>\aspnet_regiis.exe -i

Step 4:
Reinstall the MDAC component on the machine. Right click and reinstall from C:\WINDOWS\inf\mdac.inf and obtain the file off of a windows CD. Or download a new copy from Microsofts site. Check Microsofts download site for the latest version.

Step 5:
Check the console.exe.log. If there is a COMException listed then change the COM+ objects to a different identity.

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.

Occasionally users of the LANDesk console will notice what appears to be duplicate records for a single client.  This is almost always caused by the column set configuration.  Here's what this looks like:

What I've done is added Computer-Memory-Slots-Memory Slot-Installed Size to my column set configuration.  The clients in my inventory have multiple values for this attribute, and a separate line will be displayed for each unique value.  More commonly, LANDesk users will do this with the NIC address or IP address.  On computers with multiple values for these attributes, multiple records will be displayed.

One way to convince yourself that the multiple records are from the same client in the database and not multiple clients is to add Computer-ID to the column set configuration and take note of whether your multiple records all have the same ID value.

The way to resolve this is to find out which attribute in your column set has multiple values for individual clients and remove it.  As mentioned before, the IP address is frequently the culprit.

It's of course possible that you actually have more than one machine with the same name in the LANDesk database.  In that case you would notice that the Computer-ID values would be different.

This is completely different from problems caused by duplicate device IDs.  This problem is discussed in  The specified item was not found..

Error message:

Retrieving the COM class factory for component with CLSID {D240AD21-4977-11-D1-8FD4-00A0C96523EB} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Problem:

You get this error message when trying to login on the LDMS Console / Remote Console or when you try to access to some of the information in the console.

Cause:

This is due to some .dll not well registered during the installation of the Remote Console. The CLSID number references to ILAD.dll which on the managementsuite folder.

Solution / Workaround:

Follow steps 2 and 3 or article Console Initialization error - Connection failed. The type initializer for "Computer" threw an exception and you are good to go normally.

Unfortunately the present version of Landesk Management Suite can not support configurations that contain additional Consoles installed in other languages then the Core Server. (Eg. an English core with a German console)

Numerous issues has been seen beeing caused by these configurations, mostly related to reporting and agent configruation.

LANDesk's use of UNICODE in 9.0 is the necessary basis for providing cross-language functionality, but unfortunately the function is not available yet.

Reviewed: October 2014

Versions affected: LDMS 9.5 and 9.6

Problem:

When viewing inventory, the console fails to respond after 15 seconds then you are forced to close it as it has crashed. There are no problems with Security scan information or other right click options.  Other nodes that are randomly checked load inventory with no issues

Cause:

These machines may have been become corrupt in the the database and the console is crashing because its having difficulty calling up the information for these machines from the database.

Resolution:

Delete the erroneous  machines from the console, as a test, and then run a full inventory scan from that machine to repopulate this machine into the database.

You can do this by running the following command from the cmd prompt on the client machine:

"C:\program files(x86)\LANDesk\LDClient\LDISCN32.EXE" /NTT=(name of core):5007 /S=(name of core) /I=HTTP://(nameofcore)/ldlogon/ldappl3.ldz /V /SYNC /F

To prevent this happening in the future make sure that you regularly run maintenance against your database to keep it unfragmented and not too large,

Here is an article on how you can achieve this:

LDMS Database tuning for Microsoft 2008 R2 and 2012

Problem

• Web Console timing out, not connecting, or being very slow
• An error of HttpException (0x80004005): Request timed out - (ignores executionTimeout)

Cause

This kind of issue is typically occurs when a server-side code function or macro executes for a period of time longer than the maximum timeout period allowed for server-side code execution.

This can be caused by multiple things :

-Too many users logging into the web console and overloading the worker processes, causing timeouts and big slowdowns on the web console and in extreme cases unusable

-A windows update slightly changing the .net framework in a unknown way , requiring the.net to be re-registered

-A slow network connection to the core server from the administrators computer

Resolutions

• To Re-register .net
• To increase the query time out for the console and web console
• And Decreasing/Managing load on worker processes associated with the web console
  

How to Re-register .net

To Re-register the ASP.NET 4.0 components. Please reference Microsoft KB 2015129for details, or a brief summary follows:

1. Open a command prompt with administrative privileges on the core server
2. Change directory to
   • 32-bit Windows:
     %windir%\Microsoft.NET\Framework\v4.0.30319
   • 64-bit Windows:
     %windir%\Microsoft.NET\Framework64\v4.0.30319
3. Re-register the components:
   aspnet_regiis.exe /iru
4. Reset the IIS services:
   Iisreset

How to increase the query time out for the console and web console

You can increase the query time out in the console and web console using this article :

http://community.landesk.com/support/docs/DOC-1593

Decreasing/Managing load on worker processes associated with the web console

Finally to decrease the load on the worker processes which for the remote console, you can set them to automatically 'recycle' so that the memory , cache etc. associated with these processes will automatically be cleared and new process be created in their place.

Here are some article on the process of recycling associated with the IIS application web pools

http://technet.microsoft.com/en-us/library/cc753179%28v=ws.10%29.aspx

In this example I am going to use the elapsed time option, this way you will know exactly when the application pool gets reset as opposed to every time a certain memory level is reached which can be very sporadic.

Under IIS manager , navigate to the application pools window pane, via the left column.

Right click the LDAppWeb, where the remote console application resides, and click on recycling…

Notice the default time interval for this application is 1740 minutes, change this to 120 minutes and the worker processes associated with this application pool will refresh ' recycle' every 120 minutes. This should relive pressure on the main web console.

This method can also be manually used instead of performing an iisreset cmd, as this will reset only the applications associated with the web console as opposed to the entire IIS infrastructure.

To do this , right click the LDAppWeb, located in the application pools window in the IIS and click recycle. This force the application pool to 'restart' at that moment in time. This can be used in times of urgency to relieve the load on the worker process immediately

Environment:

LDMS 9.5

LDMS 9.6

Windows Server 2008

Windows Server 2012

How to:

How to reset IIS, delete temp .Net files and restart COM+ components for issue related to remote console issues.

Step by Step:

1. Stop IIS

2. Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0(revision number)\Temporary ASP.NET Files and delete all of the files in that folder.

3. Do the same thing to the v2.0 folder as well (C:\Windows\Microsoft.NET\Framework64\v2.0(revision number)\Temporary ASP.NET Files )

4. If using windows server 2008, open a command prompt and run this command to reregister .NET:

5. If using Windows Server 2012, the process is a little different to reregister .NET. Open up the "Remove Roles and Features" window and uninstall the following role and feature:

6. After this finishes uninstalling, open the "Add Roles and Features" window and reinstall the previous role and feature

7. Open Component Services and Shut Down LANDesk and LANDesk1. Start them again after shutting them down:

8. Finally, restart IIS:

Overview

This article functions as a landing page of sorts for the 32-bit console. Due to the complexity of the console and the various ways in which it can break this article will branch out into 5 sub-articles. Each sub-article will contain a link back to this main article.

Console Design and Logs

Console Cache: Console.exe makes use of cache in order to increase the speed of operations. While testing, duplicating an issue, or trying to resolve a problem it becomes important that the console be closed and restarted again and again.

Console User Layouts: The console layout is stored automatically when a user closes the console. A user can also create multiple layouts and revert to them as needed. Sometimes these layouts can cause problems with the console. See the "General Troubleshooting" area below for details on how to delete the user layout.

Core Console vs 32-bit Remote Console: By design only the console on the core server will have access to certain features and settings.

Logs:

• Console.exe.log
  • LANDesk 8.8 Location: C:\Program Files\LANDesk\ManagementSuite
  • LANDesk 9.0 Location: C:\Program Files\LANDesk\ManagementSuite\Logs
• Console.exe.Licensing:
  • LANDesk 9.0 Location: C:\Program Files\LANDesk\ManagementSuite\Logs
• Windows Event Logs
• IIS Logs
  • IIS 6 Location: C:\Windows\system32\LogFiles\W3SVC1\exXXXX.log (name includes date stamp)
    
  • IIS 7 Location: C:\inetpub\logs\logfiles\W3SVC1\u_exXXXXX (name includes date stamp)
    

Console Problem Types and Troubleshooting

Troubleshooting is broken out in the areas below for easy reference however the steps in each of the areas may help resolve any console issue.

General Console Troubleshooting (Layouts, Column Sets, Third Party Applications, UAC, Remote Consoles)

Console Slowness (Identification, Resources, Active Directory, Database Optimization, IIS, Communication Issues)

Error Messages (Identification, Interpretation)

Missing Features or Icons (Licensing, RBA, General Corruption)

How to Interpet the Console.exe.log

Known Issues

Agent Status/Discovery isn't working correctly

32-bit Console may lock up if you attempt to view the properties of a vulnerability

Console Problems after installing .NET 4.0

Remote Console 9.0 SP1 Licensing Error after Upgrading

Recommended Articles

What do those icons in the 32-bit console mean?

Miscellaneous Console Files

Problem

When we create one query then run this query to list the devices those can match the query, but the device list will include multiple duplicated devices, please refer to below screenshot:

Cause

If choosing the queried field as display column, this column will list all the queried data with device name, so there will be multiple duplicated device name in the list

Solution / Workaround

Remove the queried field in the display column, just only leaving device name in the display column,The less display column, the result will be more accurate.

Problem

An error log shows an exception along the following lines:

Arithmetic overflow error converting IDENTITY to data type int

Examples

When running createLandeskrights.exe the following error appears:

"03/10/2014 09:35:58 INFO  2836:1    RollingLog : Exception in UpgradeUserGroupCache: Arithmetic overflow occurred.

Arithmetic overflow error converting IDENTITY to data type int. at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) "

When an inventory scan files is processed on the core, the SCN files is moved to the ErrorScan Folder and the following error appears in the Windows Application Event Log:

Error comitting on table FILEINFOINSTANCE:   ARITHMETIC OVERFLOW ERROR CONVERTING IDENTITY TO DATA TYPE INT.               Increased column size might be necessary.

When rolling up certain tables dont get rolled up correctly or partley , for example the PATCHHISTORY table does not update correctly.

This error can happen on any DB table. This can effect both the LDMS core and the RollUp Core

Cause

This issue is not caused by a limitation or a defect from the LDMS console or core but actaully a limitation from the Microsoft SQL server.

SQL Error received: Arithmetic overflow error converting IDENTITY to data type int:

Please see this article form TechNet on the issue:

http://blogs.msdn.com/b/rathomas/archive/2012/11/06/business-contact-manager-2010-arithmetic-overflow-error-converting-identity-to-data-type-int.aspx

Solution

To reseed the table:

For Example for the PatchHistory table issue the solution is as follows

This is the SQL statement to run on your rollup core to resolve the issue that you are having.

It is higly recommended that you perform a full backup of the LANDESK database before running the SQL query.

USE LDMS95RollUp
DELETE FROM [dbo].[PATCHHISTORY]
DBCC CHECKIDENT ("PATCHHISTORY", reseed, 1)
GO

Change "LDMS95RollUp" to the name of your roll up core DB name.

Change "PATCHHISTORY" to the name of the table with the error

For the other issue with the users not be created or updated due to this limitation this is a lot more complicated as the DB table for these users , [dbo].[ConsoleUser] is connted and referenced in so manay other tables. This goes for other tables that have this error and are conneted to a variety of other tables.

Deleteing and reseeding these tables would be a massive issue and would corrupt your DB emmensley . So instead you can restet the counter in the effected table to a higher number than the last row and start the whole process of again.

To do this follw these steps:

1.To find the maximum ID for the table with this error run this SQL query :

Select max(ID) from table

Where ID = primary Key

And Table = the name of the table with the error

For example for the console user table the primary key is: ConsoleUser_IDN  and the table is : ConsoleUser

Example query:

Select max(ConsoleUser_IDN) from ConsoleUser

This will return a very large number . Using this number run the following query to reset the counter and continue to use your DB

DBCC CHECKIDENT ("Table", reseed, x)

Table = the table with the error

X = The number from the abover query plus 10. !0 is used as a buffer so you can easily differentaite between the DB entries now and after you have  reseeded the table

The purpose of this article is to connect to a off core SQL Server without using LANDesk technology to ensure database connectivity. A connection will be created from the LDMS core server to the SQL server using Microsoft’s SQLCMD.exe tool. SQL activity monitor will be used to monitor the connection watching for the connection to drop. If the connection drops it can be concluded that there is an issue with network connectivity between SQL and the Core that will need to be resolved before further troubleshooting can be done.

Tools Needed

Microsoft SQL Server Command Line Query Utility SQL 2008

Microsoft SQL Server 2008 Command Line Utilities

The SQLCMD utility allows users to connect to, send Transact-SQL batches from, and output rowset information from SQL Server 7.0, SQL Server 2000, SQL Server 2005, and SQL Server 2008 instances. The bcp utility bulk copies data between an instance of Microsoft SQL Server 2008 and a data file in a user-specified format. The bcp utility can be used to import large numbers of new rows into SQL Server tables or to export data out of tables into data files.

Note:

This component requires both Windows Installer 4.5 and Microsoft SQL Server Native Client

Microsoft SQL Server 2008 Feature Pack, October 2008 link

Microsoft SQL Server 2008 Command Line Utilities

X86 Package(SqlCmdLnUtils.msi) - 7234 KB
X64 Package (SqlCmdLnUtils.msi) - 12212 KB
IA64 Package(SqlCmdLnUtils.msi) - 16515 KB

Microsoft SQL Server 2008 Native Client

X86 Package (sqlncli.msi) - 4549 KB
X64 Package (sqlncli.msi) - 7963 KB
IA64 Package (sqlncli.msi) - 11112 KB

Steps for testing

Core Side

1. Install SqlCmdln Utility on the core server.
2. Open a command prompt.
3. Change the directory to \Program Files\Microsoft SQL Server\100\Tools\Binn
4. Enter the following command string: sqlcmd.exe -S SQLServerName -d DatabaseName -U Username -P Password (example: sqlcmd.exe -S SQL005 -d LDDB -U sa -P Password1 )

If the connection is successful you will see a >1 on your screen.

For a full list of switches for SqlCmd refer to this MSDN article.

SQL Server Side

1. Open SQL Management Studio and connect to the SQL server in the Object Explorer window.
2. Expand the Management tree then open the activity monitor. Locate the connection opened by the SQLCMD application.

At this point you will want to view the activity monitor on the SQL server  to see if the connection has stayed up. Viewing the activity monitor at the end of the day or the next day will determine if there have been any disconects. SQL command line utility will not reconnect if there is a drop either by SQL or network. The application name(SQLCMD) is listed in application column of Activity Monitor so it is easy to identify the sqlcmd connection.

Problem: After using the SVCCFG (Configure Services) tool to change the database login password and rebooting the core, the console no longer allows login and shows the error message 'All required services have not started' and no authentication source is shown. This specifically affects SQL Express database installations.

Cause: SQL Express uses Dynamic Port assignment by default. Because AMP and LDMS 9 require static SQL ports, this information is not being captured by the setup tool correctly and the SQL Express port is not stamped into the SVCCFG tool. Once the SVCCFG tool restamps the new password, the SQL Express Port information is lost.

Resolution: Modify the SVCCFG tool information to include the correct port. To do this:

Determine the SQL Express TCP port being used via the SQL Configuration Manager tools on the core server. To do this:

1) Click Start--Programs--Microsoft SQL Server--Configuration Tools--SQL Server Configuration Manager.

2) Open SQL Server Network Configuration and click 'Protocols for LDMSDATA'

3) In the right hand pane, double-click TCP/IP, and go to the IP Addresses Tab

4) Scroll down and find the value for TCP Dynamic Ports. This is the port SQL Express is using.

5) Launch the SVCCFG.EXE tool from the ..\Landesk\ManagementSuite directory.

6) Where it shows the value for SERVER, add a comma and the port number.

Once this information has been changed, a reboot of the core server is required. After reboot, you should be able to successfully log in to the LDMS console. An engineering ticket, CR 42066 has been filed to track this issue.

Description:

Remote 32bit Console's can experience database connection problems because they are designed to connect to the default port 1433.

Usually in this scenario we recommend using an ODBC System DSN connection.  You can view the instructions for this option here:
http://community.landesk.com/support/docs/DOC-5876

There is an alternative that has worked in some environments and may simplify setup without having to setup an ODBC connection on every machine running the Remote 32bit Console.  It has NOT been fully tested in all environments but is an option to try.

 

On the Core Server modify the Database Server setting in Configure Services to connect to the Server using the following connection string format.

SERVERNAME\INSTANCE, PORT

 

Example:

Create the following indexes in your database to decrease load time on the scanned and detected vulnerabilities within the patch tool in the Management Suite Console:

--Microsoft SQL

CREATE NONCLUSTERED INDEX IDXVULNPATCH ON VULNERABILITY

(VULNERABILITY_IDN ASC,

VUL_ID ASC,

LANG ASC)

CREATE NONCLUSTERED INDEX IDXCOMPVULNPATCH ON COMPUTERVULNERABILITY

(VUL_ID ASC,

LANG ASC,

COMPUTER_IDN ASC,

DETECTED ASC,

PATCHINSTALLSUCCEEDED ASC)

--Oracle

--Note: change USER to the actual Schema user.

CREATE INDEX USER.IDXVULNPATCH on USER.VULNERABILITY VUL

(VUL.VULNERABILITY_IDN ASC, VUL.VUL_ID ASC, VUL.LANG ASC)

CREATE INDEX USER.IDXCOMPVULNP on USER.COMPUTERVULNERABILITY CVUL

(CVUL.VUL_ID ASC, CVUL.LANG ASC, CVUL.COMPUTER_IDN ASC, CVUL.DETECTED ASC, CVUL.PATCHINSTALLSUCCEEDED ASC)

Question:

What are the single sign-on options under Configure Services?

Answer:

     Single Sign-On allows users to login to the Win Console without requiring credentials to be entered. Below are the three options:

• None
  • This option requires you to enter a username and password when logging into the console
• Only
  • This passes and authenticates with the current Windows credentials.
• Mixed
  • This will allow you to either manually enter LDMS credentials or click login to pass the current Windows credentials

Cause

Resolution

Solution 1 - Bypassing the Proxy (Recommended)

1. Disable "Automatically detect settings" for the IE Proxy settings for the user configured for the LANDesk Com+ Application Identity and any other LANDesk user that may not be able to authenticate to the proxy.
   
   
2. Enable the proxy using the manual settings. 
   1. Check the box for "Use a proxy server for you LAN".
      
      
   2. Check the box for "Bypass proxy server for local addresses."
      
      
      
      
   3. Click Advanced.
      
      
   4. Add Exceptions for each of the following items:
      Core Server Name
      Core Server FQDN
      Core Server IP
      Localhost IP
      
      For example, the settings for a Core named vm88.mydomain.com with an IP of 10.1.1.1 would be:
      
      vm88; vm88.mydomain.com; 10.1.1.1; 127.0.0.1
      
      
      
      
   5. Click OK.
      
      
   6. Click Apply.
      
      
   7. Cick OK.

Solution 2 - Configuring the Proxy to Correctly Authenticate

LANDesk has no information on this other than that we are attempting to hit the following site and proxy authentication is failing:

https://CoreServer/landesk/managementsuite/core/ssl/information/databaseinformation.asmx

1. Change the Com+ Application Identity to a User That Can Authenticate on the Proxy.
   
   - OR -
   
   
2. Have the Administrator of the proxy server configure the Proxy to properly authenticate the user configured for the LANDesk Com+ Application Identity. If the administrator is unsure as to how to do this, then use Solution 1 - Bypass proxy server.