Project Server 2007 Cannot update Reporting Database

L

Luis Mata

Hi Team

In this moment I have a problem with my reporting Database, this don´t
update from the Publishing DB from 22/09/07 aprox. 3 weeks a go.

I review all about the queue, restart the Server and nothing is happened, I
try to Cancel Any Jobs, but the Data about the Timesheet is maintened in this
queue.

I suspect that the problem is with the Timesheet queue, another jobs from
Project Server for example Update the Cube, is working perfect but with data
from the Reporting DB is show without change.

I need your help....

Luis Mata
 
L

Luis Mata

Gary:

Al projects are published, and all the people report his Task and
Timesheet's, but the problem is that all the data from Timesheet reported
after 23/09 to now don't show in reporting Database and consequent in Cubes
EPM Timesheet for example.

I watch in cube EPM Timesheet the data before 23/09, I retry to rebuild the
cubes and the status to he process of generation is Correct.

And I restart each day the Cube Services and Events Services.
 
G

Gochberg

Gary:

Al projects are published, and all the people report his Task and
Timesheet's, but the problem is that all the data from Timesheet reported
after 23/09 to now don't show in reporting Database and consequent in Cubes
EPM Timesheet for example.

I watch in cube EPM Timesheet the data before 23/09, I retry to rebuild the
cubes and the status to he process of generation is Correct.

And I restart each day the Cube Services and Events Services.

:





- Show quoted text -

Hi Luis,

Have you tried to use the Cancel Jobs Getting Enqueued option when
working with the queue? It is on the Manage Queue Page within
Advanced.

Good luck,

Dave G.
 
L

Luis Mata

Hi Gochberg

I cancel the fisrt Job's but this queue maintenance equal. I don't like lost
of Data from My Users, I need try another solution before make this option.

Can you help me with another option?

Luis Mata
 
J

Jonathan Sofer

Luis,

If you set the advanced option on for "Cancel jobs getting enqueued" and
unselect the "Cancel subsequent jobs in the correlation" then the only job
that will be cancelled is the one you selected which is the job stuck in the
state of "Getting queued". All other jobs should then process successfully
and you will not lose any data assuming the other jobs process without
issue. You will lose the one job that was stuck in "Getting queued" but
there is no getting around that.

Advanced Options:

Cancel jobs getting enqueued
Cancel subsequent jobs in the correlation


Jonathan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top