Category: Critical thinking
Well oke, the RAP (Run Advertised Program) is gone in ConfigMgr 2012, and we got the Software Center in return. Nice but now what?
For Advertised Programs we now have the: Application Catalog!
The Application Catalog is a web-site where a user can find his/her software. For an administrator it is also possible to authorize software, the user asks if the software can be deployed to his/her workstation. This might come in handy when licensing is an issue, or when a manager wants to be able to monitor application installations.
Oke nice, but how do we set this up.
Because ConfigMgr 2012 relies on .NET and uses WCF (Windows Communication Foundation) we need to install the HTTP Activation feature from the WCF Activation:
HTTP Activation feature
If this is not done it will result in following error:
There is a problem connecting with the server.
The Web site cannot communicate with the server. This may be a temporary problem. Click retry action to submit your request again. If this problem continues, try again later.
Error with Software Catalog
Then we have to install the Application Catalog Web Service Point and Application Catalog Web Site Point role on a SCCM site server.
Application Catalog site roles
We will use HTTP for Client connections and port 80 for site traffic.
Application Catalog setup
Application Catalog WebSite Setup
Servers and Site System Roles
Now we got the Application Catalog Website up and running!
Application Catalog Website
Still empty, but we will fill this up next time!
I have the following critical situation:
1. With in the Site Status the Site System Role "Management Point" status is Critical. If I start the Configuration Manager Service Manager and query the SMS_MP_Control_Manager, it shows that it is stopped, when I start it, i get the above error immediately in the event log.
Event Log error:
component SMS_MP_CONTROL_MANAGER on computer SCCM-PRI.domain.com reported: SMS Executive detected that this component stopped unexpectedly.
Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly.
Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.
2. On Client machines, I see lots of event 6006 warnings, Source: Wlclntfy
The winlogon notification subscriber <Profiles> took 129 second(s) to handle the notification event (Logon).
Event ID: 63, source: WinMgmt
The description for Event ID ( 63 ) in Source ( WinMgmt ) could not be found. It contains the following insertion string(s): PolicyAgentInstanceProvider, root\CCM\Policy\S_1_1_0.
The description for Event ID ( 63 ) in Source ( WinMgmt ) could not be found. It contains the following insertion string(s): PolicyAgentInstanceProvider, root\ccm\Policy\Machine.
The description for Event ID ( 63 ) in Source ( WinMgmt ) could not be found. It contains the following insertion string(s): PWRInvProvider, root\cimv2\SMS.
The description for Event ID ( 63 ) in Source ( WinMgmt ) could not be found. It contains the following insertion string(s): AMTProvisionProvider, root\CCM.
On the Primary Site server I've noticed the following errors:
No reply message from Server. Server may be temporarily down or a transient network error.
RegTask: Failed to send registration request message. Error: 0x8000000a
RegTask: Failed to send registration request. Error: 0x8000000a
Failed to initialize handler
Failed to process request(0x80070005).
Failed to send management point list Location Request Message to BBK-SCCM-PRI.bbk2310.com
Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI
Failed to create or open file mapping for CcmFrameworkServer\CcmIsapi
PerfObject::InitMemoryMap failed (80070005)
Failed to initialize memory map for CcmFrameworkServer\CcmIsapi
[0000000001CEFB38] Failed to cancel internal event sink query (80010108)
Successfully sent location services on HTTP failure switching to success message for MP 'BBK-SCCM-PRI.bbk2310.com'.
Result: Not Applicable, ResultCode: 0, ResultType: 0, ResultDetail:
Failed to get SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Real-Time Protection\DisableIntrusionPreventionSystem
Successfully sent location services HTTP failure message.
Can't get MP list from MP
MP check failed for 6 times and exceeded the threshold 3
I have 3 SCCM servers, CAS, Primary and Secondary, the issue is taking place on the Primary server.
The CAS and the Primary servers are on the same subnet. The Secondary server is on another subnet.
Nothing have lately changed.
your problems are all related to the fact that your management point is down, have you reviewed any of the logs related to the management point to see why it's failing ?
Thank you for your reply, please find below additional MP logs:
Here are the logs:
SMS_MP_CONTROL_MANAGER received START notification.
MPStart(): Registered for Notifications.
CMPControlManager::ReadConfigurationSettings(): m_pWmi->GetObject() failed - 0x80041010
CMPControlManager::ReadConfigurationSettings(): Periodic Interval is 1800000
CMPControlManager::ReadConfigurationSettings(): WINS Interval is 14400000
MPStart(): ReadConfigurationSettings() returned 0x80041010.
Querying MPHealthCheckIntervalInSeconds registry value returned a status of 2.
Querying MPHealthCheckTimeoutInSeconds registry value returned a status of 2.
Querying MPHealthCheckStatusMessageIntervalInSeconds registry value returned a status of 2.
Querying NLBNodeAvailabilityState registry value returned a status of 2.
MPStart(): Read all MP Settings.
MPStart(): SSL disabled.
CMPControlManager::WriteToCCMSettings(): WMI Connection established.
CMPControlManager::WriteToCCMSettings(): pWmi->GetObject() failed - 0x80041002
STATMSG: ID=5432 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=BBK-SCCM-PRI.bbk2310.com SITE=PRI PID=9016 TID=6664 GMTDATE=Tue Sep 23 02:01:35.325 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
MPStart(): WriteToCCMSettings() failed - 0x80041002
SMS_MP_CONTROL_MANAGER failed to start with 0x80041002
Verifying local MP outbox directory D:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\bgb.box for Notification Manager exists.
Verifying local MP outbox directory D:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\ddr.box for Discovery Data Manager (Trusted) exists.
MP Manager outbox Notification Manager maps to D:\Program Files\Microsoft Configuration Manager\inboxes\bgb.box
Worker thread [Notification Manager] halting execution.
MP Manager outbox Discovery Data Manager (Trusted) maps to D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box
Worker thread [Discovery Data Manager (Trusted)] halting execution.
Verifying local MP outbox directory D:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\swm.box for Software Metering Processor Usage (Site) exists.
Verifying local MP outbox directory D:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\polreq.box for Successful Policy Requests exists.
Verifying local MP outbox directory D:\Program Files\Microsoft Configuration Manager\MP\OUTBOXES\stat.box for Status Manager exists.
MP Manager outbox Software Metering Processor Usage (Site) maps to D:\Program Files\Microsoft Configuration Manager\inboxes\swmproc.box\usage
Worker thread [Software Metering Processor Usage (Site)] halting execution.
MP Manager outbox Successful Policy Requests maps to D:\Program Files\Microsoft Configuration Manager\inboxes\polreq.box
Worker thread [Successful Policy Requests] halting execution.
Successfully reset permission of inbox D:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs
MP Manager outbox Status Manager maps to D:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs
Worker thread [Status Manager] halting execution.
This post applies to SCCM 2012 R2 SP1
When installing Application Catalog Web Service point and Application Catalog Website point ASP.NET and WCF activation must be pre installed else the setup will fail. SCCM does not directly tell you if installation failed or not.
Looking through logs files will indicate success or failure.
SMSAWEBSVCsetup.log – Application Catalog Web Service Point
SMSAPORTALWEBsetup.log – Application Catalog web site point
Following error occurs if ASP.NET is not installed
Installation error code 125
Following errors occurs if WCF ( http activation) is not installed
Installation error code 123
Once ASP.NET and WCF http activication are installed role installation will succeed.
Status Message Error in SCCM:
Message ID. 8000
“Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.”
This issue occurs because the Applicationhost.config file for Windows Process Activation Service (WAS) has the following section defined, and this section is incompatible with the .NET Framework 4.0:
<add name=”ServiceModel” type=”System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b77a5c561934e089″ preCondition=”managedHandler” />
This section should be defined as follows:
<add name=”ServiceModel” type=”System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089″ preCondition=”managedHandler,runtimeVersionv2.0″ />
This is caused by an issue with .Net 4.0, so perform the following on the Web Server hosting the Application Catalog Website Point (and also possibly the Application Catalog Web Service Point – In my tests, both roles are on the same system):
Resolution Steps :
1) Open Command Prompt ( cmd.exe ) on SCCM server or where you have installed Application Catalog Role installed.
2) Navigate to below path
%windir%\Microsoft.NET\Framework64\v4.0.30319 (on a 64-bit computer)
3) Run “aspnet_regiis.exe /iru” Command.
4) that’s It.
For more information please Go through below Microsoft Knowledgeable Article.
Related Technet article: http://support.microsoft.com/kb/2015129
Mi piace Caricamento.Articoli collegati Navigazione articoli Lascia un commento Annulla risposta
%d blogger cliccano Mi Piace per questo:
recently i was at a customer site and that has a single primary site (with all roles on it). They have installed the Application Catalog but it was not working.
the SMS_AWEBSVC_CONTROL_MANAGER component was generating the error “Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 500, Internal Server Error. Possible cause: Internet Information Services (IIS) isn’t configured to listen on the ports over which AWEBSVC is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. For more information, refer to Microsoft Knowledge Base.” every hour.
Looking the logs, the installation happen without any problem, however, the awebsctl.log was giving me the error:
SSL is enabled.
Call to HttpSendRequestSync failed for port 443 with status code 500, text: Internal Server Error
AWEBSVCs http check returned hr=0, bFailed=1
AWEBSVC’s previous status was 4 (0 = Online, 1 = Failed, 4 = Undefined)
Health check request failed, status code is 500, ‘Internal Server Error’.
accessing the https:// /CMApplicationCatalogSvc/ApplicationOfferService.svc was giving me the error:
This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.
Looking at the IIS Bindings i saw that there was multiple bindings there as the customer was using custom ports for the MP and the default ports for the Application Catalog.
Trying to use same ports as the MP was using did not fix the problem.
Searching the internet, i found a good blog post called Tips and Tricks for Deploying the Application Catalog in System Center 2012 Configuration Manager did not even had the answer (of course!!) but gave me a bit of an idea what could be the problem. the certificate.
I created a new certificate only for Application Catalog and assigned it for the port 443, re-installed the Web Service role and…nothing…problem was still there.
Because the Web service point is based on WCF, i decided to check the WCF log that can be found under c:\Microsoft\SMS\ServicePortalWebService.svclog and i noticed
<E2ETraceEvent xmlns = "http://schemas.microsoft.com/2004/06/E2ETraceEvent" > <System xmlns = "http://schemas.microsoft.com/2004/06/windows/eventlog/system" > <EventID> 131076 </EventID> <Type> 3 </Type> <SubType Name = "Error" > 0 </SubType> <Level> 2 </Level> <TimeCreated SystemTime = "2014-01-19T05:19:21.5614377Z" /> <Source Name = "System.ServiceModel" /> <Correlation ActivityID = "<00000000-0000-0000-0000-000000000000>" /> <Execution ProcessName = "w3wp" ProcessID = "3016" ThreadID = "13" /> <Channel/> <Computer> ##SERVER## </Computer> </System> <ApplicationData> <TraceData> <DataItem> <TraceRecord xmlns = "http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity = "Error" > <TraceIdentifier> http://msdn.microsoft.com/en-GB/library/System.ServiceModel.Diagnostics.TraceHandledException.aspx </TraceIdentifier> <Description> Handling an exception. </Description> <AppDomain> /LM/W3SVC/1/ROOT/CMApplicationCatalogSvc-1-130345822160835419 </AppDomain> <Exception> <ExceptionType> System.ServiceModel.FaultException`1[[Microsoft.ConfigurationManager.SoftwareCatalog.Service.ServiceError, Microsoft.ConfigurationManager.SoftwareCatalog.Service.ApplicationOfferContract, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.ServiceModel, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089 </ExceptionType> <Message> Internal Server Error </Message> <StackTrace> at Microsoft. ConfigurationManager. SoftwareCatalog. Service. ApplicationOfferService. CheckServiceHeartbeat ( Boolean checkSiteRoundtrip. String reserved )
wow…did not help and i was going to call Microsoft Support, but decided to do a bit more troubleshooting, i found that the WCF has a known limitation with multiple bindings for the same protocol (http or https) and this was the case. they had the http set to port 80 as well as another http set to a new port (the http mp) and for https only the new port (the mp https port)..
in this case, i cannot remove the bindings, but what can be done is to create a new website under IIS (I called it AppCatalog), set the folder to c:\inetpub\wwroot (yes, the same as the default as SCCM will create a virtual folder pointing to the correct place), set the port to 443 and selected the certificate and done.
re-installed the Web service point and used AppCatalog as the IIS Website.
Once i’ve done it, everything started working. added the Web site point and app catalog started working. 🙂Share this:
Do you know the Application Catalog from SCCM 2012? This web based (silverlight) software shop provides applications to users. A user can search applications and install them directly from the portal.
If the user accounts are not in the same domain as the Application Catalog Server, you have to authorize the “domain users” of the user domain on the Shop Server (otherwise you receive the message, that the website cannot be located).
On the SCCM Server with the role “Application Catalog web service point” and “Application Catalog website point” (recommended by Microsoft to install both roles on the same server), go to the following folder:
(This folder is used by default, when installing the role without changing the options)
In the Properties of this folder on the tab “Security”, add the “Domain Users” of the user domain.
You need the following rights:
Read & Execute
List folder contents
Unfortunately, this folder is not fully inherited! You will still receive a login popup… add the needed domain users at least to the folder following folders:
Take care, the shop website needs to be in the trusted sites of the Internet Explorer. You can configure this in the Client setting.7 comments
I followed these steps and am still receiving the login popup when launching the application center.
Unfortunately I’ve checked again and yes, there is still the Login popup. The shop is working without entering login Information (on every popup just click ESC)… but it’s not nice😦 –> I’ll check again and let you know as soon as I have a solution!
Now it worked… I’ve changed the blog. The problem was, that the folder SMS_CMM is not inherited throug all directories… after giving the right permissions to the folder “AppIcons” it worked… looking forward to your feedback if it works for you too…
Unfortunately after granting access to the AppIcons folder I am still receiving the popup. Here is my scenario: CM12 and computer objects in domain A. User accounts in domain B and domain C. I have granted both domain user groups to the AppIcons and SMS_CCM folder and both to the Users local security group (noticed that you removed that section…is it not needed then?). I also verified that the shop site is a trusted site via the client.
I’ve checked once more and reinstalled everything… you need to add the domain users with read permissions to the following folders:
We are in business now. Thanks for all the great info. This has been a good help.
Looks like you do not need to grant permissions to the SMS_CCM folder, only the CMApplicationCatalog folder. Additionally, the AppIcons folder needs it as well.
Thanks for sharing!
Site System Roles add extended functionalities to the SCCM site. There are many roles such as:
Site System Role. A computer that runs the core SCCM setup program that provides the main functionality for the site.
Site Database Server. SQL DB Server storing information about CM assets and site data.
Component Server. Runs ConfigMgr Executive Service.
Management Point. Provides policy, content, and service location information to all clients and receive configuration data such as status messages and inventory from clients.
Distribution Point. Contains source files such as application contents, software packages, software updates, OS images, boot images, etc… for clients to download.
Reporting Services Point. Runs SQL Reporting services for reporting capability.
State Migration Point. Stores user data when migrating a computer to a new OS during Operating System Deployment (OSD).
Software Update Point. Integrates with Windows Server Update Services (WSUS) to provide software updates to Configuration Manager clients.
System Health Validator Point. Validates Configuration Manager Network Access Protection (NAP) policies. This role has to be installed on the NAP health policy server.
Endpoint Protection Point. (Optional Role) Configuration Manager uses this role to accept Endpoint Protection license terms and to configure default membership for Microsoft Active Protection Service.
Fallback Status Point. An alternative location for client to communicate and send status messages during installation in the event that they cannot reach their Management Point. We can identify unmanaged systems as well as monitor client installations.
Out Of Band Service Point. For out of band management.
Asset Intelligence Synchronization Point. Connects to System Center Online to download catalogs and to upload untitled catalogs for future cataloging.
Application Catalog Web Service Point. Provides software information to the Application Catalog website from the Software Library.
Enrollment Proxy Point. Manages enrollment requests from mobile devices so that they can be managed by Configuration Manager.
Enrollment Point. Provision Intel AMT-based computers and also uses PKI certificate to complete the mobile device enrollment.
In this lesson, we will install
As defined above, Application Catalog Web Site Point provides users with a list of available software. The Application Catalog Web Service Point provides information about available software from the Software Library to the Application Catalog Web Site.
Launch Configuration Manager. Select Administration, Under Site Configuration, select Sites. Click the Add Site System Roles button in the standard menu bar.
A dialog box shows up, click Next without changing any values.
Since we do not have any Internet Proxy, do not add one. Click Next.
Choose the three roles to be installed for this lab. Click Next.
Leave Status Fallback setting as default. Click Next.
Application Catalog Web site talks to Application Catalog Web Service on port 80. Click Next.
Leave everything default. Click Next.
Enter organization name and choose a theme color. When a user logs into the Application Catalog site, this theme color will show up. Click Next.
View Summary. Click Next.
When finished, click Close.
Use the Trace Log tool to open the log and check the installation process of the Application Catalog Website Point.
Make sure you see this line
Let’s also check the Application Catalog Web Service Point log.
Make sure you see that the installation status is success.
Personelinize yayınladığınız uygulamaları bir browser yardımı ile sunmak istiyorsanız SCCM tarafında ilgi alanınız
Application Catalog website point ve service point olacaktır.Yapılandırma aşağıdaki gibidir.
Sizde sözü geçen iki rol ekli değilse sccm yönetim konsolundan \Administration\Overview\Site Configuration\Servers and Site System Roles kısmından ekleyebilirsiniz.
Eğer katalog web sayfasını default site altında tutmayacaksanız yapmanız gereken öncelikle IIS altında default site’dan farklı olarak yeni bir web site açmak olacaktır. Örneğin yeni site’ın ismi katalog olsun. URL’sini de katalog.domain.tld şeklinde düşünün
Yukarıdaki bileşenleri eklerken website point için katalog ismini kullanabilirsiniz. Ama web service point için sonradan sorunla karşılaşmamak yada ekstra efor sarfetmemek adına default web site’ı kullanın. Yani cmapplicationcatalogsvc. default web site içinde. cmapplicationcatalog ise sizin yeni açtığınız site’da dursun.
Eğer hem servisi hem catalog’ default web site haricinde yeni sayfada tutarsanız. web browser’dan katalog sayfanız açılacak ama service’e bağlanamayarak hata verecektir.
cmapplicationcatalog bilgileri aşağıdaki gibidir .
cmapplicationcatalogsvc bilgileri aşağıdaki gibidir.
Sonrasında 2-4 dakika kadar bekleyin. yeni virtual directory/application’lar IIS altında belirsin.
Ardından http://katalog.domain.tld/cmapplicationcatalog adresinden kataloğunuzu açabilirsiniz. IIS’te bir http redirection ile URL son kısmından da kurtulabilirsiniz.
Tabii ki redirection’ı default web site’da değil ismi katalog olan yeni site üzerinde yapacaksınız.Random Posts Post navigation Recent Posts Blogroll Top Posts & Pages Search Categories Archives