Update Web.config results in Server Error: System.Xml.XmlException: An XML comment cannot contain '--', and '-' cannot be the last character.

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All


    When performing an Update Web.config, it ends up failing and lands on the following Server Error:




    The Update Web.config portion is failing once it lands upon an incorrectly formatted XML comment within a userprofiledata.xslt file (Transformation Engine).



    In order to narrow down which userprofiledata.xslt file is causing the issue, in a File Explorer window, navigate to D:\Secureauth. From here, search for "web.config" and filter by the date and timestamp.

    For example, If all web.configs updated from SecureAuth998 to 10 but failed to update from SecureAuth9 to 0, check the userprofiledata.xslt file in SecureAuth10\PostAuthData. If there is uncertainty as to which portion(s) of the code are causing the issue, you can test to affirm if it is indeed the specific .xslt file by making backup of the file and copying over the stock .xslt file from D:\Secureauth\Template\PostAuthData and running an Update Web.config.


    Special Considerations (optional as needed):  

    Make backups of the userprofiledata.xslt as needed, prior to overwriting with a stock file from the Template folder. Additionally, bear in mind if you have FileSync in use, that any changes made to the Transformation Engine code in the userprofiledata.xslt file will not be replicated over to secondary servers, unless you have the path defined in the paths.list file.



    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.

    0 out of 0 found this helpful



    Please sign in to leave a comment.