I have
faced this issue while trying to do the dynamic operation with the Timer Job in
Sharepoint 2013.
After
doing some research i got to know that in Sharepoint 2013 by default .Net
Legacy CAS support being enabled for all the web applications and Sharepoint
Timer Services.
The
solution is disable the .Net Legace CAS support for the sharepoint timer service.
Here are
the steps
·
Go to C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\Bin
·
Locate the OWSTIMER.EXE.CONFIG and Open this file.
·
By default NetFx40_LegacySecurityPolicy is set to true. You have set enabled to false (Marked in Red).
<configuration>
<runtime>
<NetFx40_LegacySecurityPolicy
enabled="false"/>
</runtime>
</configuration>
Save the File. And Reset the IIS.
This will do the magic and allow the dynamic operation with the
sharepoint 2013 Timer Job.
Please note any sharepoint update can replace your changes.
No comments:
Post a Comment