Deploy 2010 Timer Job to 2013

I've inherited an environment that has a handful of custom solutions including two timer jobs. I have installed these solutions in my SP 2013 test environment and although they are deployed, they are not showing in the job definitions.
I fully expected to have to make some changes to be able to be use thesee in 2013 but I am not sure what I need to do to get those working. Any pointers? Is there something specifically in the solution that needs to change (BTW - I dont' have
a lot of Visio experience)

Have you activated your feature at your web application, feature that will register your job?
Once you deployed the WSP/Solution.Go to the Central Administration. Manage Web Application. Select your Web Application on which the Solution has been Deployed. Select Manage Features.Activate the feature.Check your job listed at Monitoring->Review Job
Definitions.
Thanks
Ganesh Jat [My Blog |
LinkedIn | Twitter ]
Please click 'Mark As Answer' if a post solves your problem or 'Vote As Helpful' if it was useful.

Similar Messages

Access denied error in feature receiver code when deploying-activating custom timer job feature

hi,
am creating a sp timer job for a updating a list.when i write this code in a the event receiver featureactivated method, and when i activate this feature , am getting access denied error.
but, when i deploy this timer job [ without feature receiver] through powershell, it works.
i didnt run this feature receiver with runwithelevatedprivileges delegate - i think this wlll NOT solve the issue.
from one of the posts i seen that, current logedin user needs to be part of config database roles. i didnt understand this point. how can i add my current loge din user into the sp_config database roles? is it through SSMS 2012?
or
is there any way to achieve without feature event receiver?
otherwise i will be forced to write my business logic in a console appln and add this exe in a windows scheduler.!
help is appreciated!

hi Waqas,
i have ran that powershell script you have pointed to me.
function Set-RemoteAdministratorAccessDenied-False()
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") > $null
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Administration") > $null
# get content web service
$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
# turn off remote administration security
$contentService.RemoteAdministratorAccessDenied = $false
$contentService.Update()
now i need to test the functionality from the event receiver after Activate feature button click.
BTW, i have written a console appln for my business logic and created an exe.
also, should i test it with a web application levels coped feature instead of site collection level feature? this thread talks abt the same:
http://social.technet.microsoft.com/Forums/en-US/f41810ec-2348-436d-a574-c29656f3a567/access-denied-error-when-running-timer-job-from-feature-activated-event?forum=sharepointgeneralprevious
thx

How to Create Custom Timer Job for SharePoint 2010 using Visual Studio 2010?

While creating timer job Visual Studio showing some kind of error and assembly issues.

Hi Aryav
Please provide the errors so that we can resolve your issue.
Meanwhile go through the step by step process of creation of Timer Job in the articles given below.
Create and Deploy Custom Timer Job Definition in SharePoint Programatically
Indul Hassan
Microsoft Community Contributor
http://www.indulhassan.com
You Snooze.. You Lose !!

Why my timer job is not running?

I have a server farm configuration with 1 web server, 2 app servers and 1 database server.
What i am trying to do from timer job is to loop through all web applications present in the server farm and perform some action against some web-applications.
I have timer job which is provisioned with web-application(central admin web app) and locktype as contentDatabse passed as parameter, and i have scheduled this job to run every 2 minutes. This timer job is provisioned by a feature which has a farm
scope.
My timer job never runs.
If i stop the SharePoint timer service running in the app servers my timer job runs. From this
blog i have came to know that "So, the first thing is that for a particular server to be eligible to run the job, it must be provisioned
with the service or web app associated with the job." And my app servers does not host the web applications.
My questions is.
1. Why is my timer job is trying to run from the app servers?
2. If i pass a web server while provisioning timer job is that correct? I think timer job becomes tied to particular server and removing/
taking it down may make the timer job not to run.
Thanks,
Mallikarjun
mallikarjun

Try to deploy the Timer job from Web Front end not Application server. And try to Activate from there only .
Thanks and Regards
Er.Pradipta Nayak
Visit my Blog
Xchanging

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

SharePoint 2013 My Site Cleanup Timer Job

