We have a similar problem where we run execadmsvcjobs and it doesn't list any jobs as being run e.g. "Excuting . Operation completed successfully."
But if I go into Central Administration | Operations | Solution Management, it states that there is a solution on status of 'Deploying(scheduled at 3/13/2008 11:06 AM )'. Which is obviously in the past. Going to Central Administration | Operations | Timer Job Definitions, there is a Job in there called 'Windows SharePoint Services Solution Deployment for '<solutionname>.wsp'' and viewing that job definition states that last run time was 'N/A'. This may be different server farm jobs, but sounds like a similar issue. Overnight, these jobs seem to clear and the status of the Solution goes to deployed. Is there a way to kick start that? On 3/13/08, Prior, David <[EMAIL PROTECTED]> wrote: > > All, > > Thanks for the help. > > My service account is running with the correct account settings. > > I hadn't used the *STSADM* command with the *execadmsvcjobs* argument > before so I'll give that a whirl. > > Cheers, > > *David * > ------------------------------ > *From:* Gerald De Run [mailto:[EMAIL PROTECTED] > *Sent:* Thu 13/03/2008 11:39 AM > *To:* Prior, David > *Subject:* RE: [OzMOSS] Timer Tasks not running > > David, > You can force the timer jobs to run on an individual server in a MOSS farm > using the STSADM command-line: > STSADM -o execadmsvcjobs > Gerald de Run > > ------------------------------ > From: Prior, David <[EMAIL PROTECTED]> > Sent: Thursday, 13 March 2008 10:33 AM > To: [email protected] <[email protected]> > Subject: [OzMOSS] Timer Tasks not running > > Hi, > > I'm experiencing some very slow executions of Timer Tasks that are created > by MOSS during the initial configuration of the farm and the starting of > services. These are *not* custom tasks. > > On one farm they run within a minute, but on the other farm they seem to > take anywhere from an hour to lots longer (I left it running overnight and > the task still hasn't run). They are all scheduled as "One-time" tasks. I > can see in the Timer definitions that things are running, it's just not > picking up the "one-time" tasks. > > Is there a way to "kick off" the tasks. This is holding up my efforts for > configuring the farm and getting everything running since I have to wait for > the tasks to run before I can complete the next stage. > > My topology is all 64bit hardware running Win 2003 server and SQL 2005. > > 1 x Index Server > 2 x WFE (Query) > 2 x SQL (clustered) > > Any help would be appreciated. > > Cheers, > > *David * > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
