none
Project Server 2013: QueueUpdateProject2 fails with LookupTableItemInvalidLookupTable error RRS feed

  • Question

  • Hi,

    We have a strange problem here using the newly introduced QueueUpdateProject2 PSI method in WebSvcProject. The server is running version 15.0.4481.1005 (Project Server 2013, March 2013 PU). Here's the minimum repro code:

    projectService.CheckOutProject(projectUid, sessionUid, sessionDescription);
    var projectDataSet = projectService.ReadProject(projectUid, DataStoreEnum.WorkingStore);
    projectDataSet.Project[0].SetModified(); // Simplest repro
     
    var jobUid = Guid.NewGuid();
    projectService.QueueUpdateProject2(jobUid, sessionUid, projectDataSet, false);
    
     

    Unfortunately the QueueUpdateProject2 queue job always fails with error LookupTableItemInvalidLookupTable for this project. Here's the full error information as shown in PWA:

    • LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07:
      • LookupTableItemInvalidLookupTable (11073). Details: id='11073' name='LookupTableItemInvalidLookupTable' uid='b1c62182-924c-e311-9404-00155d027b07'.
    • Queue:
      • GeneralQueueJobFailed (26000) - ProjectUpdate.ProjectUpdate2Message. Details: id='26000' name='GeneralQueueJobFailed' uid='b020bf82-924c-e311-9404-00155d027b07' JobUID='f294b911-f500-45bc-91ec-a493bdf3d07a' ComputerName='1beb2ff2-5dc9-4136-aa24-1c2be86c5768' GroupType='ProjectUpdate' MessageType='ProjectUpdate2Message' MessageId='2' Stage='' CorrelationUID='ce4e569c-0aa5-70d6-c576-8b3b764d14f1'. For more details, check the ULS logs on machine 1beb2ff2-5dc9-4136-aa24-1c2be86c5768 for entries with JobUID f294b911-f500-45bc-91ec-a493bdf3d07a.

    Here are some corresponding entries from the ULS log:

    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save              myzo Medium   Error is: LookupTableItemInvalidLookupTable. Details: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07 . Standard Information: , LogLevelManager Warning-ulsID:0x6D797A6F has no entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82  Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save              4zbp Monitorable PWA:, ServiceApp:Project Server Service Application, User:i:0#.w|my\account, PSI: [TrackingId:fa790381-924c-e311-9404-00155d027b07][ResourceId:3222f5b7-c13b-e311-9404-00155d027b07][SessionGuid:db83645c-50e1-4368-a59f-94df13ff7d5e][SessionDescr:][JobGuid:af20bf82-924c-e311-9404-00155d027b07][ProjectGuid:81a4a757-c446-e311-9404-00155d027b07][PS_AC][400] Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value b99b7782-924c-e311-9404-00155d027b07     at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName, Int32 projType, Boolean ... ce4e569c-0aa5-70d6-c576-8b3b764d14f1
    11/13/2013 19:36:30.82* Microsoft.Office.Project.Server (0x06D0) 0x1E60 Project Server                 Active Cache Save              4zbp Monitorable ...isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData, String winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified. ce4e569c-0aa5-70d6-c576-8b3b764d14f1

    We would be happy to provide more information if needed. Project Professional can open and save the project just fine, so it seems to be unrelated to other forum posts (1, 2).

    Has anybody seen this before? Any hints on where to search or what to look for?

    Thanks,
    Thomas
    TPG The Project Group

    [1] http://social.technet.microsoft.com/Forums/projectserver/en-US/da3c0d64-1ced-45dd-ace6-ce821fd1c362/what-are-the-lookup-fields-in-the-local-project-cant-publish-project-to-the-server
    [2] http://answers.microsoft.com/en-us/office/forum/office_2010-project/error-110730x2b41-importsave-to-project-server/03fd792f-4451-4512-ac0b-ddad946c3e3

    Wednesday, November 13, 2013 7:33 PM

