Custom Field not displayed in PWA RRS feed

  • Question

  • We created a custom field for ProjectID, for which a value is generated and stored when a project is first checked in to Project Server. Until recently, the customization worked fine, with the ProjectID value displayed in the default Project Center view - which we modified to include display of the ProjectID value. Recently, the ProjectID has not been displaying automatically.

    We have verified that the ProjectID value exists for the project in the Draft database immediately after project creation through the PWA. However, the ProjectID value does not exist in the Published database or the PWA user interface, until a user re-opens the project, clicks Edit, and then Saves the project. Clicking Edit alone displays the ProjectID value in the associated project information page, but unless the user Saves, it still fails to exist in the PWA Project Center view, or in the Published database.

    Any suggestions would be greatly appreciated.



    Thursday, January 5, 2012 4:04 PM

All replies

  • For some reason, it sounds like the custom code is not publishing the project
    after making the edit.
    (Saving in PWA is equivalent to Publishing.)
    Maybe it stopped working after applying a Cumulative Update?

    Andrew Lavinsky [MVP] Blog: Twitter: @alavinsky
    • Proposed as answer by liangshuang Wednesday, May 29, 2013 6:57 AM
    Thursday, January 5, 2012 4:45 PM
  • Perhaps it was an environment update. We have recently experienced a new problem - where the DLL, even though copied (XCOPY deployment method) to the \Microsoft Office Servers\14.0\Bin\ProjectServerEventHandlers  directory on each server in the environment, and with the event handlers setup using the PWA Server Side Event Handlers utility, is not recognized / applied to the CheckIn event. 

    Is it likely that this is related to some updates / patches applied to Sharepoint or Project Server components. Has anyone else observed this? Suggestions on how to debug? In the past, shortly after registering the DLL as a Server Side Event Handler, you could not delete or rename the file. Now, using PWA to register the handler has no effect on the DDL file permissions. 

    A related question. Does the .Net runtime environment installed on each web / app server in the farm have any impact on the DLL function? I ask, because it appears our server team has different .Net versions on different machines.



    Friday, January 11, 2013 6:12 PM
  • What type is the custom field? ie. Text, Number, Cost, Duration,Etc

    Is it text perhaps?  And if it is, is it single line or multi-line.

    Tells us more about how the custom field was defined.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Blog contains my field notes and SQL queries

    Tuesday, January 15, 2013 5:32 AM
  • Michael,

    The custom field is a text. The server systems team performed some maintenance / applied patches over the weekend, and the custom ProjectID DLL is now working properly on 3 out of 4 servers in the Sharepoint / PWA farm. On the fourth, the event logs show the following errors when attempting to load the DLL:

    SEP: Cannot create instance of the receiver class: ProjectCustomID, Version=, Culture=neutral, PublicKeyToken=54e894fa6bdb4aa9, ProjectCustomID.IDGenerator  Exception: Could not load file or assembly 'ProjectCustomID, Version=, Culture=neutral, PublicKeyToken=54e894fa6bdb4aa9' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

    On subsequent CheckIn events handled by this server, the following errors are recorded:

    EventHandler: \ProjectCustomID, Version=, Culture=neutral, PublicKeyToken=54e894fa6bdb4aa9, ProjectCustomID.IDGenerator\ could not be loaded

    We deployed the ProjectCustomID.dll file to all 4 servers using the XCOPY method (not gacutil) - and I checked all 4 servers, the DLL is in the MicrosoftOfficeServers\14.0\Bin\ProjectServerEventHandlers directory - and there is no reference to the DLL in the Assembly Cache.

    I have done a Clean and Rebuild of the DLL in Visual Studio, to no effect. I have removed and re-assigned the CheckIn server side event handler via PWA several times. 

    Could this be a .Net runtime environment issue on the server in question? Or a Sharepoint / Project server environment issue? Any other suggestions on next steps?



    Tuesday, January 15, 2013 2:23 PM
  • you need to open your project in MS project professtion,publish it,then you could see it!
    Wednesday, May 29, 2013 6:59 AM