Project Server 2007: Problems with ActiveX Controls after loading the October 2011 CU

Hi All, it appears we have some issues around the download of ActiveX controls for the Project Center and other pages in Project Web Access for Project Server 2007 after loading the October 2011 Cumulative Update.  Thanks to Alex for his work on this one and especially to Marc for for quickly coming up with a temporary fix.  We are already working on an update to resolve this issue – but for now Marc’s fix will help you overcome the problem.

The symptom will be that you are given a message to download the ActiveX controls, which can be perfectly normal if we have updated them in a CU – however in this case the download will not complete and all the usual workarounds of manually removing and deploying etc. do not resolve the problem.  The cause is that we did not deploy new ActiveX controls with this release – but we updated a version check as if we had done.  So Marc’s temporary fix is just to ignore the result of the version comparison.  If you happen to be upgrading from a much older SP or CU and we have since updated the ActiveX then this may give unexpected results – but certainly if you are already at a recent CU this is a good temporary solution.  And of course – if you are not seeing this issue then you don’t need to make this change.

Once we have more information I will update this posting – particular around the behavior when we do fix the problem and whether you would need to revert the change first (as otherwise we may not replace the ‘updated’ file).

On to the workaround:

  1. Navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\PWA\LIBRARY
  2. Make a safe copy of the file SHELL.JS (you may need to put this back in place before future updates)
  3. Open the file SHELL.JS with NOTEPAD and modify the following lines:
    • function PJ_CompareBuildVersion(clientBuildVersion, serverBuildVersion)
    • {
    •    var rgClientBuildVersion = clientBuildVersion.split(",");
    •    var rgServerBuildVersion = serverBuildVersion.split(",");
    •    for(var i = 0; i < rgClientBuildVersion.length-1; i++)
    •    {
    •       if(rgClientBuildVersion[i] > rgServerBuildVersion[i])
    •            return 0;
    •      if(rgClientBuildVersion[i] < rgServerBuildVersion[i])
    •            return 0;
    •    }
    •    return 0
  4. Save the file SHELL.JS
  5. In Internet Explorer reload any of the PWA pages with the ActiveX grid and all should be good!


Sorry for any inconvenience this has caused – and don’t hesitate to contact Microsoft if you have any further issues with this cumulative update.

Comments (7)

  1. _-DFS-_ says:

    hi Brain!

    Yes, your decision helps.

    Will it  be included in following CU?

  2. Mike says:

    This did not work we are still stuck at loading grid on the project center and resource center. I then applied the Dec 2011 to 2 different environments. It solved the issue on one but not the other.

    I verified it is taking the new shell.js by pathing directly to the shell.js embedded in the html file and it is showing 0's however the grid still won't load.

    Also I noticed after the Oct 2011 update the download controls "click here" button is a javascript that points to downloads/downloads=hb=1,"undefined" and the url adds a Undefined in the _layouts page and then goes to a 404 file not found. if I remove the undefined from the url it attemps to download the controls then fails. This incorrect url was also fixed in the Dec 2011 update on one box but not the other.

    Any help?

  3. Once you load the new December CU Mike then you need to make sure the edited .js file is replaced with the good one.  It isn't clear if you mean new shell.js as the edited one or the original.  Basically the edit just said 'ignore any errors' so it would use the grid controls it had rather than trying to download new ones.  The initial problem in your 2007 system may be that there weren't any – either becuaser they had never been downloaded or you had manually removed as a troubleshooting step.  With the right js file and the December CU it should recognize that it needs to download the controls and they will actually be there (which they were not in the October CU).  Let me know if you still have an issue.

    Best regards,


  4. Mike says:


    Yes sorry for confusion I tried both shell.js files from Dec 2011 which shows a 1 and a negative 1 in place of 0's. So i've tried both and both don't work correctly. However I tried on a completely seperate machine that I wasn't using to troubleshoot but was able to access it before and it doesn't work on that workstation either, using any of the Shell.js scripts.

    Also I am not sure why the click here undefined error is occuring on workstations that have never downloaded the controls before.

    Any further insight into the issue? Thansk for your help!

  5. Hopefully this KB should help with manually setting things up Mike – not sure what's going wrong here:…/818046

    Best regards,


  6. Maureen Parker says:

    Thanks for this.

    Have you heard of anyone having problems with users logging into Project Server e.g. the Login permission not working after loading October 2011 CU?



  7. Hi Maureen, we have heard of a few isolated cases where ADSync appears to run OK but the users are not then populated in the Team Members group.  That would be worth checking.  A quick workaround until we find a cause and resolution would be to add the AD group you are using to sync at the root PWA site directly in SharePoint.

    Best regards,


Skip to main content