'Unable to read whether the user has edit rights' or 'Server Error in /Console Application' errors show in the 9.5 SLM Console.

Description:

- In the Dashboard and Products sections of SLM I never get any data.

- Attempting to Recalculate in Administration -> Calculations, you get an Error message stating "Unable to read whether user has edit rights".

- When opening a report, you get an error page stating "Server Error in '/Console' Application".

Cause:

STSCert and encryptioncert values in the Console and SamServer web.config files are missing

Resolution:

- Open\Edit the web.config file found at C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\managementsuite\sts

- Navigate to the bottom of that web.config file to find the two add key= lines under the <appSettings> section. They will look similar to the red highlighted lines listed below although your value= value will be different\unique for your environment :

     <add key="encryptionCert" value="ODBCMzUyN0RGMzM5RUNBNkFENjE4MEY1NUFDQjE5NThGOTg0REFCNg==" />

     <add key="STScert" value="ODBCMzUyN0RGMzM5RUNBNkFENjE4MEY1NUFDQjE5NThGOTg0REFCNg==" />

- Copy these two lines from this web.config file and add\save them to the <appSettings> section of the web.config files found in the following two locations:

      Drive:\Program Files (x86)\LANDesk\ManagementSuite\landesk\managementsuite\core\console\

and

      Drive:\Program Files (x86)\LANDesk\ManagementSuite\landesk\sam\samserver

- Reset IIS

- Verify pop-ups are allowed in the browser

- Verify Internet Explorer Enhanced Security Configuration is disabled

- Test the SLM Console components

- Clear the IE cache files if needed

If you still get the 'Unable to read whether the user has edit rights' after completing the steps above please refer to the steps below for additional troubleshooting:

Cause:

A .NET 3.x framework was installed after the .NET 4.0 framework. This causes the ASP.NET 4.0 components to no longer be registered correctly with IIS.

Resolution

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