How to fix ‘Invalid Trace Directory’ errors

As part of the migration process I’ve been going through the event logs for our CRM deployment to ensure everything is working correctly, during this I came across an ‘Invalid Trace Directory’ error (event id 17203) which was showing the following –

Invalid Trace Directory. Additional Info:[ Invalid Trace Directory (Reporting Process:Trace Diretory is Null. TraceSettings: {Filename:  ,FileCountSuffix:1 ,TraceFileSize:10485760 ,TraceDirectory: ,TracingCallStack:No ,IsTracingOff:Yes ,LoadState:LoadSuccessfulUnreported ,RefreshTraceInt:-1 ,SiteWideRefreshTraceInt:-1 ,RegistryRefreshTraceInt:6 ,Precedence:Default} ] , AppDomain:CrmAsyncService)

This error is because by default the Trace Directory will be set to ‘C:\crmdrop\logs’ which doesn’t normally exist (but you can just create it for a quick fix, I’d suggest changing it using the instructions below though).

Although this error doesn’t cause a huge issue it can keep producing quite a few errors in the event log which nobody likes to see –


Now this is pretty easy to resolve using a bit of PowerShell as I’ll show below.

Continue reading “How to fix ‘Invalid Trace Directory’ errors”


How to Resolve 500 Internal Server Errors Caused by Custom Parameters in Dynamics CRM

I’ve spent quite some time now banging my head off the desk to figure out what was causing an issue with one of our PowerObjects solutions after we’d attempted to migrate to CRM 2016 from CRM 2013 and have finally found the cause.

Quite a few solutions in the market use custom parameters on the end of address’s to pass data which if you look at a network trace in any browser will display similar to this –


However, after you’ve migrated you may find you start seeing the ever useful generic 500 error when attempting to do lookups of any kind which I’ll show you how to fix.

Continue reading “How to Resolve 500 Internal Server Errors Caused by Custom Parameters in Dynamics CRM”

WindowsSearch error when installing Dynamics CRM on Server 2016

I’ve been testing the migration process from CRM 2013 to CRM 2016 recently and came across a potential issue, in some cases it seems that Windows Server 2016 has the search service disabled which causes an error message stating –

‘Action Microsoft.Crm.Setup.Common.InstallWindowsSearchAction failed. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)’

Continue reading “WindowsSearch error when installing Dynamics CRM on Server 2016”

Loading and Using Required Form Libraries Programmatically – JavaScript CRM 2013

Something I had quite a bit of trouble figuring out when I set out to make my own CRM solution is ‘how do I use required form libraries without manually adding them to each form?’  or to put it another way ‘is there any way to programmatically load web resources?’ and the answer is “by using the code below” and “yes”.

Before I continue I would like to give credit to Inogic from the Dynamics Community for providing the code I originally used.

Continue reading “Loading and Using Required Form Libraries Programmatically – JavaScript CRM 2013”

Release of ‘Copy Opportunity Line Items’ CRM 2013 Solution

I’ve released a small solution on CodePlex for CRM 2013 online and on-premise which adds a new command bar button to the opportunities entity which will allow you to perform a lookup of another opportunity and to copy the line items from that opportunity to the current one.

Copy Opportunity Line Items – Dynamics CRM Solution

Continue reading “Release of ‘Copy Opportunity Line Items’ CRM 2013 Solution”

Useful CRM 2013 Tools

As a CRM administrator I’m all for saving as much time as possible, and as such over the years I’ve collected a small assortment of tools that I use on a daily basis that make working with CRM that much quicker and easier. Below I have included a list of my favourite programs and CRM solutions to tackle every day challenges.

Continue reading “Useful CRM 2013 Tools”

How to Stop CRM Adding the GUID to SharePoint Folder Names (Documents)

CRM has a very useful feature called Documents which allows you to link a CRM and SharePoint deployment in order to store customers documents in SharePoint however with the update to 2013 Microsoft decided that all folders will include not just the records name but that records GUID.

I had a request recently to stop CRM adding the GUID of account records to newly created SharePoint folders and it was surprisingly difficult to find any useful advice. Below I will cover the basic steps required to disable this ‘feature’.

Continue reading “How to Stop CRM Adding the GUID to SharePoint Folder Names (Documents)”