Enable logging to troubleshoot web services

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



    You might see follow error in the debug log for a Web service multi-data store realm:

    exception: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.



    By default, the service does not send any information explaining what happened. WCF does not reveal details about what the service does internally.

    For more information see the following Microsoft article:





    Use the instructions below to enable additional exception logging by editing the web.config for the data source realm (e.g. AD, SQL etc.) that generated an exception.  This will not be the same realm as where the above log message is seen (the realm using a WebService data source).  However the relevant realm can usually be determined from the same log, e.g. in this instance the web.config for SecureAuth4 should be modified:



    1. Decrypt the web.config, open the Admin console and click on the SecureAuth logo, then Tools | Decrypt Web Config

    2. Select the relevant realm and click the Decrypt button.
    3. Next go to the realm folder, e.g.:  D:\SecureAuth\SecureauthXX and make a copy of the web.config file.

    4. Edit the web.config in a text editor and enter the following line between the <serviceBehaviors> tag:
    <serviceDebug includeExceptionDetailInFaults="true" />



    5. Reproduce the fault, the exception details should now be available in the Debug log of the WebService realm.

    6. When the troubleshooting is complete, revert the web.config file that was modified in Step 4.




    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.