Custom developed solution called Timer2013.wsp. This solution has been globally deployed and activated as site feature. This Timer Job is supposed to copy data (items) between 2 lists. Expected behavior is farm solution
Timer2013.wsp with its Timer Job as a feature will be successfully deployed on production farm and copy list items between lists. This solution worked fine on version 2010 after SharePoint ungraded to 2013 this solution fails.
(Visited 76 times, 1 visits today)
And your question is …?
Perhaps you wander why it fails after the upgrade to 2013? Could be many things. Do you have any logging available for this custom solution? Do you have the source code? Then you’ll find more insight about what’s happening.
BTW, Kinda strange that a timer job is activated as a site feature, whereas timer jobs act at the level of a webapplication.
(Visited 1 times, 1 visits today)
