Troubleshooting: Content and Localization Link Inaccessible Due to Hash Files

Version Affected: All
 
 

Overview

The Content and Localization link, under the Overview tab of the Admin Console, is inaccessible and shows a Server Error:

Data at the root level is invalid. Line 1, position 1.

The full error page shows an XmlException raised from WebAdminVerbiageEditor:

Cause

The realm's Resource folder (D:\SecureAuth\SecureAuth<realm>\Resource) contains hash files (.md5, .sha1, or .sha256) alongside the language .resx files. The Verbiage Editor tries to parse these hash files as XML, which fails.

Resolution

1. Open PowerShell in admin mode.
2. To preview which hash files would be removed across every realm, without deleting anything yet, run:

   $Realms = Get-ChildItem D:\SecureAuth -Directory | Where {$_.Name -match "SecureAuth[0-9]"}
   Foreach ($Realm in $Realms){
   	$Realm = $Realm.Fullname;
   	GCI "$Realm" -recurse | Where {$_.extension -eq ".md5" -or $_.extension -eq ".sha1" -or $_.extension -eq ".sha256"} | Remove-Item -WhatIf
   }

3. To actually delete the hash files from every realm's Resource folder, run:

   $Realms = Get-ChildItem D:\SecureAuth -Directory | Where {$_.Name -match "SecureAuth[0-9]"}
   Foreach ($Realm in $Realms){
   	$Realm = $Realm.Fullname;
   	GCI "$Realm" -recurse | Where {$_.extension -eq ".md5" -or $_.extension -eq ".sha1" -or $_.extension -eq ".sha256"} | Remove-Item -force
   }

   To delete the hash files from a single realm instead, run:

   GCI "D:\SecureAuth\SecureAuth1" -recurse | Where {$_.extension -eq ".md5" -or $_.extension -eq ".sha1" -or $_.extension -eq ".sha256"} | Remove-Item -force

   Once removed, the affected realm's Resource folder contains only the language .resx files:
4. Log in to the Admin Console and go to the Content and Localization link under the Overview tab. It is now accessible.

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.