Skip to primary content
Skip to secondary content

Working Hard In IT

My view on IT from the trenches

Working Hard In IT

Main menu

  • Home
  • About WorkingHardInIT
  • Blog Roll
  • Contact WorkingHardInIt
  • Privacy Policy
    • GDPR – Request personal data

Tag Archives: The Federation Service was unable to create the federation metadata document as a result of an error.Document Path: /FederationMetadata/2007-06/FederationMetadata.xml

The Federation Service was unable to create the federation metadata document as a result of an error.Document Path: /FederationMetadata/2007-06/FederationMetadata.xml

Posted on July 4, 2017 by workinghardinit
2

While working on upgrading a Windows 2012 R2 ADFS Farm to Window Server 2016 I noticed the worried looks of the systems administrators while looking at a warning in the ADFS event log, which they wanted to trouble shoot. I knew they had a hardware load balancer in place which made me 99.999% sure it wasn’t a real issue. You see, early documentation on configuring load balancing for and ADFS farm was often configured with a health check for the following url: /FederationMetadata/2007-06/FederationMetadata.xml. This leads you to an XML file that should be available on a working ADFS node.

This works fine. The Kemp Loadmaster knows the ADFS nodes are functional or not and can do it’s job. There’s a nagging issue however. The ADFS log on the ADFS farm node keep logging every health check with a warning

Event ID 143 AD FS

The Federation Service was unable to create the federation metadata document as a result of an error.Document Path: /FederationMetadata/2007-06/FederationMetadata.xml

Additional Data
Exception details:
System.Net.HttpListenerException (0x80004005): The specified network name is no longer available at System.Net.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 size) at Microsoft.IdentityServer.Service.FederationMetadata.SamlMetadataListener.OnGetContext(IAsyncResult result)

As you cans see it just fills the logs every 9 seconds (the frequency of the health check).

image

This leads to hunting for a “ghost” issue that’s actually only an artefact of checking for .

Kemp has updated their documentation with 2 other values for the health check url to use. The good news is these don’t cause the above artefact of logging warning to the ADFS event log. These 2 options are:

  • /adfs/services/trust/mex

image

This leads to an XML file as well but it doesn’t cause the warning to be logged.

image

  • /adfs/ls/idpInitiatedSignon.aspx.

This leads to the ADFS login page which also doesn’t cause a warning to be logged.

So by changing your health check to any of the  above you get a functional health check for your nodes and you don’t have the phantom warning entries in the ADFS event log. That’s a lot better and at least doesn’t cause any unneeded concerns by the initiated accidental ADFS administrator.

Posted in ADSF, IT Pro, Load Balancing, Trouble Shooting, Windows Server 2012 R2, Windows Server 2016 | Tagged ADFS, Event ID 143 AD FS, KEMPTechnologies Loadmaster, The Federation Service was unable to create the federation metadata document as a result of an error.Document Path: /FederationMetadata/2007-06/FederationMetadata.xml, Url health Check | 2 Replies
StarWind
VirtualMetric Hyper-V Monitoring and Hyper-V Reporting

Recent Posts

  • Festive Tech Calendar 2022 – mTLS with Azure AppGateway & AppService December 13, 2022
  • Use DNS Application Directory Partitions with conditional forwarders to resolve Azure private endpoints August 24, 2022
  • PowerShell script to maintain Azure Public DNS zone conditional forwarders August 9, 2022

Recent Comments

  • Tech-Man-Dan on A WatchGuard Firebox M200 joins the home lab
  • workinghardinit on A WatchGuard Firebox M200 joins the home lab
  • Tech-Man-Dan on A WatchGuard Firebox M200 joins the home lab

Hot Topics

  • 10Gbps
  • Active Directory
  • Azure
  • Backup
  • Backups
  • Cloud
  • Cluster
  • Clustering
  • Community
  • Compellent
  • Conference
  • CSV
  • DCB
  • DELL
  • Education
  • ETS
  • Hyper-V
  • Kemp
  • Learning
  • Live Migration
  • Loadmaster
  • Microsoft
  • Multichannel
  • Networking
  • NIC Teaming
  • ODX
  • PFC
  • PowerShell
  • Private Cloud
  • RD Gateway
  • RDMA
  • RoCE
  • SAN
  • SMB Direct
  • Storage
  • Storage Spaces
  • VEEAM
  • VEEAM Vanguard
  • VHDX
  • Virtualization
  • Windows 8
  • Windows 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

Archives

Subscribe to WorkingHardInITvia Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 7,979 other subscribers

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org
Proudly powered by WordPress