Are this new installs? If you open SC before all pols are downloaded, the client will generate errors and not open SC. I have it on my notes the correct error.
Check ccm\temp folder. Cesar A. Meaning is NOT in words, but inside people! Dr. Myles Munroe. > On Jun 11, 2015, at 12:25 PM, Boseman, Marcia H - Raleigh, NC > <[email protected]> wrote: > > > > > > > > > We have seen the error above on two systems when opening software center. > In checking online I have seen that the error displays because the SCCM > client service has not fully started. In checking the service for the SCCM > client agent is set to automatic and delayed. However, in the case on one > machine even after setting the service to automatic, we still got the error. > I found the following on line and checked the registry keys and the > information was listed correctly in the registry. > > SCCM 2012 Software Center returned error code 0x0041013 (-2147217389) > After an update from SCCM 2007 client to SCCM 2012 client, there is sometimes > show the error "Loading Software Center returned error code 0x80041013 > (-2147217389)." in Software Center. This even though the client was > successfully installed. > > I think this error is because not all parts of the old SCCM clients have been > properly removed. > > You can fix this issue with the following steps: > 1. Open registry > 2. Go to > HKEY_CLASSES_ROOT\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 > 3. Check the value for Default is C:\WINDOWS\CCM\ccmcisdk.dll (if not, > change the value) > 4. Go to > HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 > 5. Delete the value in Default (value is > C:\Windows\SysWOW64\CCM\dcmsdk.dll) > You can launch the software center again and you can see the applications > without the error message. > > > What finally got Software Center to display correctly was to remove the > > 1. Go to > HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 > 2. Delete the value in Default (value is > C:\Windows\SysWOW64\CCM\dcmsdk.dll) > Can you provide some clarification as to why this happening or the proper > steps to take care of this issue? The client logs look fine. > >
