Reporting Synch jobs stuck in Waiting To be processed (Sleeping)

  • Follow


Hi, 

It seems that all my Reporting sync jobs are stuck in "Waiting to be 
processed (Sleeping) state.  All other jobs are processed OK.

I restarted the queue service, eventing service, SharePoint Timer, I even 
rebooted my 4 servers (2 WFE, 2 APP) more than once and it does not help.

I tried a Full refresh of the Reporting DB (twice) and the queue fills up 
with over 800 Reporting sync jobs that stay there until the Queue Cleanup.

There is nothing in the ULS logs, nothing in the EventViewer

I have SP2 and the October 2009 CU.

Any idea what else I could try ?

Thanks a lot for your help

Pat
0
Reply Utf 1/29/2010 4:37:01 PM

Have you searched the queue to find the job that is in queue postion 1?  It 
coudl be that that job failed and is blocking or is in the "getting queued" 
status.  If that is the case, you will need to cancel this job.

Jonathan

"PatLac" <PatLac@discussions.microsoft.com> wrote in message 
news:A16B9160-FBFB-4F2F-A2CF-2F8223222801@microsoft.com...
> Hi,
>
> It seems that all my Reporting sync jobs are stuck in "Waiting to be
> processed (Sleeping) state.  All other jobs are processed OK.
>
> I restarted the queue service, eventing service, SharePoint Timer, I even
> rebooted my 4 servers (2 WFE, 2 APP) more than once and it does not help.
>
> I tried a Full refresh of the Reporting DB (twice) and the queue fills up
> with over 800 Reporting sync jobs that stay there until the Queue Cleanup.
>
> There is nothing in the ULS logs, nothing in the EventViewer
>
> I have SP2 and the October 2009 CU.
>
> Any idea what else I could try ?
>
> Thanks a lot for your help
>
> Pat 

0
Reply Jonathan 1/29/2010 6:48:48 PM


Hi, 

Thanks for taking the time to respond.

I tried multiple times to cancel the first job but the next one or the next 
after gets stuck also.

"Jonathan Sofer [MVP]" wrote:

> Have you searched the queue to find the job that is in queue postion 1?  It 
> coudl be that that job failed and is blocking or is in the "getting queued" 
> status.  If that is the case, you will need to cancel this job.
> 
> Jonathan
> 
> "PatLac" <PatLac@discussions.microsoft.com> wrote in message 
> news:A16B9160-FBFB-4F2F-A2CF-2F8223222801@microsoft.com...
> > Hi,
> >
> > It seems that all my Reporting sync jobs are stuck in "Waiting to be
> > processed (Sleeping) state.  All other jobs are processed OK.
> >
> > I restarted the queue service, eventing service, SharePoint Timer, I even
> > rebooted my 4 servers (2 WFE, 2 APP) more than once and it does not help.
> >
> > I tried a Full refresh of the Reporting DB (twice) and the queue fills up
> > with over 800 Reporting sync jobs that stay there until the Queue Cleanup.
> >
> > There is nothing in the ULS logs, nothing in the EventViewer
> >
> > I have SP2 and the October 2009 CU.
> >
> > Any idea what else I could try ?
> >
> > Thanks a lot for your help
> >
> > Pat 
> 
0
Reply Utf 1/29/2010 7:14:20 PM

Pat – Your server environment might be blocking Reporting Synch jobs in the 
queue because it believes that an RDB Refresh is executing or has failed.  In 
this state, the system is reading a flag value (not = 0) from the reporting 
database MSP_Adminstatus table which tells the queue to block all reporting 
jobs.  Did anyone kick off an RDB refresh?  What is the blocking job in the 
queue?  If the RDB refresh failed, you need to determine why it failed and 
correct this because your reporting database and cube database will be out of 
synch.  Check for errors in your Server application eventlogs, ULS logs to 
determine the reason for failure.  There could be a corrupted project causing 
the failure.
Check the reporting database MSP_AdminStatus table – see link for details
http://msdn.microsoft.com/en-us/library/microsoft.office.project.server.library.reporting.refreshjobstatus.aspx
Check this blog – Brian Smith post information about clearing the 
MSP_AdminStatus table
http://blogs.msdn.com/brismith/archive/2007/02/28/my-queue-is-stuck-how-to-manage-your-queue-service-in-project-server-2007.aspx


"PatLac" wrote:

