none
Error while trying to access Timesheet History page from Approval Center or Timesheet Adjustment link RRS feed

  • Question

  • In our Project Server 2010 farm some of the Timesheet managers are getting below error when they try to access Timesheet History via Approval Center --> History --> Timesheets page or via Timesheet Adjustment link.

    Last month we had a similar issue but after reboot of the server farm post April MS patches affected users were able to access timesheet history page.

    We are currently on Project Server 2010 + SP2 + Dec 2014 CU. This issue is not faced by all users only a handful of users are facing this issue. Can some one advise how to fix/resolve this issue.

    05/15/2017 10:52:31.69  w3wp.exe (0x263C)                        0x5314 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (ExecuteWcfServerOperation). Execution Time=1.23864590992819 a35f0e12-7bcc-4f47-b506-278e26e773b3
    05/15/2017 10:52:31.93  w3wp.exe (0xD200)                        0x8D24 SharePoint Foundation          Runtime                        tkau Unexpected System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.    at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)     at System.Text.StringBuilder..ctor(String value, Int32 startIndex, Int32 length, Int32 capacity)     at System.Text.StringBuilder..ctor(Int32 capacity)     at System.Data.DataSet.SerializeDataSet(SerializationInfo info, StreamingContext context, SerializationFormat remotingFormat)     at System.Data.DataSet.GetObjectData(SerializationInfo info, StreamingContext context)     at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter... 87aa0181-397a-439a-9e8b-42a3a323daf9
    05/15/2017 10:52:31.93* w3wp.exe (0xD200)                        0x8D24 SharePoint Foundation          Runtime                        tkau Unexpected ..., ObjectWriter objectWriter)     at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)     at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)     at System.Web.Util.AltSerialization.WriteValueToStream(Object value, BinaryWriter writer) 87aa0181-397a-439a-9e8b-42a3a323daf9
    05/15/2017 10:52:31.93  w3wp.exe (0xD200)                        0x8D24 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (Request (GET:http://projectoffice.broadridge.net:80/pwa/_layouts/pwa/Timesheet/TimesheetHistory.aspx)). Execution Time=79951.1083419356 87aa0181-397a-439a-9e8b-42a3a323daf9
    05/15/2017 10:52:31.94  w3wp.exe (0xD200)                        0x1768 SharePoint Foundation          Monitoring                     nasq Medium   Entering monitored scope (Request (GET:http://projectoffice.broadridge.net:80/pwa/_catalogs/theme/Themed/9A2213C4/layouts-9C6B8173.css?ctag=10)) 

    Monday, May 15, 2017 3:21 PM

All replies

  • Hello Srivatsave

    I have seen similar issues in the past and it required Microsoft to analysis the database and fix some records.  I believe index or records got corrupted.   Microsoft had tools that did sanity checks on database.

    I would suggest that you open a ticket with Microsoft to fix. 



    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, May 26, 2017 4:06 AM
    Moderator
  • Looking closer at the error logs, it look like you may have run out of memory.  This could be because of corrupted data that is accessing protected memory.  

    Have you looked out your memory usage?  Are you running project server and SQL server on the same server?


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, June 1, 2017 3:13 AM
    Moderator
  • Hi Mike,

    Thanks for the response.

    We are running PWA on a 3-tier cluster farm with dedicated DB servers. I have checked the memory usage when the issue has occured but there is pretty much space with regards to both physical and logical memory in SQL server and App/Web servers.

    As I mentioned earlier, only very handful timesheet managers are facing this issue. Initially I too thought it might be due because SQL memory is low; I tried delegating to profile of such resources and accessed the page when the DB server is almost idle. Still I got the issue.

    My guess is if the issue is with memory all Timesheet Managers should be facing the same.

    After posting the question here, I accessed Timesheet History page from my profile. As I dont accept Timesheets, I thougt the page should load; which would help me to isolate if the issue is with huge number of records or something with SQL memory. Timesheet history page loaded for me, so I thought the issue could be with number of records the page is trying to get from DB and eventually it is timing out.

    So when I again delegated to the PWA profile of these users and accessed Timesheet history page, it was loading again without any issue.

    Monday, June 5, 2017 3:22 PM
  • Have you tried rebooting both the SharePoint servers to clear out all the cache and see if that fixes the problem.



    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Thursday, June 8, 2017 3:04 PM
    Moderator
  • Hi Mike,

    Yes, as I mentioned earlier, when we reboot the server farm this issue is getting resolved.

    Thursday, June 15, 2017 12:36 PM