none
Status Update Queue Job failing RRS feed

  • Question

  • Using 2010: Currently we are seeing issues where auto-approval of submitted hours for tasks on one specific project is persistently failing in the queue. This goes for both old tasks and new tasks on that particular project, while task updates from other projects are working just fine. The ULS log just states that 'StatusApproval failed at Message 3', which when searching the net is not very helpful.

    Maybe we are missing something, but after searching the net for quite some hours we are none the wiser. One clue is that the publishing and check-in of the project seems to take a bit longer than for other projects. We suspected that some data somewhere is not in sync for this project, but restoring the project from an older backup did not help the issue. How can we even start to unravel what the issue might be and get it resolved?

    We are tempted to just recreate the project from scratch, but that is not really a good way to proceed. Any help is appreciated and also if anyone knows of some good resources for resolving similar issues we would be grateful.

    Regards,
    Stig

    Thursday, September 16, 2010 1:11 PM

Answers

  • We had already suspected that there might be some issues with the calendars (based on the message). What we had seen here was that one of the resources used a base calendar that is not one of our enterprise calendars. Instead of calendar X as it should be the field refers to calendar X1. But we also see that on other projects and updates for these projects works fine.

    However, by checking data in the tables, we saw that there was a difference between what was stored in the Draft database and the Published database. In the table MSP_PROJECT_CALENDARS the draft database referred to calendar X while the Published database referred to calendar X1. These should of course be the same.

    So, deciding that some data somewhere causes this difference we decided to try this approach: Save the project in Project Pro to a local .mpp-file, then delete the project from both the Draft and Published databases and finally to open the .mpp-file in Project Pro and save this to the project server. After having done this we were able to update tasks for this project with actual hours without the jobs failing. So in reality the problem is resolved, but we still do not know what caused it.

    We are however considering adopting this as a standard way to resolve issues that cannot be easily resolved otherwise. Before doing so we do need to know what risks are inherent in using this method. So if anyone has some information on what might be lost by this we will appreciate that.

    Another issue is still why the 'extra' calendards are being introduced. We saw this also when saving the .mpp-file by checking the base calendars for the resources. When off-line we managed to change the base calendar to X, but once saved to the server it reverted to X1. Since the main problem here is resolved I will open another thread to discuss this.

    Thanks and regards,
    Stig

    • Marked as answer by Stig Tuesday, September 21, 2010 2:21 PM
    Monday, September 20, 2010 11:21 AM

All replies

  • Hello Stig,

    Look into your Windows event logs and Security logs and see if an service account is locked or something.  Also using the ULS logs, look at the date and times when problem is occuring and compare with events that are happening in you windows events log.

    Also, if you turn on SQL Profiler, and perform the action, you may find what is happening on SQL.  You should see events login in or failing to login in.  If nothing is coming into SQL, find out why>\?

    Cheers!

    Michael Wharton, MBA, PMP, MCT 


    Sincerely, Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA www.WhartonComputer.com
    Thursday, September 16, 2010 2:30 PM
    Moderator
  • Hi Michael,

    thanks for quick response. As updates are working for all but one project it is unlikely that there is a lockout. Anyway, we changed the diagnostic logging for sharepoint to include everything from 'Warnings' and upwards to ensure we had project server events included, but we have absolutely nothing in the event log for this.

    After one of these messages I tried editing the project in PWA and was told it was out of sync. I clicked on Sync and the Sync job then also failed. What we found in the ULS log for that was (still nothing in event log):

    PSI: [ProjectServerError] Mismatched Attributes for PSErrorID ProjectSyncProjectEnterpriseEntitiesFailure. List of defined attributes: none. List of provided values: c038a835-160a-4aeb-9bdc-95619bc40f63, 1ee7857b-cde3-4274-a98e-2e6615424a44, 5, System.NullReferenceException: Object reference not set to an instance of an object.   
     at Microsoft.Office.Project.DataEdit.Assignments.AssignmentCalendarUpdateHelper.ConvertActualContourToElapsed(CturWork workContour, DateTime dtStart, CalendarShiftReader workTimeMap)   
     at Microsoft.Office.Project.DataEdit.Assignments.AssignmentCalendarUpdateHelper.ConvertActualContourToElapsed(Guid assnUid)   
     at Microsoft.Office.Project.DataEdit.Assignments.AssignmentCalendarUpdateHelper.RecalcContours(IEnumerable`1 assnUids)   
     at Microsoft.Office.Project.Server.BusinessLayer.ProjectMain.ConvertAssignmentContoursToUpdatedCalendarsInternal(PlatformContext context, Guid projGuid)   
     at Microsoft.Office.Project.Server.BusinessLayer.ProjectMain.ConvertAssignmentContoursToUpdatedCalendars(PlatformContext context, Guid projGuid, Int32& revisionCounter)   
     at Microsoft.Office.Project.Server.BusinessLayer.ProjectUtility.ProjectUpdateHandler.UpdateEnterpriseEntities(Guid projectGuid)   
     at Microsoft.Office.Project.Server.BusinessLayer.ProjectUtility.ProjectUpdateHandler.UpdateEnterpriseEntitiesAndSaveProject(Guid projectGuid)   
     at Microsoft.Office.Project.Server.BusinessLayer.Queue.ProcessSyncProjectEnterpriseEntitiesMessage.HandleSyncProjectEnterpriseEntitiesMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext)   
     at Microsoft.Office.Project.Server.BusinessLayer.Queue.ProcessSyncProjectEnterpriseEntitiesMessage.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext).

    Something with the assignments for this project that does not return an expected value.

    Any help is appreciated, Stig

    Thursday, September 16, 2010 3:18 PM
  • Stig:

    Something to try: First Delete the local project active cache on the workstation and then delete the project from the published database only. Then retry publishing the project and let us know what happens.


    Gary Chefetz, MCITP, MCP, MVP msProjectExperts
    Project and Project ServerFAQs
    Project Server Help BLOG
    Friday, September 17, 2010 12:32 PM
    Moderator
  • Gary,

    tried the exact workflow you suggested. Status Update from Task Update still fails with same error and leaves the project in a checked-out status.

    More tips appreciated.

    Stig

    Friday, September 17, 2010 1:23 PM
  • Hi Stig,

    From the error it is trying to do something with calendars and the contour and failing - and NULLReference exceptions normally mean there isn't some entity where it expects there to be one.  Worth checking the calendars in use on this project (and resource and task) and if all else fails then a support incident may be your next best bet to get this resolved.

    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
    Friday, September 17, 2010 9:36 PM
    Owner
  • We had already suspected that there might be some issues with the calendars (based on the message). What we had seen here was that one of the resources used a base calendar that is not one of our enterprise calendars. Instead of calendar X as it should be the field refers to calendar X1. But we also see that on other projects and updates for these projects works fine.

    However, by checking data in the tables, we saw that there was a difference between what was stored in the Draft database and the Published database. In the table MSP_PROJECT_CALENDARS the draft database referred to calendar X while the Published database referred to calendar X1. These should of course be the same.

    So, deciding that some data somewhere causes this difference we decided to try this approach: Save the project in Project Pro to a local .mpp-file, then delete the project from both the Draft and Published databases and finally to open the .mpp-file in Project Pro and save this to the project server. After having done this we were able to update tasks for this project with actual hours without the jobs failing. So in reality the problem is resolved, but we still do not know what caused it.

    We are however considering adopting this as a standard way to resolve issues that cannot be easily resolved otherwise. Before doing so we do need to know what risks are inherent in using this method. So if anyone has some information on what might be lost by this we will appreciate that.

    Another issue is still why the 'extra' calendards are being introduced. We saw this also when saving the .mpp-file by checking the base calendars for the resources. When off-line we managed to change the base calendar to X, but once saved to the server it reverted to X1. Since the main problem here is resolved I will open another thread to discuss this.

    Thanks and regards,
    Stig

    • Marked as answer by Stig Tuesday, September 21, 2010 2:21 PM
    Monday, September 20, 2010 11:21 AM
  • Hello Stig,

    I have experienced the same issue, resolved the issue as below.

    Opened the project plan in project pro --> Saved the plan as MPP using "Save For Sharing" option --> Later open the plan from the stored location -->Save As on the same name (It will overwrite the plan)

    This is similar to your method, but the best method due to the following reason.

    These steps will retain the project GUIDs, so the project links will not be broken. Timesheet entries and Task histories will be retained.

    Most of the cases if you import projects from MPP, it will try to import the local resources & calendar to the server.

    Did you enable the option to import calendar from MPP? If yes, remove it in server settings.


    Cheers. Happy troubleshooting !!! Sriram E - MSFT Enterprise Project Management
    Tuesday, September 21, 2010 3:12 AM
    Moderator
  • Hi Sriram, thanks for the answer.

    However what you descibe seems as 2007 and we use 2010. In 2010 there is no 'Save for Sharing' option (at least I cannot find one).

    In Project Server 2010 the option for 'Allow projects to use local base calendars' is switched off. This is the only option that seems related to this.


    Regards, Stig
    Tuesday, September 21, 2010 8:12 AM
  • Hi Stig,

    The Save for Sharing option in Project 2010 can be found here (only for checked-out enterprise projects)

    File -> Save & Send -> Save Project As File -> Save for Sharing

    I hope this helps,
    Hans


    My EPM blog: Projectopolis
    Tuesday, September 21, 2010 8:22 AM
    Moderator
  • Thanks, Hans. My bad, should have checked there as it is quite logical.

    Anyway, even when having done so the problem with the base calendar persists. So it looks like the correct enterprise calendar is not saved with the file even with this option.


    Regards, Stig
    Tuesday, September 21, 2010 8:42 AM