Console is failing to open after upgrade to SP2

Version 15

    Description

    Console fails to open after upgrade to SP2. The web console may also fail to load. These are some of the potential symptoms.

     

    Console.exe.log shows:


    11/02/2010 09:29:26 INFO 1748:1 RollingLog : FormMain: Enter constructor

    11/02/2010 09:29:26 INFO 1748:1 RollingLog : Current language: ENU

    11/02/2010 09:29:26 INFO 1748:1 RollingLog : Using culture info: en-US

    11/02/2010 09:29:26 INFO 1748:1 RollingLog : FormMain: InitializeComponent

    11/02/2010 09:29:26 INFO 1748:Main Thread RollingLog : FormMain: Leave constructor

    11/02/2010 09:29:27 INFO 1748:Main Thread RollingLog : There is an error in XML document (2, 3).

    11/02/2010 09:29:33 INFO 1748:Main Thread RollingLog : Starting authentication

    11/02/2010 09:29:33 INFO 1748:Main Thread RollingLog : Initializing authentication source

    11/02/2010 09:29:34 INFO 1748:Main Thread RollingLog : Authentication source intialization complete(0 seconds)

    11/02/2010 09:29:34 INFO 1748:Main Thread RollingLog : Resolving rights for UserName

     

    Resolution:

    1) Download Streams.exe from Sysinternals.com

    - Open a command window and run "Streams.exe -s -d Driverletter:\Progra~1\landesk" (substitute the correct path to the LANDesk folder)

    - Open a command window and run "Streams.exe -s -d C:\inetpub"

    - Run streams against the SP2 media and reinstall SP2.

    2) Set the MBSDK  web service (MBSDKService) to ignore client certificates.

    A. Open IIS 7 on the core
    B. Expand Sites > Default Web Site
    C. Click on MBSDKService
    D. On the right hand side double click on SSL SETTINGS
    E. In the SSL SETTINGS window slect IGNORE under Client Certificates section.

    3) Ensure the MBSDK  web service is set to Integrated Windows authentication (and not anonymous access).

    4) Verify the user logging in to the console has been added to the LANDesk Management Suite group on the core.

    5) Validate the files on the core were successfully updated by SP2. If file permissions to LANDesk directories are too restrictive, the files may not have been updated.

    6) The ASP.net  temp folder must have the proper rights. Run this command:

    aspnet_regiis.exe –ga “Authenticated  Users”

    7) Add read, list, execute permissions for “Authenticated Users”  to the ldmain\landesk\MBSDKService folder.

    Add read, read & execute permissions for “Authenticated  Users” to ldmain\LANDesk.DataServices.Schema.dll,  ldmain\LANDesk.DataServices.Database.dll, ldmain\directorymanager.business.dll, and ldmain\dirmanapi.dll.

     

    8) Add a new Active Directory source if there is not one that starts with "LDAP." The AD source should be in the User management tool:

     

    LDAP_Configure.JPG

    9) The defaul web site should be set to use the core server certificate.

    -In IIS 6, right click the default web site, properties, Directory Security, ensure "View Certificate" is available. If not, click on Server Certificate... and assign the core certificate.

    -In IIS 7, right click the default web site, Edit Bindings..., highlight https, click Edit..., if an SSL certificate is not selected, select it and click OK.

    10) In the METASYSTEMS table in the LANDesk Management Suite database, verify that your username and password are set correctly under the CONNECTINFO column.

    11) You may also see the following error:  Console Initialization Error: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://landesk.com/MBSDKService/MBSDK/WhoAmI.

    -Check the versions of the .DLL files in C:\Program Files\landesk\managementsuite\landesk\mbsdkservice\bin and check with support to make sure you have the correct versions.

     

    Login error in console with Oracle database see the following article:

    http://community.landesk.com/support/docs/DOC-21848