Home » IT - Microsoft » Troubleshooting federation server farm problems with AD FS 2.0

Troubleshooting federation server farm problems with AD FS 2.0

Escribe tu dirección de correo electrónico para suscribirte a este blog, y recibir notificaciones de nuevos mensajes por correo.

Join 5 other followers

February 2016
M T W T F S S
« Nov   Mar »
1234567
891011121314
15161718192021
22232425262728
29  

NO! A LOS TOROS

Disclaimer

All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights. The content of this site are personal opinions and might not represent the Microsoft Corporation view. Regarding any sample code that we provide: This Sample Code is provided for the purpose of illustration only and is not intended to be used in a production environment. THIS SAMPLE CODE AND ANY RELATED INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. This blog serves 2 purposes. Firstly, I want to share information with other IT pros about the technologies we work with and how to solve problems we often face. Secondly, I use my blog as a notebook. There's so much to learn and remember in our jobs that it's impossible to keep up. By blogging, I have a notebook that I can access from anywhere. Anything you do to your IT infrastructure, applications, services, computer or anything else is 100% down to your own responsibility and liability. Mcselles bears no responsibility or liability for anything you do. Please independently confirm anything you read on this blog before doing whatever you decide to do.
Advertisements

The following table provides troubleshooting guidance for specific error event messages or other issues that you may encounter if you are having problems in a federation server farm deployment.

Before you begin the troubleshooting process, we recommend that you first try to configure Active Directory Federation Services (AD FS) 2.0 for troubleshooting and check for known common issues that might prevent normal functioning for the Federation Service. For detailed instructions for configuring and performing related system checks, see Configuring Computers for Troubleshooting AD FS 2.0 and Things to Check Before Troubleshooting AD FS 2.0.

 

Event or symptom Possible cause Resolution

Event ID 344 
There was an error doing synchronization. Synchronization of data from the primary federation server to a secondary federation server did not occur.

Generally, this event results from any failure that occurs during the synchronization. The following are more specific possible causes of this event:

  • If the error occurred while data was being read on the primary federation server, the primary federation server is unavailable or the service account identity on the secondary federation server computer does not match the service account identity of the primary federation server.
  • If a SQL write operation failed to write to the configuration database on the local federation server, the cause might be that the SQL Server or Windows Internal Database (WID) service was stopped.

Refer to the additional data in the event to determine the actual cause. Also, when this event occurs for any type of synchronization failure, look for a corresponding error (Event ID 346) on the synchronization partner server.

Make sure that the primary federation server is available, and that the service account identity of this computer matches the service account identity of the primary federation server.

Event ID 345 
There was a communication error during AD FS configuration database synchronization. Synchronization of data from the primary federation server to a secondary federation server did not occur.

Communication failed between the primary federation server and other secondary federation servers in the same farm.

Troubleshoot network connectivity between servers in the federation server farm. For more information, see Verify network connectivity.

Event ID 346 
There was an error during the retrieval of configuration data for the secondary federation server.

The SQL Server or WID service is not available.

Troubleshoot network connectivity between servers in the federation server farm, and verify that the SQL Server or WID service is available. For more information, see Verify network connectivityand Verify that the Federation Service can connect to the AD FS configuration database.

Event ID 351 
There was an error getting synchronization properties.

The SQL Server or WID service is not available.

Troubleshoot network connectivity between servers in the federation server farm, and verify that the SQL Server or WID service is available. For more information, see Verify network connectivityand Verify that the Federation Service can connect to the AD FS configuration database.

Event ID 382 
AD FS 2.0 detected that the Federation Service has more than %1 %2 trusts configured.

The farm deployment is trying to synchronize using a WID database, and it has more than 100 claim trust provider trusts or more than 100 relying party trusts.

Move to SQL Server for improved database synchronization performance when you need to support more than 100 claim trust provider trusts or more than 100 relying party trusts.

For more information about how to do this, see AD FS 2.0 operations documentation on theTechNet Wiki site (http://go.microsoft.com/fwlink/?LinkId=181189).

Source: https://technet.microsoft.com/en-us/library/adfs2-troubleshooting-federation-server-farm-problems(v=ws.10).aspx

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Microsoft on the Issues

News and perspectives on legal, public policy and citizenship topics

Mike Crowley's Whiteboard

“There are no limits to what you can accomplish when you are supposed to be doing something else."

T.B.D.

There Be Dragons

Ken Cenerelli

My life in software development

VMware, Windows, Virtualization (Servers & Desktops)

VMware, Windows, Virtualization (Servers & Desktops)

Just a random "Microsoft Server / Client Tech" info..

"Feeding Your Training and Technology Obsessions"

WordPress.com

WordPress.com is the best place for your personal blog or business site.

DocSharing

Documentación técnica, notas y apuntes sobre Administración de Sistemas, Servidores, Redes y más

Microsoft Taste

Mary's Blog

%d bloggers like this: