none
Problem with reporting database in Project Server 2007. RRS feed

  • Question

  • Good day.

    I have Project Server 2007 installed. I have transfered my sql server from 2005 to 2008. Then i decided to run Sharepoint Configuration wizard and it was my biggest mistake - it seems to clear reporting database. Now there is almost no data and  it's completely out of synch with published database.

    Can configuration wizard do that?

    Best regards,

    Chernobrivec

    Monday, September 5, 2011 12:21 PM

Answers

  • Hi Chernobrivec - the Reporting Database Refresh can be a long process and it is not obvious what is happening - it can look from the queue as if nothing is going on.  Take a look at http://blogs.msdn.com/b/brismith/archive/2011/07/14/project-server-2010-reporting-database-refresh-failing-with-large-resource-pools.aspx where I talk about the process that the re-build goes through - probably the section half way down the page will be most relevant in understanding what is going on - rather than the procise error.  It is very similar in 2007. If you stop and start services or the queue then you will likely break the flow that was working anyway - and you will need to start again. As mentioned above - the SharePoint configuration wizard would not have caused the reporting database to be cleared.

    If reading the blog, and re-starting the process again does not resolve things then best to open a support incident and we can help you through this.

    Best regards,

    Brian.


    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    • Marked as answer by Chernobrivec Saturday, September 17, 2011 6:12 PM
    Tuesday, September 6, 2011 9:16 PM
    Owner
  • Hi Chernobrivec.

    You may need to cancel the jobs & then rebuild the database by restoring custom fields objects. It will restore everything by rebuilding the database. You can use only custom fields to restore.

    Hope that helps.


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    • Marked as answer by Chernobrivec Saturday, September 17, 2011 6:12 PM
    Monday, September 5, 2011 1:19 PM

All replies

  • Hello there,

    As a process, It should not have done that. It seems that reporting database sync job was fired after the restore & couldnot get completed. You can check the Manage queue in Server settings & verify the Reporting sync job completion.

    You can try to rebuild the reporting database.

    1. Logon to Project Web Access with Administrator credentials
    2. Select Administrative Backup from the Database Administration secton on the Server Settings Page in Project Web Access
    3. In the Items for Backup section of the Backup page, select the checkbox for Enterprise Custom Fields and then click the Backup button and click the OK button when prompted by the system
    4. Select Administrative Restore from the Database Administration secton on the Server Settings Page in Project Web Access
    5. Choose Enterprise Custom Fields from the Choose Item selector on the Restore page
    6. Click the Restore button and then click the OK button when prompted by the system

     

    Allow time for the reporting rebuild job to run. You can track the state of this job on the Manage Queue page.
    Hope that helps.

    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Monday, September 5, 2011 12:44 PM
  • Good day.

    Thank you for your reply.

     

    There is many waiting jobs in queue but it seems that it's because of problem with reporting database.

    I didnt find any errors in logs so i dont know exactly why database was erased.

     

    Question about database rebuild - should i backup and restore all objects or only custom fields?

    Best regards,

    Chernobrivec.

    Monday, September 5, 2011 1:05 PM
  • Hi Chernobrivec.

    You may need to cancel the jobs & then rebuild the database by restoring custom fields objects. It will restore everything by rebuilding the database. You can use only custom fields to restore.

    Hope that helps.


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    • Marked as answer by Chernobrivec Saturday, September 17, 2011 6:12 PM
    Monday, September 5, 2011 1:19 PM
  • Good day.

     

    I killed all waiting jobs.

    Then i tried to backup custom fields, but job which should do it just hanged in state "waiting to be processed(sleeping)".

    Best regards,

    Chernobrivec.

    Monday, September 5, 2011 4:14 PM
  • HI , Have you tried re-starting the Project Queueing Service ? If nothing else blocks the Queue it should then start Processing.

     

    Andre


    http://av-epm.blogspot.com
    Tuesday, September 6, 2011 4:53 AM
  • I have made little mistake - backup and restore jobs are successful, but RBS jobs are in status waiting to be processed.

     

    Best regards,

    Chernobrivec

    Tuesday, September 6, 2011 7:59 AM
  • Tried restarting services - not helping.

    Best regards,

    Chernobrivec

    Tuesday, September 6, 2011 10:49 AM
  • Hi Chernobrivec - the Reporting Database Refresh can be a long process and it is not obvious what is happening - it can look from the queue as if nothing is going on.  Take a look at http://blogs.msdn.com/b/brismith/archive/2011/07/14/project-server-2010-reporting-database-refresh-failing-with-large-resource-pools.aspx where I talk about the process that the re-build goes through - probably the section half way down the page will be most relevant in understanding what is going on - rather than the procise error.  It is very similar in 2007. If you stop and start services or the queue then you will likely break the flow that was working anyway - and you will need to start again. As mentioned above - the SharePoint configuration wizard would not have caused the reporting database to be cleared.

    If reading the blog, and re-starting the process again does not resolve things then best to open a support incident and we can help you through this.

    Best regards,

    Brian.


    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    • Marked as answer by Chernobrivec Saturday, September 17, 2011 6:12 PM
    Tuesday, September 6, 2011 9:16 PM
    Owner
  • HI Brian,

    Just like to ask you something relating to above. If a job is "Sleeping"  as mentioned and have not worked or Processed for a couple of hours, and one just restarts the process as you have mentioned, what will then happen to the "Sleeping Jobs" wil lthey eventually be cleaned out ?

     

    Thanks

    Andre


    http://av-epm.blogspot.com
    Wednesday, September 7, 2011 5:11 AM
  • Good day.

    Thank you,Brian, for explanation.

    I will try to rebuild database again tomorrow and will tell the result.

    Best regards,

    Chernobrivec.

    Wednesday, September 7, 2011 12:50 PM
  • Hi Andre - sleeping jobs should just resume - usually they will wake every 5 minutes and check for certain conditions and then either carry on sleeeping - or start to process.  It is just when doing things beyond the queue such as cube building or the reporting database refresh where an interuption can stop things continuing as you might expect them to.

    Best regards,

    Brian.


    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Wednesday, September 7, 2011 2:42 PM
    Owner
  • Good day.

     

    Thank you all for help.

    I did again database rebuild and it helped.

     

    Best regards,

    Chernobrivec.

    Saturday, September 17, 2011 6:13 PM