Thanks to my colleague Trevor Turner for compiling the various places in Project Server and associated technologies that timeout values can be set. This came about to resolve problems in the Resource Substitution Wizard – but is helpful information for other slow scenarios too – particularly when large datasets are involved. As Trevor points out – you should carry out other mitigations such as good use of categories, and also ensure your SQL databases have up to date statistics and fresh indexes. Much better to make things run faster than just allowing longer waits for slow processing!
Whenever something fails in a very specific amount of time – 30 seconds, 1 minute, 1 hour – I always suspect some sort of timeout may be involved.
Resource Substitution Wizard and Timeout Settings
In certain circumstances where the Resource Substitution Wizard has to deal with a large amount of data the default settings for some timeout values are not large enough. This can either cause errors to be returned to the user or cause unexpected data to be retrieved when running the wizard.
In order to resolve the specific timeout errors we have to ensure that the appropriate timeout values are set in the following four locations.
NOTE: Before making these changes, however, it may be more appropriate to try to mitigate any timeout errors by controlling which projects the user can see by making use of Categories (in Project Web Access). Reducing the number of projects a user has access to in this way will reduce the length of time taken to run the wizard and, therefore, reduce the need to increase the aforementioned timeout values.
The following values/screenshots are what I have set on my system and which allow the Resource Substitution Wizard to successfully complete on a large customer dataset in around 8 minutes. Values should be modified at your own discretion.
These timeout values may need to be increased further in different environments as the system parameters will, obviously, be different.
All tests were performed using Project Server 2007 with the June CU installed for WSS, Project Server and Project Professional.
It must also be noted that increasing timeout values can cause the system to run less efficiently and effectively, particularly those settings for IIS.
1. The Project Server database
In the Project Server Published database the setting in the MSP_WEB_ADMIN table for WADMIN_CORE_SQL_TIMEOUT should be increased. This value is in seconds.
This value can also be modified by making use of the PSI. Please see the following reference;
2. The HKCU hive of the Windows registry
The following registry value should be added to the local user’s registry.
Name : Timeout
Type : DWORD
This setting controls the SOAP Toolkit timeout value on the client.
The default value is 60000, and it is ranked in milliseconds, putting the default value at one minute.
If this value is not high enough you will likely receive the following error, along with a related entry in the Application Event Log relating to MSSOAP.
3. The website timeout in IIS
In Internet Information Services (IIS) Manager, the “Connection timeout:” setting should be increased for the Project Server Web Site.
4. The ASP.NET timeout in IIS
In Internet Information Services (IIS) Manager, select the ASP.NET tab and press the “Edit Configuration” button.
Select the Application tab and set the “Request execution timeout (seconds):” value for
the Project Server Web Site.
This posting came about based on a comment on my posting http://blogs.msdn.com/brismith/archive/2009/05/13/project-server-2007-my-filters-don-t-work-in-my-data-analysis-views.aspx from Dick Ruemmele. Chris Bulson had also chased me up on this as I hadn’t had a chance to follow up. The issue is that OWC is somewhat limited in filtering – and the desire here was to have a list showing capacity and work – but only if work had a value (capacity almost always has a value). This isn’t possible with OWC against the default cubes (not sure if MDX could help here…) but if you use Excel as the client and point at your Analysis Services server and your project cubes then you have more flexibility – including Value Filters! I found the details here on the Excel blog (and do take a look at the latest postings on the Excel 2010)
With the default view we see all rows (names obliterated to protect the innocent!)– but we only want ones where Work > 0.
But by selecting Value Filters (on drop down next to Resource List) we can select Greater Than, and then set Work Greater than 0:
And we only see the rows with work!
SSRS or Excel Services might also be other options to explore to overcome some of these limitations of Office Web Components (OWC)
For full details of links and stuff see Christophe’s blog http://blogs.msdn.com/chrisfie/archive/2009/07/23/announcing-the-release-of-project-portfolio-server-2007-service-pack-2-sp2.aspx. Here are the highlights:
Highlight of Portfolio Server 2007 SP2:
The third point answers a question posted to my blog regarding VM support – but PPS may still not be listed in the validation tool just yet.
And this is my first mobile blog – meaning I am on the Connector bus en-route to Campus. One of the best benefits Microsoft has come up with recently – and the roads to Campus are noticably quieter because of it. And wireless all the way to work…
I know, that was mean. And probably a little over 10,000 ft, as Rainier itself is 14,410ft. Keshav has posted some early information about Project 2010, but to hear more you will need to wait for the Project Conference in September – and it is certainly worth waiting for!
The other Office client applications are making some earlier disclosures and there is already some cool stuff on the blogs about the other Office applications – and my favorite so far is the Excel 2010 Sparklines posting from Sam Radakovitz. The Excel blog is also a good starting point for other 2010 content – just go to their links section on the lower right.
I knew Mt Rainier was about 14k ft, but I turned to Bing for the answer (and Mt Rainer looked nearly this good from ground level this morning on my drive to work). The picture above was taken just after take-off from SeaTac on my recent vacation – which is also the reason I haven’t been too quick replying to recent comment posts to the blog… I’ll try and do some catching up next week.
It is June the umptieth and the June Cumulative Update packages for Office Suite and Office Servers (including Project Server 2007) are now available. Some of the KB articles are still on their way through the system so some of the links below may not work just yet. The overall KB pointing to all the Office client and server KBs can be found at http://support.microsoft.com/kb/972632.
So here are the links applicable to Project and Project Server:
http://support.microsoft.com/kb/971537 (Coming soon!)
Good news here is the first “fix” mentioned on the Project Server KB - The Tracking Method setting on the Task Settings and Displaypage is not applied to proposals or to converted proposals. This should return the behavior customers had grown to know and like since the Infrastructure Upgrade.