Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

Project Server 2010: Operation still processing–don’t shoot the messenger

Project Server 2010: Operation still processing–don’t shoot the messenger

  • Comments 7

Decided to make this post as we have been getting quite a few questions about this dialog – Operation still processing.

image

It can occur in various places within Project Web App and in my case I have made it appear in Project Center by creating a new project based on an Enterprise Project Type (called “Large”) that is using a project template which has around 2500 tasks.  In this case the full text says

“The Create operation has been queued, but is taking longer than expected to process.  To check the status of the creation queue job, visit the My Queue Jobs page. Once the job has completed, the new Large will be listed in the Project Center.
Click OK to close the project and return to Project Center.”

This isn’t an error – I wouldn’t even go so far as to say it is a warning – merely an informational dialog that we programmed to appear in cases where whatever you are doing is taking a little while to happen – usually around a minute or so.  It could be that something has gone wrong – more likely it is just taking a while – so have a look in the queue.  Possibly by the time you have read the message the job has completed.  It could be that you are creating a quite large plan from a template – or perhaps there are other jobs in the queue that mean yours is just waiting.  So this shouldn’t be treated as an error – unless when looking in the queue you find a bigger problem – like I did when writing this posting….  Possibly more on that in another posting if a reboot of my abused server doesn’t make my issues go away.

*** Update - Turns out in my attempted repro of this condition and using a large template I exposed a bug.  If you have a template of around 1600 tasks or bigger (the exact failure point will depend on other factors - could be as high as 4500) then you may experience a stack overflow when this hits the queue in the Project Create stage.  It will sit there processing for ever - and if you look in the ULS logs you will see evidence that the queue has restarted -

12/30/2011 07:46:48.20 Microsoft.Office.Project.Server (0x1EF4) 0x2798 Project Server General 8zdb High [SERVICE] ProjectQueueService14: ProcessWatcher signaled 
12/30/2011 07:46:48.20 Microsoft.Office.Project.Server (0x1EF4) 0x2798 Project Server General 8zdk High [SERVICE] ProjectQueueService14: ProcessWatcher restarting service for f0bf6473-d0bd-4442-8d28-65466f8f6dc0 PID: 8160 

In the application event logs you will see an event 1000 Application Error followed by one or more Windows Error Reporting event id 1001:

Faulting application name: Microsoft.Office.Project.Server.Queuing.exe, version: 14.0.6015.1000, time stamp: 0x4d0ffe25

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c

Exception code: 0xe053534f

Fault offset: 0x000000000000cacd

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

When the queue restarts it will just attempt the project create again, and after around 4 minutes you will see the same errors repeated. Best open a support incident to let us help you recover from this if you run into it.  So far I am not aware of any customers running in to this.  ***
 

 

Leave a Comment
  • Please add 8 and 8 and type the answer here:
  • Post
  • I am getting this error except mine is the SAVE OPERATION has been queued.  this only happens when in the timesheet and trying to save time.

  • OK Dammions - still not unexpected in this scenario if for example you have a lot of tasks or a lot of custom fields.  If you don't then check the usual things in terms of SQL Server database maintenance and server configuration.  Open a support incident if you still have issues and think it should be working faster.

    Best regards,

    Brian.

  • Is there a hotfix or CU that will resolve this issue?  I have this in a customer environment and am able to see it work for a 1000 task template, but fail when it is at 2500 tasks.

  • Hi Mike, we only fix things that are broken - this is working as designed and will always have a point where it displays the message rather than making the user wait.  Sorry it is not configurable for you.

    Best regards,

    Brian.

  • Now realize Mike that you meant the queue crash and not just the message - my apologies - the queue crash is certainly not by design.

    Best regards,

    Brian.

  • I think we are seeing the same issue

    Faulting application name: Microsoft.Office.Project.Server.Queuing.exe, version: 14.0.6015.1000, time stamp: 0x4d0ffe25

    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c

    Any ideas on resolution - have raised a case with Microsoft Support but no response after 48 hours :/

  • Hi Daniel, there are no current plans to fix this - ping me offline at BriSmith@Microsoft.com to follow up opn your open case.  If your company has a premier contract then a hotfix request may be an option.

    Best regards,

    Brian.

Page 1 of 1 (7 items)