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

November, 2012

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2007: Issue installing the October 2012 Cumulative Update

    • 3 Comments

    The release of the Project Server 2007 Cumulative Update for October 2012 appears to have a problem with the digital signing of one of the files and the installation will fail.  This issue affects both the Project Server 2007 - Project Server 2007 hotfix package (Pjsrvapp-x-none.msp; Pjsrvwfe-x-none.msp): October 30, 2012 – KB 2687536, and also the SharePoint Server roll-up package – SharePoint Server 2007 cumulative update server hotfix package (MOSS server-package): October 30, 2012 KB 2687533.  It also affects both the x86 and x64 versions.  This DOES NOT affect the individual SharePoint Server 2007 CU – KB 2760381, or the WSS 3.0 CU KB 2687535 – so if you need to update WSS or SharePoint Server then these packages can be used – but this will still leave Project Server un-patched.

    Thanks to Stéphane Deschênes of gp3 in Quebec City for bringing this to my attention.

    The problem file is the DATAEDIT.dll (assembly dataedit.dll.x64 or dataedit.dll.x86) and the message you will get will be “The installation of this package failed”:

    image

    The KB in the title bar will be either the Project Server one here Hotfix for Office (KB2687536) – or Hotfix for Office (KB2687533) if you are trying to load the SharePoint Server roll-up.

    In the Application event log you will see two Error events, 11937 and 1023 both with a source of MsiInstaller.  The text will be:

    Log Name:      Application
    Source:        MsiInstaller
    Date:          11/14/2012 8:33:32 AM
    Event ID:      11937
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          DOMAIN\User
    Computer:      <computername>
    Description:
    Product: Microsoft Office Project Server Application Server -- Error 1937. An error occurred during the installation of assembly 'DataEdit,fileVersion="12.0.6668.5000",version="12.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {AD9A0847-F41E-41F3-9B3C-CA9952D6D7E2}

    Log Name:      Application
    Source:        MsiInstaller
    Date:          11/14/2012 8:33:34 AM
    Event ID:      1023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          REDMOND\brismith
    Computer:      BriSmith2007.redmond.corp.microsoft.com
    Description:
    Product: Microsoft Office Project Server Application Server - Update 'Hotfix for Office (KB2687533)' could not be installed. Error code 1603. Additional information is available in the log file C:\Users<username>\AppData\Local\Temp\pjsrvapp-x-none_MSPLOG.LOG.

    The log file mentioned in the second event will give more information – the key piece will be the following:

    ….

    MSI (s) (3C:88) [08:40:11:480]: Assembly Error:Strong name signature verification failed for assembly '%1'.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key.
    MSI (s) (3C:88) [08:40:11:480]: Note: 1: 1937 2: {AD9A0847-F41E-41F3-9B3C-CA9952D6D7E2} 3: 0x80131045 4: IAssemblyCacheItem 5: Commit 6: DataEdit,fileVersion="12.0.6668.5000",version="12.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL"
    MSI (s) (3C:88) [08:40:11:480]: Note: 1: 2205 2:  3: Error
    MSI (s) (3C:88) [08:40:11:480]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1937
    Error 1937. An error occurred during the installation of assembly 'DataEdit,fileVersion="12.0.6668.5000",version="12.0.0.0000000",culture="neutral",publicKeyToken="71E9BCE111E9429C",processorArchitecture="MSIL"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {AD9A0847-F41E-41F3-9B3C-CA9952D6D7E2}
    ….

    At this time I don’t have any details of when the packages will be rebuilt – I will update this posting as soon as I have more information.

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2013 Requirements to build an OLAP Cube

    • 10 Comments

    There appears to be an error currently on our TechNet documentation at http://technet.microsoft.com/en-us/library/ee662106.aspx indicating that the version of the Analysis Management Objects required when building an OLAP cube from Project Server 2013 depends on the version of SQL Server you have running Analysis Services.  In fact it does not – and like previous versions of Project Server we actually require a specific version that our code talks to – regardless of which version it will actually be building the cube on.  For Project Server 2013 we require the ‘10.xx’ release so anything from RTM SQL Server 2008 Analysis Management Objects – version 10.0.1600.60 through to the SP2 of the SQL Server 2008 R2 10.50.4000.0 will work.  The only one that does not work in my testing is the SQL Server 2012 version.

    *** Update 11/13 - I should also point out that the requirement for the SQL native client is fulfilled by the SharePoint pre-requisite installer - so no need to add anything - but if you remove it then you will likely get an error like "Error: The 'SQLNCLI10' provider is not registered on the local machine" If this happens then just re-install SQL Native client 10.x such as the one from http://www.microsoft.com/en-us/download/details.aspx?id=30440 - look for sqlncli_amd64.msi. End Update ***

     

    If you have the 2012 version, or if you haven’t loaded any Analysis Management Objects then you will see the following error when trying to build a cube.

    image

     

    [11/12/2012 10:17 AM] Failed to build the OLAP cubes. Error: The attempt to build the OLAP database on server BriSmithSQL failed, the SQL Server Analysis Services Analysis Management Objects (AMO) client software may not be installed on this server, please install/update the client on this server and retry. The underlying exception was: Could not load file or assembly 'Microsoft.AnalysisServices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

    The SQL Server 2008 R2 SP2 version is the most recent and can be found in the feature pack at http://www.microsoft.com/en-us/download/details.aspx?id=30440 and you are looking for SQLSERVER2008_ASAMO10_amd64.msi (which is the x64 version) (***Update *** corrected the name - thanks Adrian!).  Direct download link is here. I haven’t tried building a cube against a SQL Server 2008 instance – that may need to use the earlier SQL Server 2008 feature pack – most recent is SP2 if you find the R2 version above doesn’t work.

    For those still having a hard time finding where we have hidden the cube building option (I admit it – it took me a while…) can find it either by going to Central Administration, Manage Service Applications, Project Server Service Application (or whatever you have called yours) and then use the drop down for the specific PWA site you are interested in and click Manage which will take you to the following page – and OLAP Database Management is the link you need:

    image

    Or Central Administration, General Application Settings, and click Manage under the PWA Settings header.

    image

    If you go this root you may need to change the PWA site in the upper right hand corner.

    image

    And if you are using the preview of Project Online (or you are reading this after the full release) and can’t find the link to OLAP cubes it is because that feature isn’t available in the online version.

  • Brian Smith's Microsoft Project Support Blog

    Project Server Databases–Please don’t mess with the default options

    • 0 Comments

    We have some guidance out on TechNet about the recommended settings for SQL Server for our various versions – so for example we recommend for 2010 at http://technet.microsoft.com/en-us/library/ee662107.aspx that you set AUTO_CLOSE to OFF, and AUTO_UPDATE_STATISTICS_ASYNC to ON.  But we don’t always make a show of telling you what NOT to change.  A good guide is to leave things at the default settings unless we recommend otherwise.  For example, in 2013 we don’t recommend the UPDATE_STATISTICS settings because we, like SharePoint in 2010 and 2013, now have a timer job for that purpose.

    One good example of this was a case I worked today with my colleague Vikram.  The customer had an issue connecting from Project Professional to PWA – the error was “The following job failed to complete.  Job Type: Load, Error ID: 42(0x2A), Error Description: An internal error occurred.  My apologies if you are reading this having searched for that error – it has many causes and this one is probably way down the list of likely ones…It usually means it couldn’t get the enterprise global from the database.

     

    image

    In this case we could reproduce the issue with the customer’s database, and soon found the SQL error that was being thrown (The ‘More Info’ button in the dialog, the ULS logs and SQL Profiler helped here)  – “Arithmetic overflow error converting numeric to data type numeric” as a result of executing the stored procedure MSP_WINPROJ_READ_ENTERPRISE_CUSTOM_FIELDS, which also has an set of GUIDs passed in that represent the custom fields of interest.  However, all the data looked OK, and it even gave the same error with a NULL parameter indicating no custom fields.  After trying a few things it was obvious from debugging the stored procedure that it had some issue with the eglobal version number – which should have been ‘14’ but was showing blank. The value in the database being queried was just fine - 14.1461140000, the same as on a working system I was comparing with.  But it got me thinking – it turns 14.1461140000 into 14 – I wonder if some DB options would make that give an arithmetic overflow?  Sure enough – the database had an option set to True for Numeric Round-Abort – so this implicit cast was being aborted.

    I thought I’d also look to see how 2013 behaved with this wrong setting – and as I expected it also failed, but with a slightly different (but no more helpful) error on the client side (please click the link if you too see a message that you feel could be more helpful – I did…) – though to be fair the failure is slightly different just caused by the same root cause.

    image

    But at the back end it is very much more helpful!  In the ULS logs I saw:

    System.Data.SqlClient.SqlException (0x80131904): Error 1934, Level 16, State 1, Procedure MSP_UPDATE_USER_ACTIVITY, Line 14, Message: UPDATE failed because the following SET options have incorrect settings: 'NUMERIC_ROUNDABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. 

    This is a great example of the improvements to logging we now have in 2013 to try and ensure that the log will give us the full answer – rather than just being a clue as to where we should go and look next.

  • Brian Smith's Microsoft Project Support Blog

    Project and Project Server October 2012 Cumulative Update

    • 0 Comments

    Just posted at http://blogs.technet.com/b/projectadministration/archive/2012/11/05/microsoft-project-server-and-sharepoint-server-2007-and-2010-october-2012-cu-announcement.aspx

    Remember, if you didn’t load the 2010 August 2012 Cumulative Update (CU) that the October one will also require SP1 to be installed.

    Delays on the 2007 SharePoint and Project packages, and also the roll-up SharePoint/Project package for 2010.  No 2007 client CU this cycle.  So if you just need the individual Project Server 2010 October CU you are good to go!  I’ll post again once I have an idea on the targeted release for the others – early indication is a couple of weeks…

    *** Update 11/14/2012 - The individual 2010 Server package is out - still waiting for the roll-up, and an issue has been found with the 2007 Server package - see http://blogs.msdn.com/b/brismith/archive/2012/11/14/project-server-2007-issue-installing-the-october-2012-cumulative-update.aspx. ***

Page 1 of 1 (4 items)