Troubleshooting: Update Web.config Fails with an XML Comment Error in userprofiledata.xslt

Version Affected: All
 
 

Overview

Running Update Web.config can fail with a Server Error: An XML comment cannot contain '--', and '-' cannot be the last character.

Cause

Update Web.config fails when it reaches an incorrectly formatted XML comment in a realm's userprofiledata.xslt file (Transformation Engine).

Resolution:

Narrow down which realm's userprofiledata.xslt file is causing it:

1. In File Explorer, navigate to D:\SecureAuth, search for web.config, and sort the results by date/timestamp.
2. Find the point where updates stopped succeeding -- for example, if every web.config updated from SecureAuth998 down to SecureAuth10 but failed going from SecureAuth9 to 0, check the userprofiledata.xslt file in SecureAuth10\PostAuthData.
3. To confirm a specific .xslt file is the cause, back it up, replace it with the stock copy from D:\SecureAuth\Template\PostAuthData, and run Update Web.config again.

Special Considerations

Always back up userprofiledata.xslt before overwriting it with the stock file. If FileSync is in use, changes to a realm's Transformation Engine code in userprofiledata.xslt are not replicated to secondary servers unless the path is defined in paths.list.


 

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.