Hello,

I have one client that when launching Software Center gets "Loading Software Center returned error code 0x80041013." I have tried reinstalling the client, rebuilding the WMI repository (used both winmgmt /resetrepository and stop services renamed wbem\respository folder). The client is SCCM 2012 SP1 with CU1 (had the same problem before CU1 install, was hoping that would fix it). Anyone with any suggestions? This is one in 10 test clients that did it, but I am worried about pushing this to production clients.

Hi,

Change the local security policy settings to permit interactive log on for the ACT account. To determine the current settings, and to change the Log on as a batch job rights, follow these steps:

1. Under Administrative Tools, open Local Security Policy.
2. Click Local Policies, and then double-click User Rights Assignment.
3. Double-click Log on as a batch job, and then verify that ACTUser is selected in both columns. If ACTUser does not appear, click Add, and then add ACTUser to the list. Click OK.
4. If your server is a domain member, in Local Security Settings of the Microsoft Management Console (MMC), right-clickSecurity Settings, and then click Reload.
5. If ACTUser and is not selected in the Effective Policy Setting columns under the appropriate section, repeat steps 2 and 3.
6. Work with your domain administrators to modify your domain policies to allow your local policy settings to take effect.

Best Regards,

Mustafa Akcanca

1 in 10, ok then gather up a few of these 1's in 10's and see if they have common GPO settings that the other 8 out of 10 don't.

Hello,

I have one client that when launching Software Center gets "Loading Software Center returned error code 0x80041013." I have tried reinstalling the client, rebuilding the WMI repository (used both winmgmt /resetrepository and stop services renamed wbem\respository folder). The client is SCCM 2012 SP1 with CU1 (had the same problem before CU1 install, was hoping that would fix it). Anyone with any suggestions? This is one in 10 test clients that did it, but I am worried about pushing this to production clients.

Did you manage to fix this in the end Docworley?

We recently moved from SCCM 2010 to SCCM 2012.

This appeared on a couple of systems, one appeared to self repair after a few reboots but the other system still reported the same error.

Repaired WMI and deleted Group Policy history, but still the same error message.

Found the system still had files left over from the 2010 client. (Found in C:\Windows\SysWOW64\CCM)

We still had the old 2010 sc server running, so I copied the Client install folder over to a temp folder on the computer and ran ccmsetup /uninstall.

Once the ccmsetup finished, verified that only Inventory and cache folders existed in the SYSWOW64\CCM folder.

Then ran the SCCM 2012 ccmrepair program from c:\windows\CCM.

The Software Center now opens without any errors.