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:

regsvr32.exe "C:\program files\common files\system\ado\msado15.dll"

cd \windows\system32

dir atl*.dll

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

regsvr32.exe "%LDMS_HOME%parser.dll"

regsvr32.exe "%LDMS_HOME%ldcache.dll"

regsvr32.exe "%LDMS_HOME%msinterp2.dll"

regsvr32.exe "%LDMS_HOME%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.

Description:

What happens when I right-click a machine in the inventory and select Wake on Wan?

First make sure that you have the red circle in front of the machine to have the option Wake up availble to you.

Core server sends a ##LD_WAKE_ON_WAN## Message to a MDR which in turn send the Magic Packet on port 0 to the machine you want to wake up.

The protocol used is WOL.

In the below wireshark trace

192.168.1.217 ->Core

192.168.1.201 -> MDR

You do not need to have a static MDR.

Purpose:

Network Mapping is designed to help you understand your companies network. This may or may not be an accurate representation of your environment but will help you determine what is on the network and the bandwidth.

**Note**

THIS IS A NEW FEATURE AND ASK THAT ALL FEEDBACK IS SENT TO SUPPORT TO HELP BUILD A BETTER MAPPING TOOL.

This is using our multicast system and some Access points have Access Point Isolation (AP Isolation)

Prerequisites:

• This is only available on 2018.1
• CSEP is enabled on he subnet (will be covered in the process portion)
• At least one 2018.1 agent on the subnet

Process:

Agent Settings

By default the agent settings for network mapping are turned on. There is not much here other than:

• changing the Route Target- This will send the route info from the client to the target to the core. This could be the core or any other device on the network.
• Frequency- This is how often the route occurs

CSEP

Under the Self-electing subnet services choose the network mapping and in the subnet trees to the right, right click on a subnet and enable.

Network Map

The map will show different layouts based on the traceroute

You will see different colors for the line and this shows the response time of the ping. Green is good response time, yellow is some latency and red is big latency.

Lastly you will be able to drill down and have ability to RC, review provisioning and looking at inventory. You will also see the type of OS for that machine and it's ip.

This network map uses multicast to determine the Rep for the subnet but that rep will perform the traceroute. This route is for the subnet and devices the core knows about within that subnet will be added to the map. This will not tell you devices that are not managed but are in that subnet. This is designed to show you what your network looks like for the devices managed by you the Ivanti admin; this will include agentless scanned devices. The drill down is real time but the latency check is done during the route check which is 7 days by default as you saw but can be changed. This means the map will change as often as your end-users moving around from wired to wireless and vice versa.

Description

After SP2 has been installed on the LDMS 9.0 core server, the following error appears when you try to log into the console on the core server

You have insufficient rights to launch the console. Validate that you have been assigned a role or that you belong to a group that has been assigned a role.

Cause

The reason why the above error occurs is that the tables that should  contain LANDesk rights are empty. Therefore there is no association  between users and their LANDesk rights. This problem is caused partly  due to SQL server using dynamic port rather than its default port 1433  and partly by the application CreateLANDeskRights.exe not being able to  connect to the SQL server on dynamic port. During SP2 installation  CreateLANDeskRights.exe will run and populate the following tables with  LANDesk rights

- Permission

- PermissionDefinition

- PermissionDefinitionRight

- PermissionGroup

- PermissionRight

Resolution

To resolve this issue please follow below steps

1. Open LANDesk Configure Services from Start > All Programs > LANDesk > LANDesk Configure Services

2. On the General tab enter the SQL server or instance port ( SQL_Server, port_number ), i.e. LDMS9ENU, 2594

3. Click Apply and OK

Following the steps above you now should be able to log in as a user that is member of the following local security groups on the core server

- LANDesk Administrator

- LANDesk Management Suite

All the previous user settings such as rights, scopes and groups will have to be recreated.

Another cause for this error message could be the MBSDK web service is enabled with Anonymous access. It should be Windows Authentication only.

Description

"Object reference not set to an instance of an object" Error when clicking on tasks - all devices or failed devices in the console.

Applies to 9.0 SP2 cores.

Cause

A bug in the console code.

Resolution

apply the patch following the instructions in the Readme.txt.

Install the following LD90-SP2-MCP_SD-2011-0217 and LD90-SP2-MCP_CONS-2011-0217(the console is needed with the SD patch)

LANDESK Management Suite 9.0 Monthly Component Patches (pre SP3 only)

