1 Reply Latest reply on Jul 28, 2015 9:13 AM by LANDave

    CLR20r3  error while console login





        Problem Signature 01: Console.exe


        Problem Signature 02:


        Problem Signature 03: 54198708


        Problem Signature 04: System.Web.Services


        Problem Signature 05: 4.0.30319.33440


        Problem Signature 06: 52006d37


        Problem Signature 07: 1a9


        Problem Signature 08: 42


        Problem Signature 09: System.InvalidOperationException


        OS Version: 6.3.9600.


        Locale ID: 1033


        Additional Information 1: c7cc


        Additional Information 2: c7ccfc58bd99a52b8a583c039502d40b


        Additional Information 3: 7237


        Additional Information 4: 7237b1560c7b589bc4d35624fbe48296

        • 1. Re: CLR20r3  error while console login
          LANDave SupportEmployee

          A few questions regarding this.


          Is this on the Core Server, remote console(s) or both?


          This error is possibly caused by a problem connecting to the SQL database.  Check connectivity to the database.  Also ensure the credentials to connect to the Database correct.


          On the core server in the LANDESK program files group you should have a "Configure Services" option.   Or just search for "Configure Services".   On the general tab it should show Database connection information.


          I would check the console.exe.log in the ManagementSuite\log folder to see if there are any additional details.


          In addition an entry in the system event logs (Check Event Viewer) may help in this instance.


          It also may center around the .NET Framework and issue with it.   Make sure that you have a supported version installed.  At this time we only support up to .NET 4.5 I believe.



          Another possible solution:


          For the computer running the console check the local user policy here:


          Local User Policy \ Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ Security Options – System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing – Disable



          If this was working before and is now not working, what changed?  Was a new LANDESK patch installed, were new Microsoft patches installed?


          If all else fails, consider contacting LANDESK Support and opening a support case:

          How to contact LANDesk Customer Support: