Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Plugin Trace Log not working on Dynamics CRM 2016 On-Premise RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I have set "Enable logging to plug-in trace log" to "All" and I have verified that the setting is updated in the organization entity. The setting is a optionset with a value of 2. My CRM version is (8.0.0.1088) (DB 8.0.0.1088). I have also tried setting the value to "Exception".

    However when a plugin executes, exception or not,  nothing is written to the plugin trace log.

    Has anyone experienced the same?

    Regards.

    Marius Solend


    Thursday, February 4, 2016 5:17 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Yep. For the life of me I cannot get logging to work on CRM 2016. WTF
    Tuesday, March 22, 2016 5:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am also having the same issue with Dynamics 2016 On-Premise.
    Wednesday, December 21, 2016 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    yep, same with me (on-prem, Dynamics 365): no logging is happening by the Pluging Trace Log.

    But: when I'm using the Profiler-tool (from the SDK) and install its Solution, the Plugin Trace Log are populated:

    ...so clearly there are something that the ProfilerPlugin do that makes the logging work.

    regards,

    Marius H. Enerud


    • Edited by morris80 Thursday, January 19, 2017 10:34 AM
    Thursday, January 19, 2017 10:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Refer this:

    https://community.dynamics.com/crm/f/117/t/189346

    Regards, Saad

    • Proposed as answer by Mohd Saad Thursday, January 19, 2017 12:47 PM
    Thursday, January 19, 2017 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Saad, the thread you are referencing seems to be one of the few that discuss this matter.

    But this is still being reported as a bug..Strange that MS doesn't have any answer/confirmation of this issue..

    Thursday, January 19, 2017 1:23 PM