Problem

"Invalid Product License"

"The LANDESK product license you're using to access Ivanti Web Management Console is invalid."

Cause

Com+ objects stopped

Core server not activated or hasn't been activated since renewing licenses

Information is cached in temporary files.

Solution

Verify if you can login to the core console first. If you can login, continue on. If you get a licensing error when logging in, try activating the core server first.

Start the COM+ objects

The COM+ objects are used to access certain information within the database. If either of the COM+ objects (LANDesk, LANDesk1) stops running, you can run into issues with remote control, software distribution, provisioning, and webconsole. Basically, if it needs to pull information from the database through IIS, it will fail unless both LANDesk and LANDesk1 are running.

1. Click on your start menu and type Component Services
2. Click through to Computers>My Computer>COM+ Applications
3. Right click each of the LANDesk COM+ applications and choose start

If you get any errors while starting the COM+ objects, please rebuild them: How to rebuild the LANDesk COM+ Objects

Activate the Core Server

Click on your start menu and type Core Server Activation

1. Enter your entitlement credentials
   • This was sent to your company contact when you purchased the product. If you don't know your credentials, reach out to support.
2. Click Activate

The following documents will be helpful if you run into activation errors:

Issue: Unable to Build Core Server Activation File

Troubleshooting Core Server Activation

Clear Windows and .Net Temporary Files on the Core Server

1. Go to Windows\temp
2. Delete as many files as the system will let you.
3. Run IISRESET -STOP in an admin command prompt
4. Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
5. Delete all the files in here. If any are held open by a process, run step 3 again.
6. Run IISRESET in an admin command prompt

Issue:

As seen when you attempt to login to the console (local or remote)

Console Initialization Error:  System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.IO.FileNotFoundException: 
Could not load file or assembly 'AmpLicensingProxy, Version=3.0.1.72, Culture=neutral, PublicKeyToken=null' or one of its dependencies. 
The system cannot find the file specified. 
File name: 'AmpLicensingProxy, Version=3.0.1.72, Culture=neutral, PublicKeyToken=null' at LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) 

WRN: Assembly binding logging is turned OFF. 
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. 
Note: There is some performance penalty associated with assembly bind failure logging. 
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. 

   --- End of inner exception stack trace ---.

The error on a German console.

Konsoleninitialisierungsfehler: System.Web.Services.Protocols.SoapException: Die Anforderung konnte vom Server nicht verarbeitet werden. ---> System.Data.OleDb.OleDbException: Invalid object name 'ConsoleUser'. bei LANDesk.ManagementSuite.MBSDK.MBSDK.GetRights(Boolean clearCache) --- Ende der internen Ausnahmestapelüberwachung ---.

More Info:

The error message seem to indicate that a file [AmpLicensingProxy] could not be loaded.While this is technically true, it is not specific to AmpLicensingProxy.

Cause:

This is caused by the MBSDK not having the access it needs.  Since a variety of issues can interfer with the MBSDK, a variety of solutions exist.

Solutions:

One or more of these *may* work for you.  All are not required.

• add the local "NETWORK SERVICE" user to "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" and "install:\Program Files (x86)\LANDesk\ManagementSuite" with FULL CONTROL
• If you have the database on a seperate SQL instance, be sure "hostname\instance_name" is set as the database server name
• Clear the temporary ASP.NET files.
• reboot the SQL server followed by the core server

Purpose:

Network Mapping is designed to help you understand your companies network. This may or may not be an accurate representation of your environment but will help you determine what is on the network and the bandwidth.

**Note**

THIS IS A NEW FEATURE AND ASK THAT ALL FEEDBACK IS SENT TO SUPPORT TO HELP BUILD A BETTER MAPPING TOOL.

This is using our multicast system and some Access points have Access Point Isolation (AP Isolation)

Prerequisites:

• This is only available on 2018.1
• CSEP is enabled on he subnet (will be covered in the process portion)
• At least one 2018.1 agent on the subnet

Process:

Agent Settings

By default the agent settings for network mapping are turned on. There is not much here other than:

• changing the Route Target- This will send the route info from the client to the target to the core. This could be the core or any other device on the network.
• Frequency- This is how often the route occurs

CSEP

Under the Self-electing subnet services choose the network mapping and in the subnet trees to the right, right click on a subnet and enable.

Network Map

The map will show different layouts based on the traceroute

You will see different colors for the line and this shows the response time of the ping. Green is good response time, yellow is some latency and red is big latency.

Lastly you will be able to drill down and have ability to RC, review provisioning and looking at inventory. You will also see the type of OS for that machine and it's ip.

This network map uses multicast to determine the Rep for the subnet but that rep will perform the traceroute. This route is for the subnet and devices the core knows about within that subnet will be added to the map. This will not tell you devices that are not managed but are in that subnet. This is designed to show you what your network looks like for the devices managed by you the Ivanti admin; this will include agentless scanned devices. The drill down is real time but the latency check is done during the route check which is 7 days by default as you saw but can be changed. This means the map will change as often as your end-users moving around from wired to wireless and vice versa.

DISCLAIMER

The following article contains information that may permanently delete information from the database.

It is CRITICAL that you have a full backup of your database prior to making any modifications to the database.

Failure to backup your database may result in permanent loss of some, or even all data.

How To:

When directed by Ivanti support, use this document to move all of the objects that a user account owns to another account, then back to the original account. These steps have been proven to resolve odd account issues (Possibly caused by updating the software, issues when changing LDAP servers, or other unknown causes). Once that is done you can delete the old account from the database, add the old account back, and then reassign all of the objects back to that user (Queries, scheduled tasks, provisioning templates, software packages etc).

Step by Step:

1) Backup the database if you have not already.

2) Create a local user account (Give that user a name like "TestUser") on the Core Server and add them to the "LANDesk Management Suite Administrators group".

3) You will want to verify that you can log in as the "TestUser" and that they have administrator rights in the Ivanti Console.

4) Stay logged in as the "TestUser" and then delete the user account that is having issues. Select the checkbox "Assign Objects to the Following User or Team" and select the "TestUser" account.

5) Refresh the console and verify that the bad account is gone from the console.

6) If the account is now gone, re-add it back into User Management and assign the account the proper rights/scopes that it should have.

7) Log out of the console and verify that the re-added account can successfully log into the console.

8) Log into the console with an admin user (If you are not already)

9) Delete the "TestUser" account and assign all of the objects back to the original account.

10) Verify that all of your objects are back onto the account.

What is Wake on LAN?

Wake on LAN is a technology whereby a magic packet is sent to a client that is powered off.  If a network card detects a magic packet directed to its MAC address, the computer will power on.  Both the motherboard and network card must support Wake on LAN.  Wake on LAN must be enabled in the BIOS.

How does LANDesk send a Wake on LAN magic packet?

LANDesk can send a Wake on LAN magic packet in one of three ways:

1. In the Delivery Method, configure the Multicast Domain Representative to send the Wake on LAN magic packet.

2. When creating a Scheduled Task, check the Wake on LAN option. 
    
   Note:

   Checking this option when the Delivery Method has the MDR sending the magic packet can result in the WOL packet not being sent at all.

3. In the Console, right click on a device in the Network View and choose Wake on LAN.
    
   Note for options 2 and 3:

   This packet is sent from the computer running the Console.  If the console is open on the Core Server, the Core Server sends the packet.  If a Remote Console is open on a client machine, the magic packet is sent from that client machine running the Remote Console.  If these machines are on different subnets, different results may occur based on network settings.

Is the Wake on LAN magic packet a TCP or UDP packet? Is it unicast or broadcast?

The magic packet is a UDP broadcast packet.  Because the device is off, it does not have an IP Address therefore the magic packet must be broadcast packet.  Also, since the device is off, it cannot give a proper response to a TCP packet, therefore the magic packet must be UDP.  If the packet is crossing networks or subnets, it is a directed broadcast packet.  Note that routers are usually configured to drop directed broadcast packets.

What port does LANDesk use to send the Wake on LAN magic Packet?*

By default LANDesk uses UDP port 0.  This can be configured on the Core Server by going to Configure &gt; Services &gt; Scheduler.  The LANDesk Console must be restarted for this change to take affect.

 
Note:

The MDR always sends using port 0.  In previous version, this cannot be configured.  In 8.7 SP5 and 8.8 or later version, This can be configured by setting the following registry key and restarting the Targeted Multicast service on the MDR.

HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\LDWM\Distribution\Multicast
Type: DWORD
Name: WOL Port

 
Note:

The web console will always send the magic packet from the core on port 0.

What issues may prevent devices from receiving a Wake on LAN magic packet?