> Hi, 
> 
> Thanks for taking the time to respond.
> 
> I tried multiple times to cancel the first job but the next one or the next 
> after gets stuck also.
> 
> "Jonathan Sofer [MVP]" wrote:
> 
> > Have you searched the queue to find the job that is in queue postion 1?  It 
> > coudl be that that job failed and is blocking or is in the "getting queued" 
> > status.  If that is the case, you will need to cancel this job.
> > 
> > Jonathan
> > 
> > "PatLac" <PatLac@discussions.microsoft.com> wrote in message 
> > news:A16B9160-FBFB-4F2F-A2CF-2F8223222801@microsoft.com...
> > > Hi,
> > >
> > > It seems that all my Reporting sync jobs are stuck in "Waiting to be
> > > processed (Sleeping) state.  All other jobs are processed OK.
> > >
> > > I restarted the queue service, eventing service, SharePoint Timer, I even
> > > rebooted my 4 servers (2 WFE, 2 APP) more than once and it does not help.
> > >
> > > I tried a Full refresh of the Reporting DB (twice) and the queue fills up
> > > with over 800 Reporting sync jobs that stay there until the Queue Cleanup.
> > >
> > > There is nothing in the ULS logs, nothing in the EventViewer
> > >
> > > I have SP2 and the October 2009 CU.
> > >
> > > Any idea what else I could try ?
> > >
> > > Thanks a lot for your help
> > >
> > > Pat 
> > 
0
Reply Utf 1/29/2010 11:37:01 PM

Thanks, 

That fixed the issue. 

"Gerard Wojcik" wrote:

> Pat – Your server environment might be blocking Reporting Synch jobs in the 
> queue because it believes that an RDB Refresh is executing or has failed.  In 
> this state, the system is reading a flag value (not = 0) from the reporting 
> database MSP_Adminstatus table which tells the queue to block all reporting 
> jobs.  Did anyone kick off an RDB refresh?  What is the blocking job in the 
> queue?  If the RDB refresh failed, you need to determine why it failed and 
> correct this because your reporting database and cube database will be out of 
> synch.  Check for errors in your Server application eventlogs, ULS logs to 
> determine the reason for failure.  There could be a corrupted project causing 
> the failure.
> Check the reporting database MSP_AdminStatus table – see link for details
> http://msdn.microsoft.com/en-us/library/microsoft.office.project.server.library.reporting.refreshjobstatus.aspx
> Check this blog – Brian Smith post information about clearing the 
> MSP_AdminStatus table
> http://blogs.msdn.com/brismith/archive/2007/02/28/my-queue-is-stuck-how-to-manage-your-queue-service-in-project-server-2007.aspx
> 
> 
> "PatLac" wrote:
> 
> > Hi, 
> > 
> > Thanks for taking the time to respond.
> > 
> > I tried multiple times to cancel the first job but the next one or the next 
> > after gets stuck also.
> > 
> > "Jonathan Sofer [MVP]" wrote:
> > 
> > > Have you searched the queue to find the job that is in queue postion 1?  It 
> > > coudl be that that job failed and is blocking or is in the "getting queued" 
> > > status.  If that is the case, you will need to cancel this job.
> > > 
> > > Jonathan
> > > 
> > > "PatLac" <PatLac@discussions.microsoft.com> wrote in message 
> > > news:A16B9160-FBFB-4F2F-A2CF-2F8223222801@microsoft.com...
> > > > Hi,
> > > >
> > > > It seems that all my Reporting sync jobs are stuck in "Waiting to be
> > > > processed (Sleeping) state.  All other jobs are processed OK.
> > > >
> > > > I restarted the queue service, eventing service, SharePoint Timer, I even
> > > > rebooted my 4 servers (2 WFE, 2 APP) more than once and it does not help.
> > > >
> > > > I tried a Full refresh of the Reporting DB (twice) and the queue fills up
> > > > with over 800 Reporting sync jobs that stay there until the Queue Cleanup.
> > > >
> > > > There is nothing in the ULS logs, nothing in the EventViewer
> > > >
> > > > I have SP2 and the October 2009 CU.
> > > >
> > > > Any idea what else I could try ?
> > > >
> > > > Thanks a lot for your help
> > > >
> > > > Pat 
> > > 
0
Reply Utf 2/9/2010 4:09:01 PM

4 Replies
2087 Views

(page loaded in 0.081 seconds)

Similiar Articles:













7/27/2012 11:15:26 AM


Reply: