Quantcast
Channel: Ivanti User Community : All Content - Console
Viewing all articles
Browse latest Browse all 607

Console Initialization error - Connection failed. The type initializer for "Computer" threw an exception

$
0
0

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.


Viewing all articles
Browse latest Browse all 607

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>