locked
Unexpected error on Tasks page RRS feed

  • Question

  • Hi,

    I ran just into the issue of "Unexpected Error" on Tasks page for one user. My normal ways of resolving this issue do not work. Booking Type is set to Proposed for this user in all projects. So no tasks are supposed to be displayed. Normally, this helps to identify assignment, which is causing trouble. Not this time.

    I have also checked if there are inconsistancies in published DB with following query:
    SELECT MSP_PROJECTS.PROJ_NAME
         , MSP_ASSIGNMENTS_SAVED.TASK_NAME
         , MSP_RESOURCES.RES_NAME
         , MSP_ASSIGNMENTS_SAVED.ASSN_UID
         , MSP_ASSIGNMENTS_SAVED.PROJ_UID
         , MSP_ASSIGNMENTS_SAVED.TASK_UID
         , MSP_ASSIGNMENTS_SAVED.RES_UID
         FROM MSP_ASSIGNMENTS_SAVED INNER JOIN MSP_PROJECTS
         ON MSP_ASSIGNMENTS_SAVED.PROJ_UID = MSP_PROJECTS.PROJ_UID INNER JOIN
         MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID = MSP_RESOURCES.RES_UID
         WHERE (NOT EXISTS(SELECT TASK_UID
         FROM MSP_TASKS_SAVED
         WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID))

    But no result, this should be fine.

    No errors in ULS, which could lead me to the root cause.

    Does anyone have an idea, what else I could check? It seems, that view settings of user got corrupted in some way.

    Any idea welcome!

    Thanks in advance
    Barbara

    Thursday, August 9, 2012 1:10 PM

Answers

  • Hi,

    just an update, nearly one year later. I solved this issue, and forgot completely my own question.

    Since I did not want to edit DB directly, I finally found a solution.

    - make sure, that no-one is working during the following procedure
    - get a list of all projects, user is team member of or has assignments
    - get a list of all projects, user is project owner or status manager within project. change project owner and status manager temporarily to any other user. publish
    - take an administrative backup of users and resources (just in case)
    - delete resource with Server Settings - Delete Enterprise Objects
    - recreate resource in exactly the same way (name, account, permissions, ...)
    - open all projects as found with first step. Save them and answer the question for replace local resource by enterprise resource with yes. publish
    - change status manager and project owner to original user. publísh

    It is some effort, but it did work in my case.

    Regards
    Barbara

    Tuesday, July 9, 2013 1:09 PM

All replies

  • Hi Barbara,

    The only other thing I can think of is to execute the follow query against the published SQL database and ask the user to retest in case it is an SQL timeout.

    exec sp_updatestats

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com

    Thursday, August 9, 2012 1:59 PM
  • Hi Paul,

    nice idea, thank you! But without any effect.

    I know somebody, who solved this issue by deleting resource and recreation. However, Timesheets are used for billing and resource is PM of several projects, so that is definitely no way I want to go.

    Any other idea (beside deletion) is welcome - I am lost.

    Regards
    Barbara

    Thursday, August 9, 2012 5:26 PM
  • Hi Barbara,

    Has the logging level been changed on the farm, I would expect something to be written to the ULS logs. Might be worth setting verbose logging on the trace log while investigating this issue to see if anything is logged then.

    Thanks

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com

    Thursday, August 9, 2012 6:37 PM
  •  

    Since issue is user specific, I think scenarios may result in to “Unexpected error” message scenario

    a. Duplicate Assignment Owners on the same task

    b. This can occur when the page takes longer than 30 seconds (default timeout) : this could also happen to specific user if he has more tasks to be listed as compare to working user

        As paul recommended Updating DB statics may help to address timeout issue if little tweak is needed, if not you may need to increase timeout value

    c. Missing Enterprise calendar ( If issue is being experienced by other users belongs to same project as affected user)

    d. Corrupted task

    e. Orphan records: Which you have already verified

    My apologies for the intrusion


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Thursday, August 9, 2012 7:06 PM
  • MSP_WEB_USERPROPERTIES table with user settings in projectserver_Published db - our users frequently receive “unknown error” in tasks, projects center pages and i delete records in this table based on user_uid.

    Not a perfect solution, but it will work. 

    • Proposed as answer by bratgera Sunday, August 12, 2012 9:49 AM
    Sunday, August 12, 2012 9:49 AM
  • Hi Paul,

    sorry for delay, I am still waiting for verbose files.

    Thanks in the meantime
    Barbara

    Monday, August 13, 2012 2:13 PM
  • Thanks for suggestion, I will follow up, when I have more information.

    Regards
    Barbara

    Monday, August 13, 2012 2:15 PM
  • Hi,

    good idea - I will check table. However, I definitely will not edit this DB ;-). But it may give me an idea what to do.

    Barbara

    Monday, August 13, 2012 2:16 PM
  • Hi,

    just an update, nearly one year later. I solved this issue, and forgot completely my own question.

    Since I did not want to edit DB directly, I finally found a solution.

    - make sure, that no-one is working during the following procedure
    - get a list of all projects, user is team member of or has assignments
    - get a list of all projects, user is project owner or status manager within project. change project owner and status manager temporarily to any other user. publish
    - take an administrative backup of users and resources (just in case)
    - delete resource with Server Settings - Delete Enterprise Objects
    - recreate resource in exactly the same way (name, account, permissions, ...)
    - open all projects as found with first step. Save them and answer the question for replace local resource by enterprise resource with yes. publish
    - change status manager and project owner to original user. publísh

    It is some effort, but it did work in my case.

    Regards
    Barbara

    Tuesday, July 9, 2013 1:09 PM