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

July, 2011

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: Benign OWSTimer unhandled exception popup – System.Security.Cryptographic.CryptographicException


    Thanks to Paul Andrew for his permission to re-post this issue for the Project Server audience.  Probably not everyone has Visual Studio on their Project Server 2010 system – but I know I do, and get this error regularly (every 24 hours as Paul mentions  – and have heard of this issue from others too.  It will also pop up when you run the configuration wizard too, so with SP1 and the June CU out I thought it worth bringing this to your attention.  Here is the reason and some potential workarounds.  Thanks again Paul!

    Have you seen this popup exception message from the Visual Studio Just-In-Time (JIT) Debugger?


    Here’s the resulting event log error:

    An unhandled exception occurred and the process was terminated.

    Application ID: DefaultDomain

    Process ID: 6148

    Exception: System.Security.Cryptography.CryptographicException

    Message: Keyset does not exist

    StackTrace: at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)

    at System.Security.Cryptography.SafeProvHandle._FreeCSP(IntPtr pProvCtx)

    at System.Security.Cryptography.SafeProvHandle.ReleaseHandle()

    at System.Runtime.InteropServices.SafeHandle.InternalFinalize()

    at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)

    at System.Runtime.InteropServices.SafeHandle.Finalize()

    If you see this error message from SharePoint 2010 you can relax, nothing bad is happening. When SharePoint 2010 and Visual Studio 2010 are both installed on the same machine you may see this error every 24 hours. This occurs when the OWSTimer service has a regular process recycle and in the shutdown of the old process an exception is raised. The exception doesn’t interfere with the normal process shutdown and recycle and is only ever seen if you have a JIT debugger installed on the machine. You should never see this error on a production SharePoint 2010 server, because you should not be installing Visual Studio 2010 on those servers. You can safely ignore these exceptions and close the window, or leave it there. You actually cannot debug the process, because it will already have been closed by the time you click the button and start your debugger.

    You can avoid the popup exception message entirely by disabling JIT debugging on your machine. Bear in mind this will disable JIT debugging for all applications on the machine.

    To configure the server to no longer show a dialog when an unhandled exception occurs, use the registry editor to delete the following registry keys:

    · HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

    · HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

    On a 64-bit operating system also delete the following registry keys:

    · HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

    · HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

    More details on JIT Debugging are at:

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: Problems when bulk editing too many resources


    I came upon this bug while working on my earlier posting regarding Reporting Database Refresh – and specifically trying to bulk edit lots of resources at once in the Resource Center.  It appears we throw a very complex and large query over to SQL and it has some issues parsing it.  The failure is pretty silent for the user – who just gets the Resource Center page back and might assume everything worked ok.  However there will be no jobs in the queue, the change will not have been made – and the resources will all be left check-out (as you will find out if you try the process again!).  The answer is to check all the resources back in again (or at least the ones you checked out – someone else may be doing work with other resources) and then reduce the number you have selected and try again.  The size and complexity of the query depends mainly on the number of resources, but also will be affected by the number of custom fields at the resource level – but my finding were that you could edit around 400 resources at once with bulk edit if you had around 24 resource custom fields.  Your mileage may vary!

    The errors that are seen are interesting – in that it appeared to depend on the severity of the issue.  With just over the triggering number of resources the failure was pretty silent in the USL logs and SQL Server – exceeding by a few more (20+) then gave errors in SQL Server of Error: 208, Severity: 16, State: 0 (which tends to mean object not found, and I’m guessing it was not finding the temporary table it wanted to use in part of the query) – but still nothing much in the ULS logs – and it was only when increasing the number of resources close to 500 did I see the following in SQL Server

    • Exception - Error: 191, Severity: 15, State: 1
    • User Error Message - Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.

    and then the ULS logs gave me an exception too:

    • 07/15/2011 15:49:02.07 w3wp.exe (0x19B8) 0x220C Project Server General 0000 Exception Exception occurred in method Microsoft.Office.Project.Server.BusinessLayer.Resource.ReadResources Microsoft.Office.Project.Server.DataAccessLayer.FilterDal+FilterException: Error during filter query execution. Query: declare @ResUid UniqueIdentifier; set @ResUid = eb736432-cd8d-4db2-8d9b-ad57bb3f0085; declare @EntUids NVarChar; set @EntUids = e162554e-45f0-496a-a86e-0010ef91ae13,bb57a927-1b4b-42e9-b29b-001c63e0b53c,... followed by hundreds more GUIDs

    I’ll be logging this bug internally too so we can consider a fix for it – or at least a limit on the resource selection so you don’t run in to this one.

  • Brian Smith's Microsoft Project Support Blog

    Some blog updates to my site to make the most of IE 9


    Some of you may have noticed that my blog now prompts if you want to pin it to your Task Bar and then it will also give you some Jump List items to go to the recent posts directly, or over to the Project Administration blog.  I hope you find this useful.  If you haven’t seen these features or the prompt then perhaps you are not running IE 9?  Or have IE 9 running in compatibility mode?  Now is the time to take a look!

    You can either use the prompt in the floating bar or just drag the tab down to your task bar in Windows 7 (Server 2008 R2 with the Desktop Experience feature – as I am using in the first screen shot) and it will look something like this:


    and if you ‘right-click’ then the jump list looks like this (this time from Windows 7)


    Let me know if you think there are other useful Tasks to add to the jump list.  If you want more details on IE 9 then the Beauty of the Web site is a good starting place – and if you want to do something similar then take a look at  Thanks also to Stephanus Schulte who shared some of the details on doing this for our MSDN/TechNet blogs – as he has done at Enjoy!

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: Reporting Database Refresh failing with large resource pools


    *** Update *** - fix made it into the August CU -

    •The reporting database update job fails in Project Server 2010. Therefore, other jobs that are marked with "waiting to be processed" that follow the update job in the queue are auto canceled. - also in the roll-up server package -



    If you have a large(ish) resource pool, with over about 1500 resources then you may run in to an issue with the Reporting Database Refresh not completing correctly – with the initial symptom that many of the Reporting (Resource Sync) and all of the Reporting (Project Sync) jobs may just say Cancelled and if you click through to the errors from the queue you will see:

    • Reporting message processor failed:
      • ReportingResourceChangeMessageFailed (24008) - A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.. Details: id='24008' name='ReportingResourceChangeMessageFailed' uid='e3caf6d3-cc85-4078-90d3-1ce1ad929776' QueueMessageBody='Resource UID: '7d536aef-9be1-46c7-971a-286e384918c8'. ChangeType='Add'. ResourceChangeType='All'' Error='A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.'.


    • Reporting message processor failed:

      • ReportingProjectChangeMessageFailed (24006) - A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='bfd6372f-b545-4368-8b8e-00807de566f0' QueueMessageBody='Project UID='65cae55a-48e3-44fe-826e-f4f7fa478cc8'. PublishType='All'' Error='A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.'.

    and if you look in the ULS logs then you will see something like:

    07/14/2011 12:19:04.56    Microsoft.Office.Project.Server (0x2084)    0x2538    Project Server    Reporting    auhd    High    PWA:http://Server/PWA, ServiceApp:Project Server Service Application, User:DOMAIN\User, PSI: [RDS] ULS Event: ReportingResourceChangeMessageFailed was associated with exception: Microsoft.Office.Project.Reporting.ProjectReportingPublic.ReportException: A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ResourcesChangedMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext)    ae4c9ca3-2a2c-44d1-b7d3-3d54589fcc8a

    07/14/2011 12:29:16.10    Microsoft.Office.Project.Server (0x2084)    0x3868    Project Server    Reporting    atwr    High    PWA:http://Server/PWA, ServiceApp:Project Server Service Application, User:DOMAIN\User, PSI: [RDS] ULS Event: ReportingProjectChangeMessageFailed was associated with exception: Microsoft.Office.Project.Reporting.ProjectReportingPublic.ReportException: A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run.     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RDSBaseMessageProcessor.CheckIfAllowedToProceed(ReportingBaseMessage msg, MessageContext msgContext, Group messageGroup, JobTicket jobTicket)     at Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.ProjectPublishMessageProcessor.HandleMessage(Message msg, Group messageGroup, JobTicket jobTicket, MessageContext mContext)    ae4c9ca3-2a2c-44d1-b7d3-3d54589fcc8a

    The first message will appear for cancelled resource sync jobs, and the second for projects.  If you don’t happen to notice this issue, then the next thing you might see are failed reporting publish jobs such as the resources that assignments belong to may not exist in the reporting database (if they were among the cancelled ones.  These errors will look something like this:

      • Reporting message processor failed:
        ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='6b806909-7a24-4409-8b80-b898f4a904a9' QueueMessageBody='Project UID='79bf1075-a46a-467c-828a-24a1dc00ebbb'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmAssignment_ResourceOwnerUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmResource", column 'ResourceUID'. The statement has been terminated.'.
      • Queue:
        GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx. Details: id='26000' name='GeneralQueueJobFailed' uid='29aca4ff-eb33-46ac-b6e6-1126f8532dae' JobUID='8ed284d5-7015-4e6e-a344-6380aae4b0d1' ComputerName='ServerName' GroupType='ReportingProjectPublish' MessageType='ReportProjectPublishMessageEx' MessageId='1' Stage=''. For more details, check the ULS logs on machine ServerName for entries with JobUID 8ed284d5-7015-4e6e-a344-6380aae4b0d1.

    To better understand the reason for the failure it may help to understand more about the reporting database refresh process.  It is a process that gets automatically started based on certain conditions that would mean the data in the reporting database would not be consistent – and the most common of these is that some metadata such as the custom fields have been restored from archive.  Once this happens then the reporting data may be incorrect – as it may have custom field data that no longer makes sense – for CFs that were not in the archive so they no longer exist.  If you monitor the queue you will see an initial job that says Reporting Database Refresh and this will soon change to Reporting Database Refresh(Sleeping) – which is ok.  You will then see several sets of jobs getting added at intervals.  It will look something like this:

      • Reporting (Fiscal Period Sync) – Immediate
      • Reporting (Resource Capacity Range Sync) – Immediate
      • Reporting (Lookup Table Sync) for each lookup table, and added to the queue 5 minutes after the Reporting (Resource Capacity Range Sync)
      • Reporting (Custom Field Metadata Sync) for each custom field, and added to the queue 5 minutes after the Reporting (Lookup Table Sync)
      • Reporting (Entity User View Refresh) for each view and added at the same time as the Reporting (Custom Field Metadata Sync)
      • Reporting (Resource Sync) for each resource and added to the queue 5 minutes after the Reporting (Entity User View Refresh)
      • Reporting (Workflow Metadata Sync) for stage, phase etc. – added 5 minutes after Reporting (Resource Sync)’s finish
      • Reporting (Enterprise Project Type Sync) for the EPT’s – added at the same time as the Reporting (Workflow Metadata Sync)
      • Reporting (Project Publish) for each project and added 5 minutes after the Reporting (Enterprise Project Type Sync)
      • Reporting (Timesheet Assignments Refresh) – added 10 minutes after the Reporting (Project Publish)
      • Reporting (Timesheet Project Aggregation) one for each timesheet period – added at the same time as the Reporting (Timesheet Assignments Refresh)

    While all this is going on the initial job will wake every few minutes to make sure things are still going along OK – and it is at this point that the bug this blog is about can break things.  It is a timing issue and it is possible that when the waking job checks to see if all is OK it gets a response it is not expecting so it thinks things have failed – writes a failure message to one of our database tables along with a failure time.  Subsequent jobs are checking this table too and will see that things have apparently failed so they will just cancel (or some of the jobs may show “Failed but not blocking correlation”).  This is the reason for the error message saying “A RDS message that was spawned during a RDB refresh operation attempted to execute outside of the time range in which the refresh operation run” – as the current time does not fit between the apparent start and end time of the reporting database refresh.

    So how to recover?  There will be a fix coming along – and my hope is that it will make the August 2011 Cumulative Update – but there is a workaround if you should find yourself in this situation.  You will need to force a reporting update for all the resources and all the projects. 

    For the resource you can open them in Resource Center and Save (no change needed), and you will see the Reporting (Resource Sync) and the Reporting (Timesheet Project Aggregation) jobs kicked off for this user.  The reason you need to refresh all resources and not just the ones that failed is this second group of jobs – the Reporting (Timesheet Project Aggregation) – which puts data from the admin lines of the timesheets into the MSP_EpmAssignments and MSP_EpmAssignmentsByDay tables.  You can use the Bulk Edit option to enable you to do multiple resources at once but for this to work you need to make a change (you could add a new CF and just type some text into it)  – and you also need to be sure all your resources are checked in.  You may find the page a little unresponsive when you hit Save (you might want to limit it to a few hundred at once – I did around 200 at a time and that worked for me .  A trick that might help – if you select a group of rows using the shift-click you can then check the select box for all of the selected rows.  I’m still playing around with the options here – I will update the post if I find some new tricks and tips.

    For projects you will need to re-publish all the plans.  You can do this either using ProjTool from the SDK or use a PowerShell commands made available by the code gallery sample at  The getting started guide on that page has a sample that can do a check-out, publish and check back in.

  • Brian Smith's Microsoft Project Support Blog

    Project Server 2010: SP1 and June CU Questions and Answers


    Firstly I should announce that the ‘refreshed’ version of the June 2011 Cumulative Updates are now live on the support site.  If you downloaded an earlier version then please get the latest – same URLs, but you will see a revised date (for example on the Project Server 2010 server package that also includes SharePoint Foundation and SharePoint Server you will now see “Article ID: 2536600 - Last Review: July 11, 2011 - Revision: 4.0” and the Note: This is build 14.0.6106.5002 of the cumulative update package.  The fixes over and above the original CU are the first two of the “Known Issues” posted on the KB article itself:

    Known issue 1
    If you install an earlier build of this hotfix package on a SharePoint server that has .NET 4.0 installed, you cannot synchronize user profiles from AD and LDAP into the SharePoint User Profile Service application database. The user profile synchronization export process fails. Additionally, the System.PlatformNotSupportedException exception shows in Event Viewer.
    Note This issue is fixed in build 14.0.6106.5002 of this hotfix package

    Known issue 2

    After you install an earlier build of this hotfix package, the following services may fail at either runtime or the provision process if you run these services by using a user account other than the farm administrator account:

    • Session State Service
    • Secure Store Service
    • Business Data Connectivity (BDC) Service

    Note This issue is fixed in build 14.0.6106.5002 of this hotfix package.

    and the third is one mentioned by Adrian in our Project Server 2010 Service Pack 1 and June Cumulative Update webcast regarding Fix 30793 – When saving a timesheet (also creating), custom field values for *other* timesheets are deleted.

    *** Update 8/26 - Just noticed that for the single Project Server package still says the original release number of 14.0.6106.5001, but I checked and the actual download you will get is the latest - 14.0.6106.5002.  I have asked for the article to be updated.  Also noticed that the package referenced above has the KB showing Revision 6 now rather than the 4 mentioned above.  The article has been updated but no new patch revision to worry about. ***

    We had a number of questions came up during the session and we thought it would be useful to summarize them here, for those who did not attend the webcast or those who didn’t get a chance to look at the Q&A section as we were going along.  Thanks to all who asked such great questions!

    Question: Do we need to load the SharePoint Foundation SP1/June CU?

    Answer:  It is included in some of the roll up packages, so you may not need to explicitly install it.  However, if you are just going to load the Project Server 201 June Cumulative Update package (KB 2536586) and you have not installed previous CUs then you will need the SharePoint CU (or SP) or you will get the jsgrid issue reported when we shipped the August 2010 CU - – the view failed to load, and Exception occurred in method Microsoft.Office.Project.Server.BusinessLayer.Project.ProjectGetProjectDetailsForGridJson.  If you are unsure if it is in a package then scroll down to the complete file list.  SharePoint Foundation stuff will be the files like sts-x-none.msp, and ones starting with wss.

    Question: Any requirements for Office 2010 app's?

    Answer:  It isn’t necessary to also upgrade the client applications but it's certainly a great idea to update both Project and Office to SP1.

    Question:  What's the minimum CU, both client and server, that we need to be on before applying SP1?

    Answer:  No minimum CU is required. You can go directly from the initial release to SP1 if desired.

    Question:  Did the fixed work task type get fixed for entry in PWA?

    Answer:   Yes! Additionally, effort driven tasks are supported.

    Question:  Does SP1 contain the June CU or do I need to install them both?

    Answer:  SP1 does not contain the June CU, although the June CU does contain much of what is in the Service Pack.  It is advisable to load both.

    Question:  Install June CU then SP1 or vise versa?

    Answer:  Technically, it doesn't matter. It is usual to install SP1 first and then June CU (and the configuration wizard can just be run once – after both are loaded, assuming you are doing it right away).

    Question:  Is hotfix 2534413 included in the June CU?

    Answer:  That hotfix was the Project 2010 April 2011 Cumulative Update, and is included in the KB 2536590 hotfix – the Project 2010 June 2011 Cumulative Update.

    Question:  Is there a list of bugs/fixes available for the 2nd June CU that will be coming out in a week or so?

    Answer:  There is – and I also mention what is fixed above.

    Question:   In June 2011 KB the 5th items says when you apply updates using PWA, your updates are lost. We had that issue in PS 2007 fixed it with Feb 2011 CU. After migration to 2010 we are getting it in PS 2010. The June 2011 restricts the issue from happening further. But is there a way to restore lost hours?

    Answer:  Best to contact support for assistance with this type of issue - and as it relates to a bug there will be no charge. The support engineer will be able to help identify if and how hours can be re-applied.

    Question:  Where can I find the links for the June CU?

    Answer:  We will get the latest link up on the Project Administration blog shortly,  or search

    Question:  We run this on a VM, with the server set to dynamic memory, it simply takes as much memory as it could, is that normal, and is there a way\config setting to limit this?

    Answer:  You can set an upper limit for Dynamic memory (certainly for HyperV) - if nothing else is using it then why would you want to limit? If you have conflicting apps then you can also set priority of memory usage.

    Question:  I missed the reasoning behind the statement that we should reconsider our settings for "manually scheduled tasks can be published to team members"

    Answer:  At release you could not record time-phased data against manually scheduled tasks so this was one reason you might have wanted to check that option. You may still want to restrict publishing if you are using manually scheduled tasks more for longer term planning.

    Question:  I have a resource who can not see his tasks in PWA. PWA displays loading and then "Cannot communicate with the server. Verify your connection and try again.". Has this problem been resolved? Only one resource has this problem.

    Answer:  I don't know off the top of my head - sounds data related if one resource is affected - or might be some customization of their view. Ping me via my Blog contact and I can give some pointers.

    Question:  Does the auto publish also close the projects it publishes?

    Answer:  It will submit a request to publish after auto approval so this will be queued and will actually when the job gets to the top of the queue, assuming the plan is checked in (or checked out in the same session doing the approval/publish).   The publish itself does not check the project out.

    Question:  Earlier it was mentioned re: multi-browser support, that Safari was supported not on PCs but only on PowerBooks. Did you guys mean any/all Apple native hardware? Or is that PowerBook, specifically? For instance, supported on iPads?

    Answer:  Although our testing was on desktop and laptop Apple hardware we are not aware of any issues on other Apple platforms such as the iPad and have heard anecdotal references to it working.

    Question:  Can you provide the URL's for the links to the excel workbooks that contain the list of fixes?


    Question:  If we upgrade both SharePoint Foundation and Project to SP1, is there a sequence to follow?

    Answer:  Recommendation is SharePoint Foundation first - but either way will work, and you only need to run PSCONFIG after loading both.

    Question:  When synching a Project 2010 file with a SharePoint 2010 task list, does SP1 now support multiple resources for each schedule task?

    Answer:  That hasn't changed.

    Question:  Regarding the new AutoPublish checkbox, would like to make sure I completely get it. The functionality looks great, no need for code or for publishing after the rule is run, correct? If so, that is great! Can I also take advantage of this functionality to create a generic / general rule that matches all updates on all projects, check the box, and have myself a completely automated task accept-update-publish function? I ask because customers have asked to program this before and we've had to use PSI previously. Would this scheme work to do it OOTB now?

    Answer:  Yes  - that is the intention of this feature. My top pick for SP1.

    Question:  Please could you let me know on what is the largest project schedule (task activities) uploaded and managed within the server environment as we are implementing Project Server 2010 within the mining environment here in South Africa as in 2007 it was a bit of a challenge?

    Answer:  Our suggested maximum is around 400,000 tasks – but there are many other factors that would need to be taken into account.

    Question:  When synching a Project 2010 schedule to a SharePoint 2010 Task List, does the Gantt chart now support summary tasks (similar to MS Project)?

    Answer:  This has not changed with SP1 and summary tasks are still represented as folders containing the sub-tasks within the SharePoint Task list.

    Question:  Does the project server 2010 SP1 contain the SP 2010 SP1?

    Answer:  There is just one SP covering Office Servers which includes Project Server 2010 SP1.

    Question:  Are budget resources supported in templates launched by EPT's in PWA?

    Answer:  No, these are not supported for projects created from templates directly on the server, when not using the Project Professional client.

    Question: Is there any way for users to add tasks that are synced from project server (into the outlook tasks) into their calendar as well? Many of my clients liked this feature in the past, and find the task only one less friendly to use.

    Answer:  There haven't been any changes in SP1 to expand the Exchange/Project server integration and how those tasks appear in Outlook.

    Question:  Hi, could you advise on any improvements with archiving of projects, simplification primarily.

    Answer:  There are no changes to project archiving.

    Question:  Project to SharePoint synch - does it support dependencies other than FS?

    Answer: (Not answered on the webcast, but the answer is…) SharePoint only supports Finish-to-Start predecessors without constraints or lag times.

    Question:  Is there a limit to how many approvals/publishes can be done at a time?

    Answer:  Not aware of a limit – but the questioner apparently had seen approvals fail is ~500 tasks updates.  We would need a support case if anyone wants to dig deeper on this issue – no known issue were found in our databases.

    Question:  How soon before the SP1 demo VM of Project server 2010 will be available?

    Answer:  We will pass the feedback on to the marketing team letting them know that the SP1 demo VM is needed.  But a great place to practice loading the updates!

    *** Update 7/13/2011 - added an additional useful Q&A

    Question:  Where is the best place to go for details on patching Office Web Apps to SP1?


Page 1 of 2 (6 items) 12