Troubleshooting: Update Web.Config Fails With a System.Xml.XmlException – SecureAuth Support

Version Affected: All

Overview

Clicking Update Web.Config can fail with an unhandled System.Xml.XmlException stack trace instead of completing normally -- for example, Name cannot begin with the ''' character, hexadecimal value 0x27. The specific character and message named in the error vary depending on what actually broke the XML.

Cause

The Transformation Engine's userprofiledata.xslt file has been edited and now contains invalid XML, which breaks the update process for the whole appliance, not just the realm the file was edited on. An unescaped quote character is a common cause, but any other invalid character, or any other way the file's XML has become malformed, produces the same kind of error.

Resolution:

Replace the affected realm's userprofiledata.xslt file with the stock version:

ASP.NET Server Error page showing a System.Xml.XmlException: Name cannot begin with the ' character, hexadecimal value 0x27, thrown from MFC.WebApp.SecureAuth.UpdateWebConfig.UpdateXSLT.

The Update Web.Config error itself does not identify which realm or file is responsible. Check each realm for whether Transformation Engine is enabled -- it is only shown on realms where it has been turned on.
On any realm with Transformation Engine enabled, open its userprofiledata.xslt in the XSLT Editor and look for content that should not be there (for example, extra text pasted in alongside the XSLT).
Copy that realm's edited userprofiledata.xslt out of D:\Secureauth\<RealmName>\PostAuthData:

File Explorer showing the realm's own PostAuthData folder, containing usersprofiledata.xslt.

Copy in the stock version instead, from D:\Secureauth\Template\PostAuthData\usersprofiledata.xslt:

File Explorer showing the stock Template PostAuthData folder, containing the original usersprofiledata.xslt.

Run Update Web.Config again -- it should now complete successfully.

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.