PSI 2010 SOAP Resource Web Services - Update Resources Error RRS feed

  • Question

  • Hello Community, 

    We are trying to use SOAP UI to perform an update request using PSI Resource ASMX Web Services. We are simply performing an update with the same resource dataset information obtained from the ReadResource call. 

    <soapenv:Envelope xmlns:soapenv="" xmlns:res="">
                   <diffgr:diffgram xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
                       <ResourceDataSet xmlns="">
                          <Resources diffgr:id="Resources1" msdata:rowOrder="0">
                          <ResourceRates diffgr:id="ResourceRates1" msdata:rowOrder="0">
                          <ResourceAvailabilities diffgr:id="ResourceAvailabilities1" msdata:rowOrder="0">

    The server responds with the following error: 

    <s:Envelope xmlns:s="">
             <faultstring xml:lang="en-US">ProjectServerError(s) LastError=GeneralUnhandledException Instructions: Pass this into PSClientError constructor to access all error information</faultstring>
                      <class name="An unhandled exception occurred in Microsoft.Office.Project.Server.BusinessLayer.Resource.UpdateResources.">
                         <error id="42" name="GeneralUnhandledException" uid="362c7b0b-6b4f-45c2-9b4a-640623dd7560" Exception="System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Office.Project.Server.BusinessLayer.Resource.DataSetHasMsxColumns(ResourceDataSet resourceDataSet)
       at Microsoft.Office.Project.Server.BusinessLayer.Resource.UpdateResources(ResourceDataSet rds, Boolean validateOnly, Boolean autoCheckIn)
       at Microsoft.Office.Project.Server.Wcf.Implementation.ResourceImpl.UpdateResources(ResourceDataSet rds, Boolean validateOnly, Boolean autoCheckIn)"/>

    The exception is generic but does anyone know what can be wrong here? the method called has no documentation (DataSetHasMsxColumns) but the name might be suggestive to someone used to work with the services.

    Thank you in advance

    Best Regards

    Monday, March 14, 2016 12:34 PM

All replies

  • Hi there,

        The error you show above occurs when the server is trying to check for the presence of certain columns in the DataSet you supplied (RES_CAL_OOF_EXCHANGE_SYNC and RES_EXCHANGE_EWS_URL).  It shouldn't crash at this point which suggests that there is a problem with the Resource DataSet object you have supplied to the API.

    I would suggest you ensure that you are using the appropriate .NET libraries to supply the serialization of the changes you are attempting.  Doing this via text manipulation is prone to error as the DataSet is a complex object with particular ways of storing changed rows as well as the originals.

    Good luck,


    James Boman BSc. MCP:EAD

    • Proposed as answer by James Boman Wednesday, June 7, 2017 7:42 PM
    Tuesday, March 15, 2016 2:05 AM
  • Hello James, 
    Thank you for your help. 

    In my current business scenario im actually trying to invoke the web services from an Java Application using Apache CXF. I'm just doing in SOAP UI to guarantee that the payload i'm sending is the same as the one i'm receiving (without any interferance from a Java Transformation). 

    The two columns you mentioned are not in the payload, not even when i call the Read Resources method to read the resource data set. 

    I guess i will have to look around to check if there is any Java Library to manipulate the data sets correctly or i will have to fill the values manually somehow.

    Thank you

    Best regards, 

    Tuesday, March 15, 2016 11:59 AM
  • Filipe,

       Yes, simply returning the payload you got after having changed it is unlikely to be correct.  Using .NET/Mono is recommended.

    Obviously the 2010 software is very old - in 2013 MS added CSOM, JSOM and REST interfaces to make this kind of activity easier.



    James Boman BSc. MCP:EAD

    Tuesday, March 15, 2016 10:10 PM
  • Hi Filipe

    I am facing exact same error in my Soap request.

    It will be really very helpful if you can share your resolution for this issue.

    Thanks in advance.

    Best Regards, Somnath

    Wednesday, June 7, 2017 5:49 PM