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

  • Brian Smith's Microsoft Project Support Blog

    Interesting Article on Project Programmability Blog - Issue and Risks web part timeout workaround


    I missed this posting at the tail end of last month - so just calling it out in case some of you missed it too.  Scalable Issues and Risks Report!

    If you have lots of workspaces then a behavior you may have seen is the timeout of your PWA homepage, caused by the query bringing back (or at least attempting to bring back) the list of active issues and risks for a user.  Patrick Conlan has posted a potential workaround for this which is very cool.  It uses the reporting database and the SQL Reporting Services web part to give a very elegant alternative to the existing web part.  This isn't meant to be a replacement in all situations - and please note the caveat on the posting that this isn't something that will have an migration/upgrade path to future products; should be fully tested in pre-production and will not be fully supported by Microsoft.

    This suggested replacement really shows how the reporting database can be the best place to query for this kind of information.

    The full article can be found here - also look at some of the recent great postings including details of developer training for Project Server 2007.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    A Couple of "Visual How Tos" added to the Online SDK


    These short video clips are just over 10 minutes each and support the SDK articles Walkthrough: Creating a Custom Project Server Web Part and  How to: Write and Debug a Project Server Event Handler.  Both of these videos show Visual Basic being used - and the articles show C# for both and also VB for the event handler example.  They can be found at the following links:-

    Creating Custom Web Parts for Project Server 2007 

    Writing and Debugging Event Handlers for Project Server 2007.

  • Brian Smith's Microsoft Project Support Blog

    PSI: Filter constraints and escaping the recursive event handler


    A couple of topics that have come up through support incidents and comments posted here.  The first on the use of the filter or xmlFilter parameters available in a few of the web services, and the second talking about event handlers and what happens if you fire an event based on Check-In that then issues a check-in - how do you break the loop?


    The SDK details how the xmlFilter parameter can be used to filter the returned dataset and the sample code covers the CustomFields dataset.  However there are a couple of limitations that you should be aware of.  You can use the PSLibrary.Filter.Fields.Add to control the columns returned in the dataset and PSLibrary.Filter.Criteria to control the rows.  The criteria can only be used against the main tables of the dataset and cannot be used to filter rows in the secondary datasets.  For example the Resource web service has the ResourceDataSet which contains the ResourcesDataTable as the main datatable and also several others including the ResourceAvailabilityDataTable.  Only rows in the ResourcesDataTable can be filtered using criteria. You will get a ResourceFilterInvalid Exception (or CalendarFilterInvalid exception if you try to use criteria on CalendarExceptionsDataTable of the Calendar web service).  This should be fairly obvious as the construction for the criteria does not allow for a specific DataTable to be referenced.  The other limitation is less obvious and will be corrected in our documentation shortly.  The ResourceCustomFieldsDataTable cannot be filtered at all using the filter parameter - you will get a ResourceFilterInvalid exception.  In both cases you can of course use filter on the client once you have the full dataset returned.  Another option would be to create your own PSIExtension that does the extra filter and keep everything server side.

    Recursive Event Handlers

    I addressed this question from a comment but might be useful for a full posting.  So if as part of your workflow you have an event handler for check-in, and when it fires you need to update something in the project then you will also need to check-in when you have finished, which will then fire the event handler and so on.  The best way I could think of to break the circle is to set a specific string as the session description when you use the check-in in your event handler.  Then you can check in your code before checking out if the sessions description in the project dataset is the one for your event handler - or a user session description which will be of the format machinename\pwa_account.  If it is your setting then no need to continue.  If anyone has a better way then please share.

    Technorati Tags: Project Server 2007

  • Brian Smith's Microsoft Project Support Blog

    Joining the translation bandwagon


    I just saw Treb's posting on the new Windows Live Translator service that was rolled out this week - so I too have added a link in my News column on the left hand side.  I hope this helps my readers who prefer to read their own language.  I'm guessing it will not make much sense for real error messages - please let me know how it works for you.

  • Brian Smith's Microsoft Project Support Blog

    So where did all these GUIDs come from?


    Project Server 2007 makes much more use of GUIDs to identify different entities than the previous version so I thought I'd do a quick post to explain what they are, why we use them and how you should use them.  GUIDs were originally a priestly class in ancient Celtic societies.  No sorry, that was Druids.  GUIDs are Globally Unique Identifiers and are 128 bit numbers usually represented in the database and ULS logs as a sequence of hexadecimal digits.  They are not guaranteed to be unique - but with 2122 or 5.3×1036 to choose from you shouldn't see duplicates (or if you do it might be the right day to buy that lottery ticket!).

    One future benefit the move to GUIDs could give us is the potential for consolidation of servers - or the use of replication between servers - where we can be sure that all the entities are unique.  With Project Server 2003 there would always be a project 101 in every server, so difficult to combine data from two servers.  GUIDs lead the way to federated servers.

    One place where you may need to use GUIDs is as an identifier for new users you add through the FormsAuthUpgrade tool.  A recent support case had a customer sure that his GUIDs in his users.xml file were correct but still got an error:

    Error: An error occurred creating user janedoe in membership provider. Error: Guid should contain 32 digits with 4 dashes

    Closer examination showed the GUIDs had the character "g" and they should only contain hexadecimal digits (So 0-9 and a-f).  In my testing I have been known to start with one GUID and just change the last numbers for other users so I can see how this can happen (pseudo GUIDs - as my colleagues call them).  Better to use a tool to give you a new unique one.  Visual Studio can do this through Tools, Create GUID - or you can do it in code. 

    If you have ever had to search logs or the database looking for a particular GUID then you will also appreciate that you don't want too many that look the same - and better still to have the first few characters different.  In most cases if you look at the first 4 or 5 digits you would be unlucky to find duplicates in even a large dataset.  To find out even more see the entry on Wikipedia

    One useful relationship you should be aware of is that the Correlation Id you see in the queue and in the logs will actually be the Project GUID for any project-related queue job.

    Technorati Tags: Project Server 2007

Page 81 of 93 (464 items) «7980818283»