I am trying to develop a timer job that is deployed at Farm Level. can anyone point me to an example of how to deploy it?
(I am looking for code in FeatureActivated and deactivated event)
View Complete Post
I'm trying to create a custom document library template at farm level, as I want to template to be available in all the sites I create.
The thing is that I'm not sure if I'm taking the correct approach. I just need a standard document library with 3 additional columns (Metadata) 2 text fields and one date field. I will then add a document library of this type to a custom site template I've
already created. (So instead of list with Type '101' I will use my custom 10055 library.
The way I'm trying to do this is:
1. I make a copy of the FEATURES\DocumentLibrary folder of my installation. So now I have FEATURES\CustomLibrary folder
2. I create an empty SharePoint project in Visual Studio 2010 and map the TEMPLATE folder, and the I add CustomLibrary folder and all the files and subfolders in it.
3. I edit the feature.xml, and add a newly generated GUID
4. I make the modifications I need to the other xml files included in the DocLib and SiteTemplates subfolders. (Type=10055, etc..)
5. I right click on the solution and deploy.
After this, I can't see my custom library when I try to create a new item in my sites.
One thing I don't understand is why the OOTB DocumentLibrary feature has HIDDEN = true in the feature.xml file. Anyway I've tried both in my custom template, but
I created a timer job based on Andrew Connell's tutorial. I ran this timer job on my development server, and it works perfectly. When I deployed it to our testing server, which is a multi-server farm with one wfe, it doesn't seem to work.
Here is what I have tried so far to get the timer job to work on our test server, based on other posts in this forum, and other tutorials I read on the web.
I assume that since this is the first time writing a timer job, I am obviously missing something that my solution needs to run on a multi-server farm. I even played with the SPJobLockType, but no luck, it is currently set to ContentDatabase. Do I need to
add code that tells my timer jo
Is it possible to have a custom timer job provisioned at the site collection level? In writing my custom spjobdefinition, it looks like you can only create the timer job at the web application level:
public KBRankingTimerJob(string jobName, SPWebApplication webApplication)
: base(jobName, webApplication, null, SPJobLockType.ContentDatabase)
this.Title = jobName;
My feature receiver is defined as a site collection feature, so I can activate it at a site collection level, but my timer job is being provisioned and running once for each content database within the web application (it seems). I'd like the timer
job defined for just one particular site collection (the one the feature receiver is activated at). Is this possible? Or am I stuck at the web app level?
If I am stuck at the web app level, how has anyone created a timer job to run against 1 particular list within a site?
I've created a custom BCS solution in VS2010, for SP2010, it's based on a .net assembly and in dev/test it all works fine.
Unfortaunetly, when I package it for production, although it deploys successfully - or so everything says - if I look in Central Admin for the BDC model, it's not there!
Has anybody else come across the same issue?
Please let me know what other information you might need.
MSDN Magazine February 2001
I was unable to register a custom timer job in Moss 2007 using both the web interface via feature activation event as well as through code by taking the instance of the timer job class in a custom web part where i manage the custom timer
The same above case was working fine in a different environment.Could you please help by listing out the reasons/solutions/work around.
This is very critical and urgent as i was deploying the same in production.Thanks in advance.
I have scheduled a custom timer job to run for weekly two times using the spschedule. the string used in the feature event was
"weekly between tue 23:00:00 and thu 23:00:00"
But the problem is i have the job is running only once with the above schedule.How can i run the job twice a week on specific days.
Please share your ideas/solutions to run the custom timer job in MOSS as per the above schedule.