none
Frequent Error approving updates, help with what to start looking for. RRS feed

  • Question

  • This is what I dug out of the ULS so far.

    PWA:http://WFE/PWA, ServiceApp:Domain Project Server, User:i:0#.w|domain\engproject, PSI: Failed to process change for project f477408d-00ce-e211-be7c-00155d09a701, node 3, transaction uid: 32d27efa-8a50-4088-928a-0e0c30d9323d Project:f477408d-00ce-e211-be7c-00155d09a701

    any common PSI failures that relate to this?

    Tuesday, June 25, 2013 8:47 PM

All replies

  • Check the entries above and below that to see if they indicate anything useful....?

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky

    Wednesday, June 26, 2013 2:40 AM
    Moderator
  • I have a ton of these High Level items....

    UserAgent not available, file operations may not be optimized. at Microsoft.SharePoint.SPFileStreamManager.get_UserAgent() 

    The user who fails on the approvals is surrounded by these....

    [Forced due to logging gap, cached @ 06/26/2013 08:07:10.08, Original Level: VerboseEx] PWA:http://WFE/PWA, ServiceApp:Domain Project Server, User:i:0#.w|domain\engproject, PSI: [TrackingId:07cab9e7-58de-e211-9439-00155d099c06][ResourceId:7d370653-af7a-e211-93f2-00155d099c06][SessionGuid:9c2f207c-2dc9-e211-be78-00155d09971a][SessionDescr:CTENG166\serv1s15][JobGuid:00000000-0000-0000-0000-000000000000][ProjectGuid:11111111-1111-1111-1111-111111111111][PS_AC][789] prop: Property(255852574,F40001E,MSP_ASSIGNMENTS,ASSN_ACT_OVT_COST), LogLevelManager Warning-ulsID:0x39356538 has no entities explicitly specified. 

    Here is the Exception before the PSI failed

    CalcServiceManager : Communication with the worker failed in sessionId: rbbOC6dNe0qR+31uojJKfI1Ad/TOABHivnwAFV0JpwFTBjd9eq8R4pPyABVdCZwG22LyQd5YEeKUOQAVXQmcBsEN7EQ8yzFMmz1sC78aNC0= System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:00:29.9843781'. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host 

    Wednesday, June 26, 2013 12:41 PM
  • Looks like SQL server error. Please check SQL server logs for more details.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Wednesday, June 26, 2013 1:05 PM
    Moderator
  • I had a 5 second repeating message in the log

    Message
    Using 'dbghelp.dll' version '4.0.5'

    Google says to stop the 2 sharepoint SQL Extended Events.

    While digging I also found an duplicate IP assigned to Production and Development. So I will monitor for a scheduling cycle and see how it goes.

    Wednesday, June 26, 2013 5:32 PM
  • Duplicate IP could be the reason.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Wednesday, June 26, 2013 5:35 PM
    Moderator
  • Crashed again this morning lost a half day...

    Memories of 2003

    Faulting application name: schedengine.exe, version: 15.0.4481.1001, time stamp: 0x50f92665

    Faulting module name: ntdll.dll, version: 6.2.9200.16579, time stamp: 0x51637f77

    Exception code: 0xc0000374

    Fault offset: 0x00000000000ebd59

    Faulting process id: 0x748

    Faulting application start time: 0x01ce733fa23ac445

    Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Bin\schedengine.exe

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 15e42805-df63-11e2-943a-00155d099c06

    Faulting package full name:

    Faulting package-relative application ID:

    Thursday, June 27, 2013 7:56 PM
  • This I think is the exact same problem I had with 2003, It was a math thing when actuals are submitted that don't fit into a 9 to 5 day or on a constrained task the update processing would crash. It would fail on a cdata for whatever the API was back in those days. Now 2013 is even worse.

    If I tried to apply those updates manually within the project pro client the project pro client will crash on the exact same update. Ten years and it still isn't fixed.

    Thursday, June 27, 2013 8:17 PM
  • If you can repro this issue in any environment and this could be potential bug and you could open support incident with Microsoft. If this is a true bug you will not charged for support incident. Please provide step by step repro  so that I can try to repro this issue too.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Saturday, June 29, 2013 3:17 PM
    Moderator
  • I'm working a Microsoft case on this now. As I think back to my first test environment did not think I had this issue. I'll post the cause once we find it.
    Tuesday, July 9, 2013 5:33 PM
  • Just wondering if you found resolution to your question as we are experiencing something similar.


    Lenny

    Tuesday, February 4, 2014 4:58 PM
  • still not solved, been almost a year with Microsoft support case.

     [REG:113062710549701] Approval of Updates is generating errors, when that erroring update is manually entered in Project Pro , Pro crashes.

    I had a repeatable crash when trying to manually apply the updates.

    the layout was like this

    task -(fts link)- failingtask

    I removed the link then adjusted actuals on failingtask and project pro did not crash.

    I have asked support to attach a debugger to the scheduling engine but they refused.


    • Edited by Toomanyhats Friday, February 14, 2014 3:13 PM
    Friday, February 14, 2014 3:11 PM