Monday, 29 July 2013

SPF Part 5 - Registering the Service Provider Foundation Endpoint


This is the final step in registering the System Center 2012 R2 Service Provider Framework endpoint with the Azure Pack management server. Compared to the previos steps, it's a much smaller piece of work so it should be over quickly.

Other posts in this series are



Note: The username is potentially case-sensitive. We had a few problems here registering the endpoint, and we used the following troubleshooting steps as follows to try to identify the problem. However, once we used the correct case in the username (i.e."va\Administrator" instead of "va\administrator") the endpoint registered successfully. We're not sure if this was just a concidence, but since it resolved the issue we were unable to investigate further.
  • First, enable Failed Request Tracing in IIS on the Service Provider Framework server (VASCM01 in this case). Configure a tracing rule for the SPF website in Internet Information Services Manager, for all content with status codes 200-999 and for all providers. Then, enable Failed Request Tracing from the Actions pane for the SPF website.
  • Next, try to configure the endpoint again in the Azure Pack management server. If this still fails, check the failed request trace log folder on the SPF server ("%SystemDrive%\inetput\logs\FailedReLogFiles\W3SVC2" by default). This should contain some "fr######.xml" files. Open the highest-numberer file in Internet Explorer and check if you see the following error:
          ModuleName - ManagedPipelineHandler
          Notification - EXECUTE_REQUEST_HANDLER
          HttpStatus - 401
          HttpReason - Unauthorized
          HttpSubStatus - 0
          ErrorCode - The operation completed successfully. (0x0)

  • Check the "Compact View" on the trace, and check the RequestURL in the first trace event is ""

  • Open Event Viewer and check the "Event Viewer -> Application and Services Logs -> Microsoft -> Windows -> ManagementOdataService -> Operational channel" log. We saw an error logged with the following details:
          - <Event xmlns="">
            - <System>
                <Provider Name="Microsoft-Windows-ManagementOdataService" Guid="{60B4C807-9E58-40D0-A608-9A60DFFDD6B9}" />
                <Version>1 </Version>
                <TimeCreated SystemTime="2013-07-29T20:39:07.612582900Z" />
                <Correlation ActivityID="{7212F460-8C7E-0000-C85B-13727E8CCE01}" />
                <Execution ProcessID="2392" ThreadID="3568"/>
                <Security UserID="S-1-5-20" />
            - <EventData>
                <Data Name="userName">va\Administrator</Data>
                <Data Name="authenticationType">Basic</Data>

  • On the Azure Pack management server, open Internet Explorer and try to navigate to the url in the error (i.e. ""). This should load an document containing an OData xml document as per the screenshot below.


  1. Do you have an overall topology for this WAP environment? I've been looking at the installation guides offered by Microsoft and it is confusing. I really want to install it and play around with it but so far you are the only site I know even trying it.

  2. Hi Jason,

    You're not alone - I've had the same experience with the TechNet documentation. It's pretty incomplete at the moment, so hopefully they'll be updating it with more details and a better layout as time goes by.

    We're basically just following our nose as we go, and dealing with problems when we find them. I'll post a network diagram of what we've installed so far in the next few days. We've not even finished our Virtual Machine Cloud setup, and there's still all the Service Bus and Web & Worker Role farms to install yet, but it might help a little bit.



  3. Looking forward to your upcoming posts. Not sure why Microsoft is making this so difficult. The requirements are ridiculous.