1. If crossing subnets, routers are usually configured to drop directed broadcast packets. 

2. LANDesk uses port 0 for the magic packet by default.  Many firewalls may block this port.  This port is configurable on the Core Server but not on the MDR. 

3. The packet may be arriving but the network card or motherboard may not support Wake on LAN; or Wake on LAN is not enabled in the BIOS.

Why does a device wake up from a Remote Console but not from the Console on the Core Server?

This packet is sent from the computer running the Console.  If the console is open on the Core Server, the Core Server sends the packet.  If a Remote Console is open on a client machine, the magic packet is sent from that client machine running the Remote Console.  If these machines are on different subnets, different results may occur based on network settings.

After changing the Wake on LAN port under Configure &gt; Services &gt; Scheduler, the change does not appear to have occurred.  What could be the problem?

The problem could be two things:

1. If sending the Wake on LAN packet from the console, the console must be restarted for this change to occur.

2. This change does not modify the Wake on LAN port on the Multicast Domain Representative.  The Wake on LAN port on the MDR is not configurable and will always be set to 0.

If network devices such as routers and switches are blocking directed broadcast and not a single machine on a particular subnet is powered on, will Wake on LAN work?

If Wake on LAN magic packets cannot cross subnets, then at least one workstation must be available and running the LANDesk Agent with the Targeted Multicast feature.

Description

What happens when I right-click a machine in the inventory and select Wake on Wan?

First, make sure that you have the red circle in front of the machine to have the option Wake up available to you.

Core server sends a ##LD_WAKE_ON_WAN## Message to an MDR which in turn send the Magic Packet on port 0 to the machine you want to wake up.

The protocol used is WOL.

In the below Wireshark trace

192.168.1.217 ->Core

192.168.1.201 -> MDR

You do not need to have a static MDR.

Agent version 2018.1 for Windows Configuration does not not have the option Real-time Inventory and Monitoring

CAUSE: Activation credentials used to activate the Ivanti Endpoint Manager ( EPM ) version 2018.x does not contain the license for the EPM version 2018.x

Note: Management Console on the EPM 2018.x Core Server > Configure > Product Licensing... shows Product Name: Ivanti Endpoint Manager powered by Landesk Version: 10.1 where version 10.x is the version for the EPM version 2017.x, whereas EPM version 2018.x is and should be version 11

RESOLUTION: Contact Ivanti's technical support or your Account Manager and request to have the license for the Ivanti Endpoint Manager ( EPM ) version 2018.x to your Core Server activation credentials. Then activate / reactivate your EPM 2018.x Core Server and verify within the Management Console on the EPM 2018.x Core Server > Configure > Product Licensing... that the Product Name: Ivanti Endpoint Manager powered by Landesk shows Version: 11.0

From within the Management Console on the EPM 2018.x Core Server verify that the Agent Configuration now has the option Real-time Inventory and Monitoring available within the Agent for Windows.

Ivanti's Licensing Portal https://portal.ivanti.com can also be used to check the licensing.

Description

Real-time Inventory and Monitoring enables you to retrieve current real-time information from your client machines such as CPU, memory and network usage. Real-time Inventory is also used by Inspector to display information. Inspector requires both the Baseline Components as well as the Extended Components.

Note: If baseline and extended components are not enabled you will see the following state notifications when attempting to use the Inspector: Real time inventory and monitoring not configured on the device or Unable to contact the device.

Enabling Real-Time Inventory and Monitoring

From the console navigate to Tools > Configuration > Agent Configuration. Double click the agent configuration that you want to enable real-time inventory and monitoring on. Within the agent configuration 'Start' screen check the option for Baseline Components as well as Extended Components option under Real-time Inventory and Monitoring. Save the agent configuration. Deploy the agent configuration to your client machines.

Additional information on agent deployment can be found here: Ivanti Endpoint Manager and Endpoint Security - Agent Deployment Landing Page.

Problem:

Description

When attempting to launch LANDesk Management Suite you are presented with the error ‘Console Initialization Error: Error calling ParseLocalConnectionString Parameter name: local_conection_string’.

Resolution 1

1. On the core server open the Internet Information Services (IIS) Manager. This can be accessed by navigating to the Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Alternately you can type in ‘inetmgr’ into the Start Search box and press Enter.

2. Within the IIS Manager application navigate to the \[core server name]\Sites\Default Web Site\landesk\managementsuite\core\ssl\information folder.

