How to find missing realm folders and IIS applications

Version Affected:  All

Description:  

How to find missing items that cause problems with FileSync and other components of IdP.

Cause:  

The following can cause problems with Filesync and can lead to the error described in this article:

https://support.secureauth.com/hc/en-us/articles/360027892151-FileSync-Object-Reference-Error-When-Creating-SyncManifest-xml

1. Missing realm folders, where the IIS Application for a realm exists but the folder on D: drive does not.

2. Missing IIS Applications where the folder exists on D: drive but the corresponding IIS Application is missing.

3. Missing web.config files from SecureAuthXXX realm folders present on D: drive.

Manually checking what exactly is missing can take a long time if many realms are involved, so instead run the commands below to help quickly identify what is missing.

Resolution:  

The following Powershell command runs a comparison between IIS Apps (in Default Web Site) and filesystem folders (in D:\SecureAuth) with names matching SecureAuthXXX.  Powershell should be run as Administrator for these commands.

If the SideIndicator points left then that means there is a filesystem folder present but the IIS App is missing.

If the SideIndicator points right then that means there is an IIS App present but the filesystem folder is missing.

compare (gci d:\secureauth | ?{$_.name -match "SecureAuth[0-9]{1,3}$"}).name (gci 'iis:\sites\default web site' | ?{$_.name -match "SecureAuth[0-9]{1,3}$"}).name

This command shows any realms which are missing a web.config file.

gci d:\secureauth | ?{$_.name -match "SecureAuth[0-9]{1,3}$"} | %{if(!(Test-Path "$($_.fullname)\web.config")){Write-Host "$($_.name)\web.config is missing" -ForegroundColor Red}}

Special Considerations:  

The commands above require the IIS Administration module, so if not already imported run the following command first:

Import-Module WebAdministration

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.