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

June, 2010

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: View Failure in Project Center when certain ISO Currency Codes used in published projects

    • 7 Comments

    This one came to my attention via the TechNet Project Server forums http://social.technet.microsoft.com/Forums/en-US/category/projectserver2010 (thanks Milen!) and was specifically raised concerning the Bulgarian currency code BGN.  If this was used in a project (File, Options, Display, Currency) then published to the server then an error would occur when navigating to Project Center:

    View Failure.  The view failed to load.  Press OK to reload this view with the default settings.  Press Cancel to select another view.

    Pressing OK would just repeat the error – pressing Cancel would enable you to choose another view – and then see the error again.

    Investigating the problem I found it to be due to changes in the currency codes over recent years that have been implemented in the client (Project Professional) but in the server we are picking up the codes from the RegionInfo class in .NET 3.5 System.Globalization and these are still the old ones (they are now right in .NET 4.0 – but that doesn’t help for the 3.5 targeted codes in Project Server 2010).  The countries and currencies affected are:

      • Azerbaijan         From AZM to AZN
      • Bulgaria             From BGL to BGN
      • Belarus              From BYB to BYR
      • Venezuela         From VEB to VEF
      • Zimbabwe         From ZWD to ZWL

    The 'From' codes are those available on the server. The 'To' ones are those available on the client.  One final breakage is for XDR, which is included on the client but does not list on the server via RegionInfo as it is the ISO code for the International Monetary Fund (IMF).

    There is a Catch-22 here, in that customers in these countries or using these currencies in their projects will only have the old codes available for their server – but only the new ones on the client. 

    The only workaround would be to use some other nominal currency that is represented in both places.  I won’t risk offending anyone by suggesting a single currency… There may be other reasons you might get this error – but if you suspect these currencies could be causing the issue then look for any of the following in the File, Options, Display, Currency entry in Project Professional ('AZN','BGN','BYR','VEF','ZWL','XDR') or for the adventurous I will save you a few minutes and tell you the table you want is in the published DB, and is MSP_PROJECTS and the column is PROJ_OPT_CURRENCY_CODE.

    Also Romania and Russia have changed codes, but ROL/RON and RUR/RUB do not create the issue, as it has been resolved for these specific languages (and hopefully a similar fix will be forthcoming for these languages.

    *** 5/21/2013 Update - This also affects the Nigerian currency - symbol NGN.  This does appear in the list of currencies for Project Server 2013, but was not in the .NET Framework for Project Server 2010.  For NGN as well as the other currencies mentioned here one option, which we have helped a Venezuelan customer with, was to use LocaleBuilder to get the new currency in - http://msdn.microsoft.com/en-us/magazine/cc163506.aspx .  Contact us in support if you want some pointers.  This would apply to the currencies above, although I believe in SP1 of Project Server 2010 we did address some of these issues (VEB/VEF) ***

     

    Technorati Tags: ,
  • Brian Smith's Microsoft Project Support Blog

    June 2010 Cumulative Update (CU) for Project Server 2007, Office SharePoint Server 2007, WSS and Project 2007 now available!

    • 1 Comments

    I just posted over at the admin blog http://blogs.technet.com/b/projectadministration/archive/2010/06/30/june-2010-cumulative-update-cu-for-project-server-2007-office-sharepoint-server-2007-wss-and-project-2007-now-available.aspx – so won’t repeat everything here, This is the release of the Office and Office Servers 2007 June 2010 CU, including Project 2007 and Project Server 2007 – the release of the June 2010 Cumulative update for the Office 2010 and Office Server 2010 (including Project 2010 and Project Server 2010) will be announced shortly.

    *** Update *** Also do not forget the upcoming Webcast where Adrian Jenkins will provide an overview of this release and also address related questions:

    Information About Microsoft Project and Project Server Cumulative June Update - Tuesday, July 13, 2010 8:00 AM Pacific Time (US & Canada)

    For full details of this series please see http://blogs.msdn.com/b/chrisfie/archive/2010/06/16/microsoft-project-and-project-server-2007-and-2010-cumulative-update-webcast-series.aspx

    *** /Update ***

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: Cannot create or edit projects in Project Center

    • 3 Comments

    I am revisiting the topic of my earlier postings on this topic here, and here as I’ve since seen a couple of customers running into this, and my earlier posts were really focused on the tools (PowerShell) to fix the problem rather than the problem itself.  So to recap, the symptoms are that you cannot create or edit projects in PWA, and you cannot open Project Details Pages in Server Settings.  The error message received will be headed 'Project Fields" for the example of adding a new basic project plan or sample proposal and the error will say:

    This Web Part was unable to load.

    Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Server with the following ID:
    and will be followed by a GUID.

    The error when trying to open a Project in Project Center will depend on the stage in workflow, if any, and the associated Project Detail page - but will be similar to the above, but labeled, for example, "Proposal Summary".

    If the ULS logs are examined the GUID will be found by searching (Web Front End in a multi server environment), but will not be present in the Correlation column but in the Message text.  the message will be like:

    Web Part Exception Unique ID: 60278184-b699-405f-8a8b-54ed9a0aa6af System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.Office.Project.PWA.WebParts.ProjectFieldPartBase.GatherAndLoadCFList(Boolean bForceRefresh)     at Microsoft.Office.Project.PWA.WebParts.ProjectFieldPartBase.RebindGrid(Boolean forceRefresh)     at Microsoft.Office.Project.PWA.WebParts.ProjectFieldPartBase.PWA_OnLoad(EventArgs e)     at Microsoft.Office.Project.PWA.WebParts.PWAResiliencyPart.OnLoad(EventArgs e)

    and will be of level Exception with Tag ce9r.

    It is possible that the exception will be slightly different based on the configuration of the PDP being loaded for the specific Enterprise Project type. The key piece here is the NULLReferenceException and GatherAndLoadCFList and the cause is that the PDP infrastructure is not loaded correctly so it cannot get the data it is expecting for the web part..

    It is also possible that the same error could occur for different reasons - such as other script failures with the PDP infrastructure.  However, these would normally also show an IE script error, while this particular issue does not. (I may have an interesting posting soon about PC firewall products truncating the pdplib.js…).

    More evidence of this problem is that pdplib.js is not loaded, so will not be present if you View Source on the broken page in IE, or if you go to IE Developer Tools and look for the script.

    The cause of the issues I have seen is that a certain property of the PWA web site is set (PWAURL) that is expected to be NULL for the PWA site.  It should be set for project sites, but not the PWA site itself.  I can make this property get applied by turning on the Project Site Collaboration features on my PWA site and then associating it with a project – but have also seen customer scenarios where this certainly isn’t the current state of the system, so not sure if the same steps cause the same problem.  It is only an issue when you migrate to a different URL, such as during a move to 2010, or moving from production to test – so will not immediately break if you do have PWAURL set.  The reason for this is that PWAURL will actually be the same context of the current site –so the code will get the right result for the wrong reasons – but once you migrate, which carries over this URL then this will no longer be the case.

    For the remedial steps see the links in the first sentence – but wanted to give a better explanation of the issue and symptoms to make this more discoverable.

    Technorati Tags: ,
  • Brian Smith's Microsoft Project Support Blog

    June Security Hotfix for WSS V3 and Office and Project Server 2007

    • 2 Comments

    We released a security hot fix in June, that could have an impact on Project Server 2007, though if you have installed February 2010 Cumulative Update or later for SharePoint/Project Server you will have already received this patch – so do not need to read on.

    Microsoft Security Bulletin MS10-039 - Vulnerabilities in Microsoft SharePoint Could Allow Elevation of Privilege (2028554)
    See also KB979445  -> MS10-039: Description of the security update for Microsoft Office SharePoint Server 2007: June 8, 2010

    This fix was flagged as important, so it is possible for stand-alone installations with automatic updates configured that it has been downloaded and the binaries installed automatically.  The problem this could give is that the SharePoint Configuration wizard (psconfig) still needs to be run to complete the installation.  Until this is run you could see some bad behavior, such as not being able to browse the Central Administration site. 

    If you do not have a stand-alone installation then updates are blocked from installing automatically. The software update program checks the Windows Registry and blocks automatic installation on any Web server that does not contain the value "Serverrole"="SINGLESERVER" in the HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web server extensions\12.0\WSS\ key. 

    However, if you manually install this update, then you need to be sure to treat this just like any other SharePoint update and run the configuration wizard to complete the installation.  If you think you may be suffering the consequences of not running the configuration wizard and re-running now is not resolving things for you then please open a support incident.

    Thanks to Shazeb and Aik for suggesting this as a useful blog posting, and to Joerg_Sinemus for his original posting http://blogs.msdn.com/b/joerg_sinemus/archive/2010/06/09/june-security-hotfix-for-wss-v3-and-moss-2007.aspx.

    Technorati Tags: ,
  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: Server Language Pack walkthrough

    • 0 Comments

    I had a comment from Benno asking about language pack behavior in 2010 compared to 2007 so I though it was time to do a quick run through with some screen shots to show what’s changed.  As a reminder, the TechNet article is now live at http://technet.microsoft.com/en-us/library/ff700192.aspx and the download site can be found at http://www.microsoft.com/downloads/details.aspx?FamilyID=046f16a9-4bce-4149-8679-223755560d54&displaylang=en.  Don’t forget to change the language in the dropdown on the download page – unless you really just want the US English version to install on a server with a different base language. Also remember to rename the serverlanguagepack.exe if you are downloading multiple languages to install.

    A lot is still the same, for example the installation (except you download executables rather than ISO images).  My screen shots show the Arabic language pack – but the same steps apply to others too (Benno asked the question specifically regarding Arabic – and as a right to left language it does show some interesting behaviors).  You install on all severs:

    image

    then run the configuration wizard

    image

    Once this completes then you need to decide which sites you wish to enable the language to be available to.  This is a change from 2007, both in terms of the capabilities within Central Administration for the switch of languages, and how you make them available. In 2007 they would be available on PWA sites more or less immediately and were switched based on the users IE language preferences.  in 2010 the administrator goes to Site Actions, Site Settings, and clicks Language Settings:

    image

    in the Language Settings page will be displayed the Default Language, and check boxes for any Alternate languages you wish to make available.  You can also choose if any manually changed text translation is overwritten.

    image

    Once I check Arabic and OK, then I am able to go to my settings options (the drop down opened by clicking my display name – Brian Smith (CSS), and can choose which of the available languages I wish to use.  I also discovered after talking with Christophe, that this setting follows the IE language preference – which was the way to control things in 2007 – so if you are used to using that way you still have the option (once the language you want is enabled)

    image

    Et voila, Central Administration in Arabic!

    image

    I can then repeat the Site Action and my personal language settings options for other sites as required, such as the PWA site:

    image

    Notice that certain text is not translated but stays either in the base language - Project Web App, Home and Reminders (web part name) along with any manual entries to the Quick Launch, such as my ‘Test Under BI’ item.

    I can also switch languages for Project Sites (workspaces) that were originally provisioned in English, but again some original language content will not change – and in this case we see right justified English text that still reads left to right.

    image

    Once we have the Language Pack installed we can however choose to provision a PWA site in that new language;

    image

    And for any of our PWA instances we can choose which language any new Project Sites are provisioned in.  So here is a site provisioned in Arabic but viewed in English:

    image

    And the same site viewed in Arabic – with the only remaining English being my name and the project title.

    image

    Finally, my Arabic PWA site has finished provisioning – so I browsed to it…:


    image

    Oops.  I can’t read that.  But I knew I could get a better error if I enabled English on the site.  This is where it helps to memorize the positions of the menu options –  so I was able to get to here;

    image

    and check English.  Ah – we need a Gregorian calendar,

     image

    so over the Site Settings, Regional Settings (which I sort of could see from the original Arabic error)

    image

    and finally – here is our Arabic PWA site – first in English

    image

    and then with my settings changed to prefer Arabic:


    image

    Hopefully this gives you a good idea of the capabilities the language packs offer, and the extent of the translations.  the good news for 2010 is that we get a few extra languages, but also have the options for Central Administration and workspaces that we were used to seeing for our PWA sites in 2007 (and earlier!)

    Technorati Tags: ,
Page 1 of 2 (10 items) 12