How To: Find Missing Realm Folders, IIS Applications, or web.config Files

Version Affected: All

 

Overview

Missing realm folders, IIS Applications, or web.config files can cause problems with FileSync and other IdP components, including the error described in Troubleshooting: FileSync Fails to Create, Read, or Sync SyncManifest.xml. A folder can go missing while its IIS Application still exists, an IIS Application can go missing while its folder still exists, or a realm folder can be missing its own web.config file -- see also Troubleshooting: FileSync Creates Lowercase Realm Folder and IIS App Names for a related naming mismatch. Checking every realm by hand can take a long time on an IdP with many realms, so use the PowerShell commands below to quickly identify what's missing instead.

Compare Realm Folders, IIS Applications, and web.config Files

Run PowerShell as Administrator for both commands below. If the SideIndicator in the output points left (<=), the filesystem folder is present but the IIS Application is missing. If it points right (=>), the IIS Application is present but the filesystem folder is missing.

Compare IIS Applications (in Default Web Site) against filesystem folders (in D:\SecureAuth) with names matching SecureAuthXXX:

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

Find any realm folders that are missing their 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. If it isn't already imported, run Import-Module WebAdministration first.


 

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.