CRM 2013 Maintenance Jobs

Darren Liu's Blog

The Maintenance jobs for CRM 2013 is similar to the CRM 2011 jobs if they are not the same. I had to dig into the details of each of the jobs for my project. These are my findings and I hope it will be useful for everyone. Please remember to reschedule these maintenance jobs after the installation of CRM is completed.

Maintenance Job Name


Default Frequency/ Recommendation

Deletion Service

The deletion service maintenance operation now cleans up subscription tracking records for deleted metadata objects as they expire.

  • If Outlook does not sync for 90 days, the job will remove the subscription with CRM.
  • Cleanup POA records. Un-sharing of record(s) do not remove the records in the POA table, it will stay there for 90 days and it will clean up by the deletion job.
  • Cleanup failed/stuck workflows for the record(s) synchronize with Outlook.

By default, the job executes every…

View original post 1,611 more words

attributeName error while using join in LINQ in CRM.

I recently wrote a LINQ using joins, all seemed fine, but was still getting the attributeName exception. Finally this post came to rescue.

Hope it helps.


REVIEW: Microsoft Dynamics CRM 2013 Marketing Automation


I was very happy to receive the eBook of Microsoft Dynamic CRM 2013 Marketing Automation (Packt Publishing by Alok Singh and Sandeep Chanda) for review few days back.


It a mini guide focusing on the Marketing Module of CRM 2013, with around 100 pages divided into 6 chapters. It starts by explaining the challenges faced in marketing and how CRM 2013 can address those challenges. It then explains in detail various feature available in Microsoft Dynamics CRM 2013 that can be leveraged to successful implement the marketing module.It also talks about two of the most popular third party marketplace solution available for marketing module of CRM i.e. ClickDimensions and CoreMotives.

The book is very informative and clearly explains everything that there is in Marketing Module of CRM 2013. The authors are expert and we can clearly see their authority in the subject.

It a must read guide for all the CRM professionals.

Grab your copy here






CRM 2013 – Workflow to set the current date and time

Hosk's Dynamic Blog

This question has popped up in the forums now and again so I thought I would write a blog post on it.

The solution on how to do this is simple, once you know where to look and how it works.  I can understand why some people struggle to find the answer to the question of setting a date field to the current date and time because you don’t see it mentioned very often and it isn’t obvious.

To set the a Date Time value in CRM to a when the workflow was run you can use the dynamic value


Execution Time

This basically does what is says on the tin and sets a Date time value to Execution time of the workflow.

workflow for current date and time

Open up your workflow and choose the Update, select Account entity

To set a field

Select the field and in the example above, I clicked into…

View original post 67 more words

The request for security token could not be satisfied because authentication failed error in CRM while developing Visual Web Part in SharePoint 2013.


We recently developed a Visual Web Part which was using OrganizationService to interact with CRM.

We were initially using Network Credentials for OrganizationService and were setting appropriate username, password and domain. Later we changed it to Default Credentials and set the AppPool identity of the SharePoint portal’s app pool to a CRM User with appropriate access. It was then we started getting this error.

The reason was SharePoint web configuration settings has Identity Impersonation set as true.

If impersonation is set as true, then IIS uses the ‘NT AUTHORITY\IUSR’ but if disabled IIS will run under whatever account been set in the identity pool.

So one way of fixing the issue was setting impersonation as false.

Hope it helps.

Fix: NodeRunner.exe processes consume lots of RAM (memory) and CPU

Tjen Sharepoint Blog

I started SharePoint 2013 development recently. Initially, I only got dual core CPU and 4 GB RAM and as you probably know, it runs very slow. I’m not curious about it cause I expect the performance when you install SharePoint 2013 with less than minimum recommended hardware specification.


Then .. I fed up with it and upgrade the RAM to 8 GB, but funny things my development box is still runs very slow. I looked into my task manager and found something like below. Several NodeRunner.exe processes consume lots of Memory and CPU.



  1. Open SharePoint 2013 Management Shell and type in:
    Set-SPEnterpriseSearchService -PerformanceLevel Reduced
  2. Open NodeRunner process configuration file below in Notepad
    C:Program FilesMicrosoft Office Servers15.0SearchRuntime1.0noderunner.exe.config.
    Update <nodeRunnerSettings memoryLimitMegabytes=”0″ />.
    This is the configuration to limit NodeRunner process memory usage, replace to acceptable number like 100 or 150.
  3. Restart SharePoint Search Host Controller service.

NOTE: I’ve…

View original post 52 more words