All replies

  • OK, we opened a support case with Microsoft. They could reproduce the issue, but there's no fix available yet. As there's only a single customer with two defective projects right now, they likely won't provide a fix either. So if you're facing the same issue, please contact Microsoft Support and connect with case REG113121911042186.

    Thanks,

    Thomas

    TPG The Project Group

    • Proposed as answer by hardit singh1 Thursday, June 18, 2015 2:16 PM
    • Unproposed as answer by hardit singh1 Thursday, June 18, 2015 2:16 PM
    Monday, February 17, 2014 11:02 AM
  • We have the exact same issue and I spoke to Brian Smith ( http://blogs.msdn.com/b/brismith/ ) when I was at Project Server Conference 2014. He acknowledged that is a known issue and even internal Microsoft folks get this error.  He also mentioned that a fix is in the works and might be released sometime in April 2014.
    Monday, February 24, 2014 9:32 PM
  • Hi Srini, Thomas, I can see that we have a fix for this in Project Online - I am just finding what the fix schedule looks like for an on-premises fix in Project Server 2013. It would certainly help if a premier customer makes a hotfix request, but in my mind we have seen enough of this issue to know that we need to fix it.

    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

    Monday, February 24, 2014 10:10 PM
    Owner
  • Hi @all has this issue been fixed yet (on-premise)?
    Tuesday, May 6, 2014 7:07 AM
  • Hi Everyone,

    We also seem to be hitting this error in 2013 - with a reasonable amount of schedules (at least 10, maybe many more).

    I will log an issue with the reference of this posting.

    Thanks

    Nico


    http://blogs.umtsa.co.za/nicoo

    Wednesday, June 11, 2014 11:21 AM
  • There seem to be many different things being discussed in this thread.  The issue I said was being fixed is fixed in the June CU - KB 2837680 http://support.microsoft.com/kb/2837680/en-us and also included in the uberpackage KB 2881062 - http://support.microsoft.com/kb/2881062/en-us

    Assume that you have a local custom field that is defined to include a lookup table, and yet the table is missing. When you save the project to the Project server, the save operation fails. Additionally, you receive an error message that resembles the following:

    The following job failed to complete.
    Job Type: Save
    Error ID: 9000(0x2328)
    Error Description:  The project could not be saved to the server. Please retry saving the project. If the problem persists, save the project as a MPP file and contact your system administrator.

    This is usually seen when saving from Project Professional 2013 - the fix is on the server.  This may also fix the issue seen when updating through the PSI - but we would need a repro of that condition.

    The case Thomas refers to appears to be related to a project publish problem and not related to QueueUpdateProject2 error with Invalid Lookup Table item.

    If you don't load the uberpackage then there are other Project Server fixes in http://support.microsoft.com/kb/2880489/en-us too.

    Hope this help.

    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, June 11, 2014 2:03 PM
    Owner
  • That is actually brilliant info, thanks for that - its EXACTLY the problem described in the article, and I have the exact same error as Thomas.

    I will install the CU and see.

    Thanks

    Nico


    http://blogs.umtsa.co.za/nicoo

    Wednesday, June 11, 2014 2:09 PM
  • Just to clarify,  I get these errors in the ULS logs:

    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project Server        Active Cache Save        myzo        Medium        Error is: LookupTableItemInvalidLookupTable. Details: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a . Standard Information: PSI Entry Point:  Project User: i:0#.w|africa\spsetupdev Correlation Id: f6a91701-62f1-e311-944d-00155de84b1a PWA Site URL: http://epmdev.af.didata.local/PWA SA Name: SharePoint_EPM_Dev_ProjectServerService PSError: LookupTableItemInvalidLookupTable (11073), LogLevelManager Warning-ulsID:0x6D797A6F has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff

    06-11-2014 14:15:02.42        w3wp.exe (0x23AC)        0x23E0        Project Server        Active Cache Save        4zbp        Monitorable        PWA:http://epmdev.af.didata.local/PWA, ServiceApp:SharePoint_EPM_Dev_ProjectServerService, User:i:0#.w|africa\spsetupdev, PSI: [TrackingId:f6a91701-62f1-e311-944d-00155de84b1a][ResourceId:f6760993-7a33-47ef-8cea-0c9cc5231ae7][SessionGuid:6c189001-cd9e-e311-9426-00155d879c00][SessionDescr:ZABRYSVEPMD01\Dev PWA][JobGuid:d3e31201-62f1-e311-944d-00155de84b1a][ProjectGuid:7537ccc0-7692-4456-93dd-fc7adcb5d1c8][PS_AC][807] Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.WinProjException: LookupTableItemInvalidLookupTable for lookup table value 440c1ce7-61f1-e311-944d-00155de84b1a     at Microsoft.Office.Project.Server.BusinessLayer.WinProjUtility.P12Deserializer.PostReadRow(P12ContainerHeader cntrHeader, Row row)     at Microsoft.Office.Project.Server.BusinessLayer.WinProj.SaveProjectInternal(Guid projGuid, String projName, Int32 projType, Boolean isNewProj, Guid jobGuid, Guid sessionGuid, Guid checkOutByResUid, String sessionDescr, Boolean isFirstPacket, Boolean isLastPacket, String newVersionStamp, Int16 dataFormatVersion, Boolean isDataCompressed, Byte[] projectData, String winprojBuildNumber, ACProcessorType acProcType), LogLevelManager Warning-ulsID:0x347A6270 has no entities explicitly specified.        72d0999c-429e-80e4-4f95-1037e3c788ff

    And in addition to that, we get the Error  9000 when saving in MSP.  

    Still downloading the files, but the more and more I look at it I'm hopeful this will solve our problem.


    http://blogs.umtsa.co.za/nicoo




    Wednesday, June 11, 2014 4:58 PM
  • The patch (Brian posted the link above) fixes the  Error  9000 save issue.  Thanks Brian
    Wednesday, June 11, 2014 6:05 PM
  • Same this side.  The patch looks like it helped us too.  Thanks Brian, from my side too.

    http://blogs.umtsa.co.za/nicoo

    Thursday, June 12, 2014 7:42 AM
  • Brian, sorry, just one last question - the rollup package consists of three files - should I just install all of them?  I just installed the specific hotfix to test, but would rather install the rollup.

    Thanks,

    Nico


    http://blogs.umtsa.co.za/nicoo

    Thursday, June 12, 2014 9:25 AM
  • No problem Nico - and just to be clear for others reading this - the specific hotfix you mention is actually a roll-up of all previous Project Server hotfixes - when you mention roll-up you are referring to the full package including SharePoint fixes too.  This is 3 files and you need all of them.  You cannot actually just install one of the files - they form a set - and I hope to get the CU release blog post out today and will point this out.  It was the same for the full package for April CU too (actually released May 7th).

    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

    Thursday, June 12, 2014 2:11 PM
    Owner
  • Hi,

    I was facing the same issue in Project 2010( still using 2010 ): ). What i did:

    1) Opened project having issues in MS Project 2010 and saved the project as XML on my desktop.

    2) Close the project in project in MS Project.

    3) Opened the XML project in MS Project again and selected to create as new project.

    4) It saves and publishes successfully.

    May be this solution can help. Let me know in case of any questions.

    Cheers,

    Hardit Singh

    • Proposed as answer by hardit singh1 Thursday, June 18, 2015 2:16 PM
    Thursday, June 18, 2015 2:15 PM