Is the My Site Cleanup Timer Job responsible for deleting the User Profile or just the Mysite or both?
Are Profiles deleted after 14 days or is it some other number.
Is there any action that would extend this time frame
I am not able to find any 2013 specific articles on this nut there are many on 2010, is everything still handled the same way?

Hi，
The My Site Cleanup Job is responsible for deleting user profiles and My Sites of those users. This includes the following activities:
Remove user profiles that are queued for deletion.
If those users have a My Site, Email the manager letting them know that the user’s My Site will be deleted in 14 days.
11 days after the first notification, email the manager again letting them know that the My Site will be deleted in 3 days.
After a total of 14 days, delete the MySite.
Run the "My Site Cleanup" Timer job and check if the user profile that is marked as disable in FIM is deleted.(An important point to note is that this job
requires a My Site Host to be configured on the UPA, even if you are not using My Sites. )
If the My Site Cleanup Timer Job is disabled, we can clean up deleted users by the follwoing powershell:
Set-SPProfileServiceApplication $upa –PurgeNonImportedObjects $true
For more information about mysite clean up time job, refer to the followng articles:
http://blogs.msdn.com/b/kaevans/archive/2012/06/25/top-recommendations-for-managing-the-my-site-cleanup-timer-job.aspx
http://www.harbar.net/archive/2011/02/10/account-deletion-and-sharepoint-2010-user-profile-synchronization.aspx
https://sharepoint2013admin.wordpress.com/2013/11/19/my-site-cleanup-timer-job/
Best regards，
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Alert set through timer job is not working in sharepoint 2010 as expected

