ConfigMgr 2012 SP1 Admin Console will not connect to site system

Problem Description:

Configuration Manager 2012 SP1 Admin Console will not connect to site system.  In SmsAdminUI.log you find the following:

 The performance counter ‘# <counter name>’ was not found

Cause:

The Performance Counter Store has become corrupted.

Resolution:

On the host you are trying to install the Admin Console on, perform the following steps:

1. Uninstall the admin console
2. Launch Command Prompt as administrator
3. Enter the command: LODCTR /R
4. Install the admin console.

Client Fails to Create Certificate

Problem Description:

Configuration Manager 2012 client does not create a Client certificate

CertificateMaintenance.log shows the following entries:

Crypt acquire context failed with 0x8009000f.
CCMDoCertificateMaintenance() failed (0x8009000f). Raising pending event: instance of CCM_ServiceHost_CertificateOperationsFailure {DateTime = “20130730192131.135000+000”; HRESULT = “0x8009000f”; ProcessID = 6024; ThreadID = 5512; };
CCMDoCertificateMaintenance() raised CCM_ServiceHost_CertificateOperationsFailure status event.

 

Cause:

Permissions are not correct on the 19c5cf key located in C:\Users\All Users\Microsoft\Crypto\RSA\MachineKey

Resolution:

On the management point server you perform the following steps

1. Open Windows Explorer and navigate to C:\Users\All Users\Microsoft\Crypto\RSA\MachineKey
2. Change security settings on the 19c5cf key to include local administrators
3. Restart the SMS Agent Host service
4. Verify that your client has created a self-signed certificate

MP Control Manager detected MP is not responding to HTTP requests. The http error is 12029.

Problem Description:

SMS_MP_CONTROL_MANAGER reports the following error:

MP Control Manager detected MP is not responding to HTTP requests.  The http error is 12029.

Checking the mpcontrol.log you find the following entries:

Failed to send http request /SMS_MP/.sms_aut?MPLIST. Error 12029
Call to HttpSendRequestSync failed for port 8080 with 12029 error code.

Cause:

IIS does not have an entry for the custom port of 8080.

Resolution:

On the management point server you perform the following steps

1. Open IIS Manager
2. Expand your server
3. Expand Sites
4. Select Default Web Site and click Bindings…
5. Click Add
6. Add the custom port information, and click Ok.
   
7. Click Close
   
8. Monitor mpcontrol.log until you see the following entry:
   Call to HttpSendRequestSync succeeded for port 8080 with status code 200, text: OK

Configuration Manager Client Install Fails with Error 1603

Problem Description:

Installation of the SCCM 2012 client fails on target machine with the following generic error.

File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action:
ErrorMessages:

Cause:

This is a generic failure message and can have many possible solutions.  In my case I had to register atl.dll for the MSI installation to complete.

Resolution:

1. Run ccmsetup /uninstall to remove the client
2. At the command prompt type: regsvr32 atl.dll and press enter.
3. restart client installation

Cannot Connect to the Application Server

Problem Description:

When trying to connect to the Configuration Manager 2012 Application Catalog website you receive the error message:  Cannot connect to the application server.  The website cannot communicate with the server.  This might be a temporary problem. Try again later to see if the problem has been corrected.  If this problem continues, contact your help desk.

Cause:

There are a number of causes for this error, however, in this case the issue was the the wrong SSL Certificate was set in the Default Site Bindings.

Resolution:

Change the SSL Binding on port 443.

1. On the server hosting the Application Catalog roles, open IIS Manager
2. Expand Sites
3. Select Default Web Site
   
   
4. Select Bindings
   
   
5. Select HTTPS port 443 and click Edit
   
   
6. Under SSL Certificate, change the drop down to your ConfigMgr SQL Server Identification Certificate and click OK.
   
7. Click Close
8. Refresh you browser and you should now be able to connect to the Application Catalog.

Data Warehouse Registration Fails

Problem Description:

Data warehouse registration fails with a generic error message. No errors are logged in the event log, the data warehouse test connection succeeds, but the registration still fails.

Cause:

The data warehouse registration wizard uses a PowerShell cmdlet to perform the registration of the data warehouse. By default, PowerShell execution policy prevents the execution of the registration cmdlet and results in the data warehouse registration failure.

Resolution:

To ensure that the PowerShell execution policy isn’t the issue here, perform the following steps on the machine where you are attempting the registration from.

1. On the computer where you are attempting the data warehouse registration from, on the Windows desktop, click Start >> All Programs >> Accessories >> Windows PowerShell >>  Windows PowerShell . Right-click Windows PowerShell, and click Run as administrator.
2. At the Windows PowerShell command prompt, type the following command, and then press ENTER:  Set-ExecutionPolicy RemoteSigned
3. Close the Service manager console, if already open.
4. Launch the console and attempt the data warehouse registration again.