3. In the middle pane double click on the ‘Authentication’ option within the IIS area as depicted in the screenshot below:

4. Please ensure the Authentication settings are set as follows:

Note: These are the default settings that are input into IIS upon installation of LANDesk Management Suite and are the suggested settings for IIS.

5. Launch LANDesk Management Suite and attempt to login.

Resolution 2

1. On the core server open the Internet Information Services (IIS) Manager. This can be accessed by navigating to the Control Panel > Administrative Tools > Internet Information Services (IIS) Manager. Alternately you can type in ‘inetmgr’ into the Start Search box and press Enter.

2. Within the IIS Manager application navigate to the \[core server name]

3. Open ISAPI and CGI Restrictions

4. Make sure that both ASP.NET v4.0 are allowed

5. Launch LANDesk Management Suite and attempt to login.

Resolution 3: 

CoreDButil  Tries to communicate over SSL V3,   if it is disabled.   Then you can also get the ParselocalConnectionString Parameter name: local_connection_string’ message
To check to see if SSL V3 is enabled Open regedit and browse to this location:
go to the Key HKLM\Currentcontrolset\control\securityproviders\schannel\protocols\SSL 3.0\Server    Also check the client sections to make sure that,  "Disable by default is not set to 1.
If you see SSL V3 is disabled  Dword = 1 change it to a "0".   You will need to restart the system after Making this change.

Note: If you are experiencing the ‘Error: Exception! Error calling ParseLocalConnectionString Parameter name: local_connection_string’ message during an installation or upgrade, please visit the following community article for additional information and a fix for this issue. Core Install Fails at Configuring Datamart Step

Symptoms: The following error is displayed when

1. Launching a remote console and attempting to connect to a core server.

2. Installation during Configuring Datamart.

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 set to True.

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

See the help file for your version of Management Suite / Endpoint Manager for the latest information on this subject.

Environment

LANDESK Management Suite 9.5 and later

Problem

You are unable to generate a DELL OMCI BIOS package from the Tools > DELL OMCI console

The Console.exe.log reports error messages such as:

Exception during StringFormat: Input string was not in a correct format.

Cause

The Dell OMCI features, available in the LANDESK Management Suite 9.0, are no longer supported in version 9.5.

Environment

LANDesk Management Suite 9.50.0.530, Windows Server 2008R2 SP1 Standard Edition

Problem/Issue/Symptoms

LDMS Console fails to initialize after renaming the core server machine, reporting the following pop-up window error:

The error reported in the console log is the following:
Exception Details: </b>System.ArgumentNullException: Error calling ParseLocalConnectionString<br>Parameter name: local_connection_string<br><br>

In this scenario, opening  the "LANDesk configure services" from Start > All Programs > LANDesk > LANDesk Configure Services fails to start, reporting a pop up window error.

Where W2008R2SP1ENG is the previous machine name, and W2008R2SP1NEW is the new one.

Cause

This problem occur after changing the hostname of the core server.
It is strongly recommended not to change the hostname of the core, especially in a production environment.

Solution

Locate the previous machine name lingering in the LANDesk registry keys

- Open the registry editor

- Find the previous machine version

- Replace it with the current one

The following keys are the three basic to change to have the console running again, but more are stored in the registry, that's why it's not recommended to change the hostname of the core server.

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite]

"CoreServer"="previous machine name"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\DBUtil]

"Inventory Server Name"="previous machine name"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Setup]

"CoreServer"="W2008R2SP1ENG"

Error

When opening the Console, after entering your credentials and trying to login, you receive the error:

Console Initialization Error: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.

The request failed with the error message:

--

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>IIS 7.5 Detailed Error - 500.19 - Internal Server Error</title>

<style type="text/css">

<!--

body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;}

code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}

.config_source code{font-size:.8em;color:#000000;}

pre{margin:0;font-size:1.4em;word-wrap:break-word;}

ul,ol{margin:10px 0 10px 40px;}

ul.first,ol.first{margin-top:5px;}

fieldset{padding:0 15px 10px 15px;}

.summary-container fieldset{padding-bottom:5px;margin-top:4px;}

legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}

legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px;

border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696;

border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;font-size:1em;}

