Quantcast
Channel: LANDESK User Community : Document List - All Communities
Viewing all articles
Browse latest Browse all 6338

When starting SLM in 9.5 I receive the error 'The operation had an unknown failure'

$
0
0

Description:

When starting SLM in 9.5 I receive the error 'The operation had an unknown failure'

slm.PNG

 

 

Review the web.config file found in

C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\managementsuite\sts

Edit the file and goto the <appSettings> section at the bottom and review the two "add key= lines". If the two "add key= " entries match the values listed below then the web.config file needs to be corrected.

 

<appSettings>

<add key="encryptionCert" value="CN=test, OU=pc, O=Unspecified, L= Core Server, S=7DA9, C=NA" />

<add key="STScert" value="CN=test, OU=xxxx, O=Unspecified, L= Core Server, S=7DA9, C=NA" />

</appSettings>

 

To fix this problem do the following:

Open a command prompt on the core and run the following (NOTE-change the "Core Certificate Name" field to the certificate name used by the  core server - make sure to keep the quotation marks around the value)

 

"C:\Program Files (x86)\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe" "addstsandencryptionthumbprinttowebconfig" "Core Certificate Name" "CommonServices"

 

after that completes run the same command but change "CommonServices" to "STS"

 

Reset IIS then open the web.config file found at C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\managementsuite\sts and verify the add key= values under <appSettings> now has a value for both "encryptionCert" and "STScert"

The two add key= values should look something like this although the value= data will be different in your environment as it creates this from your core certificate.

 

<appSettings>

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

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

  </appSettings>

 

Open IIS, goto Default Web Site then the CommonServices and open "Application Settings" in Features View. You should see the same values as those listed under <appsettings> in the web.config file

Do this same review of the "Application Settings" for STS under the Default Web Site.

Do this same review of the "Application Settings" for Console under the Default Web Site. (The console Application Settings will have an additional cert listing called ReportsLicense)

 

Attempt to reopen the SLM console on the Core Console. If it fails, clear the Internet Explorer cache files, goto IIS > Application Pools and change the LDAppCommon pool identity to LocalSystem from NetworkService. Reset IIS and attempt to get into SLM again at the Core Console.

You should be able to get into the SLM console now.


Viewing all articles
Browse latest Browse all 6338

Trending Articles



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