Troubleshooting: Updating web.config Fails Due to a Customized Transformation Engine XSLT File

Version Affected: All
 
 

Overview

Updating a realm's web.config can fail with a generic stack-trace error.
 

Cause

Transformation Engine (TE), if enabled on a realm with a customized userprofiledata.xslt file, is a common culprit -- the error itself doesn't identify which file is at fault.

Resolution:

1. Attempt the web.config update and confirm the same generic error appears.

2. Check whether Transformation Engine is enabled on any of the realms.
3. If a realm has Transformation Engine enabled and its userprofiledata.xslt file has been customized, copy that file out, then copy in the stock userprofiledata.xslt from the template folder instead.
4. Place the stock file in that realm's D:\SecureAuth\SecureAuth<n>\PostAuthData folder (where <n> is the realm number), then run the web.config update again -- it should now succeed.

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.