Operation Timed Out on the Resource Availability Report in Project 2010

One user was getting an error while trying to view the Resource Availability report in Project 2010, though the report worked fine for all other users. It turns out that the error message in the log file was one of the generic messages that didn’t mean too much: “operation timed out”. So, it wasn’t reporting any sort of permission issues, it was just reporting that the database wasn’t able to finish the queries in the default time of three minutes. So, one option is to go change the config file on the server and allow it to run for more than three minutes. But before doing that, there’s another possibility. On the Resource Availability report page, there’s a section that allows you to change the date range and the units from weeks to days or months:

resource report options


When a change is made to the above, the server remembers that change and defaults it to that for the next time. So, if a user changes the dropdown to “days”, the next time they navigate to this page, “days” will already be selected. However, if the system can’t handle reporting on days within the allotted three minutes, then the error occurs. And, when the user navigates back to that page, it will default to days again, generating the error again, without giving any opportunity to change the selection back to weeks or months.

In light of the above, try the following:

  1. Navigate to the resource center
  2. Make sure that no users are selected
  3. Select one resource that does not have any tasks in the next couple months. Perhaps an old resource that shouldn’t be in the system?
  4. Click on “Resource availability”

If my guess above is correct, then the report will run fine, as there is no data for the user, and as such the timeout won’t be hit. If the report runs, then check the units drop-down. If it says “days”, change it back to weeks. Also, check the date range. If the range is large, make it smaller.

If the above doesn’t work, then the next step will be either troubleshooting the SQL server, or working with IT to get the config file modified to change the default timeout value to a higher number.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s