Sapphire On I Love Money

Two important aspects to consider in Custom SharePoint Timer Job 2010

Apparently Visual Studio 2010 has done a good job to automate the installation and deployment process when developing components for SharePoint 2010, Web elements, "Timer Jobs", etc. . So good work that developers have not developed to SP 2007 does not know that installing the Timer Job manually on the server production is necessary to enable the "feature" in the Site Collection (Assuming the defined scope of the "feature" is equivalent to a Site Collection Sites). Otherwise though this installed, and implemented the "Timer Job" will not appear on the "Central Administration" SharePoint 2010, Monitoring section or "Monitoring".

But when we try to activate happen that will indicate an error when checking SharePoint USLogs read the description of Access Denied Event ID: 6615. But do not worry our friend Paul Kotlayr to resolve the problem by running a script level SharePoint Power Shell 2010.

Here is the link: http://unclepaul84.blogspot.com/2010/06/sppersistedobject-xxxxxxxxxxx-could-not.html

So do not forget to enable the "feature" in the collection of sites that want run and run the script from Paul to remove access denied error even though you do with the Farm Administrator will not allow you to run but RemoteAdministratorAccessDenied change the value to false.

Until next time, SharePoint20104Fun!, Manolo Herrera