Software Center not loading for most/all clients

PaulM 121 Reputation points
2020-10-06T17:55:09.217+00:00

We are on 2002 and have roughly 42,000 clients and we are seeing wide spread issues where Software Center will not load. It first launches with a blank white screen and after sitting for a while it will load the header and categories, but then has an error saying Software Center can not be loaded etc. We aren't sure when this started, but it seems to be happening to all clients. I'm not really sure where to begin troubleshooting this. I haven't found any errors in the client logs I've looked at so far.

Any help would be appreciated.

Microsoft Configuration Manager
0 comments
Accepted answer
  1. PaulM 121 Reputation points
    2020-10-09T17:19:22.873+00:00

    This ended up being a certificate issue. We are in the middle of transitioning our CA and we had both the old and new certs on the clients and the SCCM agent was picking the new cert even though the MP's were still using the old cert. The resolution was to go into the site properties and define a search criteria for the cert to make sure that the agent was choosing the correct client cert.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Fiona Yan-MSFT 2,311 Reputation points
    2020-10-07T06:03:54.99+00:00

    @PaulM
    Thank you for posting in Microsoft Q&A forum.

    I would suggest to take one of the computer and dive deep into testing and troubleshooting. Have we tried to disable some Anti-malware programs? Is the client computer waiting for any updates or a reboot?

    The following post describes a similar issue, I hope this is helpful to you:

    1. https://social.technet.microsoft.com/Forums/en-US/71841acb-822a-4e49-9b50-311e92799e5b/software-center-can-not-be-loaded?forum=ConfigMgrCBGeneral
    2. https://social.technet.microsoft.com/Forums/en-US/18edddff-79db-4670-8939-c87c3a9f8347/software-center-can-not-be-loaded?forum=ConfigMgrAppManagement

    Have a nice day!

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Sherry Kissinger 3,806 Reputation points
    2020-10-09T16:46:14.23+00:00

    We had similar issues; and the way to see if you are having the exact same (or similar) issue we were having, log files to look at:

    At the client, look at the users' SCClient_<someone>.log
    If in that log at or around the time of the user launching Software Center, does it say something like... "GetApplicationsAsync: The HTTP Request to.... has exceeded the alloted timeout of 00:01:00 ... Unable to fetch..."

    On your Management Point, look at "UserService.log"
    again, at or around the time of that user launching Software Center, is there a line similar to this:
    System.Data.SqlClient.SqlException: Execution Timeout Expired.
    which refers to this stored procedure: usp_GetApplicationPropertyValuesFiltered.

    If so, there are two things to do.

    1. If you are on the latest version of CM (2006) OPEN A CASE with Microsoft. Do not pass go, do not hesitate. Tell them you are having this issue, when asked, zip up all the log files when asked, and send them to Microsoft on that case.
    2. If you can't wait for them to fix it; one workaround--which is horrid, but it might work, is to change your Database Compatibility mode. For example, when we were having this issue, we were on SQL 2017, compat 130. If we changed it to Compatibility of 110, then that particular procedure finished quickly. Of course... that's not ideal. Because now we're missing out on any enhancements which a higher compat level would grant us.

    If you are still having this exact issue (with those exact errors in the two log files), then compat mode change should let you limp by. However, the real fix will be for Microsoft to either optimize that particular usp_ routine to work correctly with higher levels of sql; or change CM itself to call that particular usp_ routine with the HINT 110. (it's embedded in the code, we couldn't hack/change it).

    If you decide to just 'limp by' with compat mode 110 (and that works) and not open a case with MS--make sure you document what you did, why; etc. etc. for your company; let your team and boss' know what you are doing and why.

    Again... the above is only if you are seeing those exact errors in those log files. If you aren't, it's a different issue. But perhaps those log files will help you find clues to what is going on in your environment.

    0 comments