The tool is available for download at the codeplex site: https://enterpriselogger.codeplex.com/.
The entire documentation of the tool and how to use it can be found in the documentation tab in the codeplex site. In case you want to keep reading this blog, I suggest you go back to the link: https://debajitcrm.wordpress.com/2014/06/26/enterprise-logger-for-microsoft-dynamics-crm/ and gather an idea about the tool and what it does.
Now we would see how we can configure the Enterprise Logging tool for CRM to log in the CRM entity. This is the most simplest of configuration.
The logging would happen in the “Error Log” entity which is comes with the Xrm Logger solution.
Please Note: If you are using Crm Entity as the logging mechanism, you should make sure that all your security roles should have Organization Level Read, write and Create access on the Error Log entity. Sounds difficult? No worries, I have the RolePrivilegeUtitlity.exe executable, which I would provide along with this tool, which will do that for you.
Now I have selected “Crm Entity” as my logging mechanism and saved the configuration.
Now I again go in CRM and create an account. Next I open Advanced Find in CRM and check for the Error Log entity.
Isn’t this truly interesting. You have changed the Logging Mechanism without changing a single line of code!
Please read this very carefully if you are using the CRM entity as your logging mechanism
If you are invoking the Logger methods from CRM, where CRM maintains transactions (synchronous plugin and synchronous workflows(CRM 2013 only)), the logger tool would log an error in the Error Log entity only if the passExceptionToUser parameter in the method of the logger is set to false. If it is set to True, the error would be thrown back to the user with the complete stack trace but no Error Log record would be created. However no such restrictions for Warning and Message Logging.
Another great advantage of the tool is say you are moving your organization from on-premise to online, no change in the logging code is required. All you need to do is come back to the configuration page of the Xrm Logger solution and select Office 365 and then CRM would start to log in the Error log Entity.