Hi,
I create the standard sharepoint alerts through timer job.
in my timer job, i loop through a list and based on the user value in the alert to field i create alert for the users and the condition for the alert are only when new items are created and something changes in the below view.
all the properties are set fine. Email triggered on new items additions and on specific daily or weekly summary.
The view filteration is not working at all:(
But after the timer job ran and set the alert, if i open the alert settings on UI and without changing anything if i click ok , then the view filteration is happening and alerts are working fine.
What is wrong here? is it a bug or anything am missing?
Aruna
try
SPList Configlist = web.Lists.TryGetList("Configuration");
foreach (SPListItem oItem in Configlist.Items)
ProfilePicker = oItem["ProfilePicker"].ToString();
ProfileViewer = oItem["ProfileViewer"].ToString();
string MIS = oItem["MIS"].ToString();
SPList list = web.Lists.TryGetList(ProfileViewer);
SPList ProfileList = web.Lists[ProfilePicker];
foreach (SPListItem oItem in ProfileList.Items)
frequency = oItem["Frequenzy"].ToString();
created = (DateTime)oItem["Created"];
string createdDate = created.ToString();
createdDate = DateTime.Parse(createdDate).ToShortDateString();
DateTime today = DateTime.Today.Date;
string dateonly = today.ToString(); ;
dateonly = DateTime.Parse(dateonly).ToShortDateString();
SPFieldUserValue fieldValue = null;
SPFieldUser UserColumn = (SPFieldUser)oItem.Fields.GetField("Alert_x0020_owner");
fieldValue = UserColumn.GetFieldValue(oItem["Alert_x0020_owner"].ToString()) as SPFieldUserValue;
if (fieldValue != null)
alertowner = fieldValue.User;
alert = alertowner.ToString();
//if (createdDate == dateonly)
SPUser user = web.EnsureUser(alert);
SPAlert newAlert = user.Alerts.Add();
newAlert.AlertType = SPAlertType.List;
newAlert.List = list;
newAlert.DeliveryChannels = SPAlertDeliveryChannels.Email;
newAlert.EventType = SPEventType.Add;
if (frequency == "Daily")
createDailyAlert(newAlert, list, user);
else
createWeeklyAlert(newAlert, list, user);
catch (Exception ex)
// Danfoss.Sharepoint.Logger.DanfossLogger.LogToOperations(ex, "Exception occurred in setting the profile alert", 0, EventSeverity.Error, DanfossExceptionCategory.General);
private static void createDailyAlert(SPAlert newAlert, SPList list, SPUser user)
newAlert.Title = "My Daily Profile viewer Alert";
newAlert.AlertFrequency = SPAlertFrequency.Daily;
newAlert.AlertTemplate = list.AlertTemplate;
newAlert.AlertTime = new DateTime(DateTime.Today.Year, DateTime.Today.Month, DateTime.Today.Day, 10, 0, 0);
newAlert.AlertTime = newAlert.AlertTime.AddDays(0);
SPAlert existingAlert = null;
newAlert.Properties.Add("filterindex", "4");
newAlert.Properties.Add("viewid", list.Views["Daily Alert"].ID.ToString("D"));
newAlert.Properties.Add("filterpath", string.Format("{0}/", list.Views["Daily Alert"].ServerRelativeUrl.TrimStart('/')));
foreach (SPAlert alerts in user.Alerts)
string al = alerts.AlertFrequency.ToString();
// Filter down the alert to the list you wish to report on.
if (al == "Daily")
// Found your existing your custom alert. Don't create one.
existingAlert = alerts;
if (existingAlert == null)
newAlert.Update(false);
private static void createWeeklyAlert(SPAlert newAlert, SPList list, SPUser user)
newAlert.Title = "My weekly profile viewer Alert";
newAlert.AlertFrequency = SPAlertFrequency.Weekly;
newAlert.AlertTemplate = list.AlertTemplate;
newAlert.AlertTime = new DateTime(DateTime.Today.Year, DateTime.Today.Month, DateTime.Today.Day, 10, 0, 0);
newAlert.AlertTime = newAlert.AlertTime.AddDays(0);
SPAlert existingAlert = null;
newAlert.Properties.Add("filterindex", "4");
newAlert.Properties.Add("viewid", list.Views["Weekly Alert"].ID.ToString("D"));
newAlert.Properties.Add("filterpath", string.Format("{0}/", list.Views["Weekly Alert"].ServerRelativeUrl.TrimStart('/')));
foreach (SPAlert alerts in user.Alerts)
string al = alerts.AlertFrequency.ToString();
// Filter down the alert to the list you wish to report on.
if (al == "Weekly")
// Found your existing your custom alert. Don't create one.
existingAlert = alerts;
if (existingAlert == null)
newAlert.Update(false);
This is my code. alerts are not sending based on the view:(

Hi sathyaav,
I followed the example and made a test in my environment, it works like a charm.
I suggest you check if you have inputed the valid site URL when you create the project solution.
If you deployed succeed in the Central Administrator Site using Visual Studio, then the job named "Simple Job Definition" will appear in the job definition list.
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Zhengyu Guo
TechNet Community Support

Project Server 2013: Synchronization of AD with security groups - missing from list of timer jobs

I have same problem in:
http://social.msdn.microsoft.com/Forums/en-US/2b916bb9-2277-4c53-8b97-271a912414ba/ps2013-timer-job-missing-quotproject-server-synchronization-of-ad-with-security-groups-forquot
"I cannot find timer job in SPS central administration "Project Server: Synchronization of AD with security groups for <PWAIntanceName>" to schedule synchronization. Enterprise Resource Pool synchronization working fine and timer job
"Project Web App: Synchronization of AD with the Enterprise Resource Pool job for <PWA site name>" exist on server."
Don't offer solution for "Schedule Enterprise Resource Pool synchronization".
Only "Timer job in SPS central administration "Project Server: Synchronization of AD with security groups".
Have a solution?

Project Server timer job "Synchronization of AD with security groups" don't exist.
So I created job in Task Scheduler of Project Server OS, that every day start PowerShell-script:
if ((Get-PSSnapin | where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null)
Add-PSSnapin Microsoft.SharePoint.PowerShell
Invoke-SPProjectActiveDirectoryGroupSync –Url http://project/pwa
Security groups of Project Server automatically synchronize with groups from AD!
http://technet.microsoft.com/en-us/library/jj219472.aspx

InfoPath Forms Services Form Upgrade timer job continuously failing

Hello all,
We've recently uploaded several InfoPath form templates to our production SharePoint 2010 environment (6 server farm). One of the forms
was still stuck in 'upgrading' (even after it said successful after the upload). So we deleted that form and re -uploaded it successfully.
Since then we've been seeing the following timer job failures every minute. The forms all work but the timer job failures still keep
coming.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Execute method of job definition Microsoft.Office.InfoPath.Server.Administration.FormsUpgradeJobDefinition (ID 6904b095-822d-4158-9572-f6b3fe8d4265)
threw an exception. More information is included below.
Object reference not set to an instance of an object.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We saw this
http://gpkarnik.wordpress.com/ looks hopeful, but we are reluctant to proceed when we read this article
http://blogs.technet.com/b/nishants/archive/2008/10/10/how-to-delete-orphan-configuration-objects-from-sharepoint-farm.aspx
We have done the following:
Reset timer service on all servers (same job just moves to a different server failing)
removed the suspect InfoPath form and re uploaded (no change)
All servers in the farm rebooted (no change)
Questions:
Can we just get rid of the failing InfoPath Forms Services Form Upgrade?
Will a new one get created the next time we upgrade a form?
Thank you,
Jim

Hi Jim,
When you upload an administrator-approved InfoPath form template to SharePoint, SharePoint automatically creates a Solution Package for it as well as a Timer Job. When a solution package is deployed in a farm, it will be restored in 14 hives.
Timer jobs are scheduled for execution, but sometimes it can take a long while before a SharePoint timer job gets executed. The timer job created by SharePoint would have a Title similar to Windows SharePoint Services Solution Deployment for “form-[your_uploaded_form_template_name].wsp”.
The Schedule Type for this timer job would be One-time.
If you want to hurry the execution of administrative timer jobs along, you can use the following stsadm command:
stsadm -o execadmsvcjobs
More information, please refer to the link:
http://www.bizsupportonline.net/blog/2008/12/infopath-form-uploaded-sharepoint-remains-stuck-installing-upgrading-status/
http://johnliu.net/blog/2013/1/8/infopath-form-stuck-on-installing-upgrading-or-deleting.html
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Is there a relationship between InfoPath and the "Solution Approval" and "Solution Unpublish" timer jobs?

One of our developers has a test SP 2010, service pack 2 system. Against it, he is testing form library InfoPath 2010 applications that he is developing.
There are, over the 2 months he has been working, an increasing number of times that the machine becomes so slow as to be unusable. For instance, in his attempt to publish an updated form this morning, the publish time was about 2 hours.
I see nothing obvious in the event log.
However, in the 5.7 million line 14 hive log, there are 5.6 million lines of the form:
Solution Deployment : Deleting directory C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\FT-01-6d499aed-f899-c88e-5f7e-8dad243ccaf1\solution.xsn.1.0.0.1018.1.0.0.735. Delete if not empty. ae8f490c-f1bf-4f25-92aa-6fc8e0de7de5
When I look in the Features subfolder, there are over 13k of folders containing a solutions.xsn and a DLL with the name of the application.
These folders date back to when the work began.
When I look at timer job history , all I see are status of Succeeded.
But I do notice that every minute a series of 6 Solution Approval and 6 Solution Unpublish timer jobs run.
Since the timer says to run every minute, I suspect that something is wrong with the jobs.
This being a test machine, there is no reason to have 13k of old copies of the form and dll. He is not going back to one of those as far as I am aware.
Is there some action that he should be taking that should be "cleaning up" this situation?
Is there something that a SP admin could do to clean things up so that things no longer take so long to run and create such large log files?
Thanks for your ideas.

Try using this document to locate the tag: http://goo.gl/GDeRb
It could have worn off, depending on how long you have had the notebook and what kind of conditions it has been through.
Also, where did you happen to purchase it from?
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

Is there a way to change the Recurring Schedule of timer job Expiration Policy in SP online ?

I'm using SharePoint Online. I want to run a rule every day on the items of a list.
To do this, I went into Information management policy settings
of my list and enabled Retention. There, I added a daily event and set the
Recurrence to 1 day.
After 24 hours, nothing occurs.
I guess the default schedule for the Information management policy
and the Expiration policy timer jobs are set to 1 week (as is the case for 2010 and 2013 on premise versions) but I'll have to wait a couple of weeks to be sure.
Does anyone know how to change this setting ? any workaround ?
Thanks !

Nope, none i can think of. We have no control over that level of behaviour within SharePoint and have to accept the MS standard offering.

How to update the lists using the timer jobs?

Hi,
I'm new to sharepoint developing
Using the timer jobs the items which are present in the one list must get updated in the another list and also should be overwritten.
For example:
If there 10 items present in a X list. After some time period the first five of X should get updated in Y list . After some more time the next 5 items of X has to overwrite the items present in the Y list.
Regards,
Santto.

Hi Santto,
The following articles and code examples would be helpful.
SharePoint 2010 Custom Timer Job
https://code.msdn.microsoft.com/office/SharePoint-2010-Custom-416cd3a1
SharePoint Add/Update/Delete List Item Programmatically to SharePoint List using C#
http://www.sharepointblog.in/2013/04/add-new-list-item-to-sharepoint-list.html
Best Regards
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Migrate Inplace Custom Timer Job to Online

Hi All,
I am pretty new in SharePoint Online, we have planned to migrate all SharePoint 2010 In-place contents to SharePoint Online. We have few timer jobs deployed in our farm and do not have access to Online servers to migrate custom timer jobs.
Hence what should be the best strategy to migrate these?
Regards,
Ripon Kundu

Timer jobs cannot be migrated or created in Office 365. You do not have the access to run those things.
You'll have to re-design your solution.

Force immediate alerts timer job to run on a particular server

In Central Admin->Manage Content Database->Preferred server for timer jobs says "Not selected". We have 2 WFE servers, server1 and server2. server1 currently is not able to connect to the smtp server so we would like for the immediate
alerts timer job to be executed on server2 which has access to smtp. I know I could set the preferred server for timer jobs to be server2 but that would mean that all timer jobs would execute on that server.
I have a few questions:
1. Is there a way to force just immediate alert timer job to run on server2?
2. How can I find out which server is currently processing the immediate alerts timer job (or which server processed the last immediate alerts timer job)
3. If I force all timer jobs to execute on server2, how much of an effect does it have on the server in terms of RAM, CPU and other resources?
thanks,

What i believe is, alerts timer jobs is ContentDatabase Locktype so if you select the prefred server from the Central admin.
I am sure, all the timer jobs which having the ContentDB lock type will run on preferred server.
Note that content database locks are handled at the server and database level, not at the individual job level.
The Article Trevor mentioned is great for explanation.
2.) you can check it from the Central admin > Monitoring > Job History and from here select the job definition which history you want
to see.
3)you forcing all timer jobs in one server that's mean you are increasing the over head for that server so performance may be issue. Its depend how many user / load you already have
on the server. another thing, may be deadlock between the jobs i.e if one job took more time and other jobs wait for it ends up skipping it.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

SharePoint Timer Jobs and 3rd Party DLLs

I have a custom built timer job that references a third party DLL. Currently, I have the 3rd party DLL stored in the GAC along with the timer job and all works fine. Our client however, does not want the third party DLL in the GAC. As such
I want to put it in the bin folder associated with the SharePoint Central admin port.
When I deploy the solution, I do see that the third party DLL was copied to the bin folder. I did restart the SharePoint timer service. When the timer job runs, it complains that it cannot find the third party DLL.
Is it possible for a timer job running in the GAC to access DLLs in the bin folder? If so, do I need to modify CAS policies in order for it to work?
Saul

CAS policies are deprecated (and all solutions in 2013 are Full Trust). I believe the DLL needs to be in the GAC.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Deploy 2010 Timer Job to 2013

Similar Messages

Maybe you are looking for