Why custom Sharepoint 2010 timer Job doesn't run?

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • hemantbasva
    New Member
    • Oct 2008
    • 12
    #1

    Why custom Sharepoint 2010 timer Job doesn't run?

    I have created a custom timer job using Visual Studio 2010 ultimate and have deployed the same in Sharepoint 2010 environment.

    The timer job is deployed successfully but the problem is it not running. the The last run time it is showing is NA.

    Since its a sample timer job it logs event into event viewer..

    The article i used to create this timer job is as follows

    http://dotnetfinder.wo rdpress.com/2010/07/24/creatingcustomS harePointtimerj ob2010/

    Even if i click on "Run Now" button then also it is not running. tried to check LOg file also on 14 hive structure but could not find anything...

    Pls assist
    Tags: sharepoint 2010, sharepoint 2010 timer job, timerjob, timerjob sharepoint 2010
    • Megaroutex
      New Member
      • Oct 2011
      • 1
      #2
      Hi Hemantbasva - I'm having the same problem, once we promote the custom timer job to our tst box it just doesn't run at all even though it's there as a scheduled job, nothing in sharepoint 2010 logs or event logs - is well weird!

        Comment

        • hemantbasva
          New Member
          • Oct 2008
          • 12
          #3
          @Megaroutex :run all timerJob using powershell script.....

          Code:
          Start-SPAdminJob [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]
          Have a look at
          Start-SPAdminJob (Microsoft.SharePoint.Powershell)
          http://technet.microsoft.com/en-us/library/ff607833.aspx
          Use the Start-SPAdminJob cmdlet to execute all administrative timer jobs immediately rather than waiting for the timer job to run. When the service account for the SharePoint Administration service (SPAdminV4)) is disabled (necessary in some installations for security reasons), the Start-SPAdminJob cmdlet must be run on all computers to perform administrative task like provisioning. When you run this cmdlet in person (not in script), use the Verbose parameter to see the individual administrative operations that are run. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at SharePoint Server Cmdlets.
          Last edited by Niheel; Oct 5 '11, 10:24 AM.

            Comment

            Previous template Next
            Working...