a:link,a:visited{color:#007EFF;font-weight:bold;}

a:hover{text-decoration:none;}

h1{font-size:2.4em;margin:0;color:#FFF;}

h2{font-size:1.7em;margin:0;color:#CC0000;}

h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;}

h4{font-size:1.2em;margin:10px 0 5px 0;

}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif;

color:#FFF;background-color:#5C87B2;

}#content{margin:0 0 0 2%;position:relative;}

.summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}

.config_source{background:#fff5c4;}

.content-container p{margin:0 0 10px 0;

}#details-left{width:35%;float:left;margin-right:2%;

}#details-right{width:63%;float:left;overflow:hidden;

}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF;

background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal;

font-size:1em;color:#FFF;text-align:right;

}#server_version p{margin:5px 0;}

table{margin:4px 0 4px 0;width:100%;border:none;}

td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:bold;border:none;}

th{width:30%;text-align:right;padding-right:2%;font-weight:normal;}

thead th{background-color:#ebebeb;width:25%;

}#details-right th{width:20%;}

table tr.alt td,table tr.alt th{background-color:#ebebeb;}

.highlight-code{color:#CC0000;font-weight:bold;font-style:italic;}

.clear{clear:both;}

.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;}

-->

</style>

</head>

<body>

<div id="header"><h1>Server Error</h1></div>

<div id="server_version"><p>Internet Information Services 7.5</p></div>

<div id="content">

<div class="content-container">

<fieldset><legend>Error Summary</legend>

<h2>HTTP Error 500.19 - Internal Server Error</h2>

<h3>The requested page cannot be accessed because the related configuration data for the page is invalid.</h3>

</fieldset>

</div>

<div class="content-container">

<fieldset><legend>Detailed Error Information</legend>

<div id="details-left">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Module</th><td>IIS Web Core</td></tr>

<tr><th>Notification</th><td>BeginRequest</td></tr>

<tr class="alt"><th>Handler</th><td>Not yet determined</td></tr>

<tr><th>Error Code</th><td>0x800700b7</td></tr>

<tr class="alt"><th>Config Error</th><td>There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined

</td></tr>

<tr><th>Config File</th><td>\\?\C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\web.config</td></tr>

</table>

</div>

<div id="details-right">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Requested URL</th><td>https://landesk95:443/mbsdkservice/msgsdk.asmx</td></tr>

<tr><th>Physical Path</th><td>C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\msgsdk.asmx</td></tr>

<tr class="alt"><th>Logon Method</th><td>Not yet determined</td></tr>

<tr><th>Logon User</th><td>Not yet determined</td></tr>

</table>

<div class="clear"></div>

</div>

</fieldset>

</div>

<div class="config_source content-container">

<fieldset>

<legend>Config Source</legend>

<pre><code> 5: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

<span class="highlight-code"> 6: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/></span>

7: <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

</code></pre>

</fieldset>

</div>

<div class="content-container">

<fieldset><legend>Links and More Information</legend>

This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=500,19,0x800700b7,7601">View more information »</a></p>

</fieldset>

</div>

</div>

</body>

</html>

The same error will also show in the Console.exe.log file

Reason

Opening a Console calls several webservices which are configured by a web.config file. In this file are several .Net Framework sections defined. LANDesk uses mainly .Net Framework 2.0, so sections that aren't defined in the main .Net Framework 2.0 configuration, the machine.config, need to be defined in the web.config.

However, all LANDesk webservices are run in an IIS Application Pool. This pool is configured to run with a specific .Net Framework version. If the application pool is somehow re-configured to use a higher .Net Framework version, it can be that the sections in the web.config are already defined in the main machine.config file for that .Net Framework version, resulting in the config error a duplicate section is defined.

This can be caused by .Net Framework updates or errors in the (un-)install of LANDesk software and updates.

Resolution

Look in the complete error message for the URL and the web.config file that are being logged as containing a duplicate section. In the above error:

<tr><th>Config File</th><td>\\?\C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\web.config</td></tr>

</table>

</div>

<div id="details-right">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Requested URL</th><td>https://landesk95:443/mbsdkservice/msgsdk.asmx</td></tr>

Open the Internet Information Services Manager on your Core Server, and find the specified URL/Webservice (in the example MBSDKSERVICE). Right Click on this the Webservice - Manage Application - Advanced Settings. Note the Application Pool the webservice is running in.

In the same IIS Manager, open the Application Pools, find the pool noted before, righ click on it and open Basic Settings. Change the .Net Framework version to 2.0. Restart the Application Pool.