#ProjectOnline Export Capacity Planning data to #Excel issue #PPM #PMOT #Office365 #MSProject

June 30, 2018 at 7:44 am | Posted in Administration, Configuration, Fixes, Functionality, Information, Issue | Comments Off on #ProjectOnline Export Capacity Planning data to #Excel issue #PPM #PMOT #Office365 #MSProject
Tags: , , ,

Just a quick post to highlight an issue I came across that I thought might be worth posting about in case anyone else runs into the same issue. In Project Online, in PWA you can export most of the grids to Excel. I was testing something in PWA and came across an issue exporting the Capacity Planning grid to Excel, I clicked the button but nothing happened, the details grid would flicker when the button was clicked but nothing after that. Opened the browser debugger and tried again, no console errors but looking at the Network log an error 500 was thrown for the ProjectServer.svc:

SNAGHTML57ccc6b

Looking at the response I could see a general unhandled exception was thrown caused by a key not being present in the dictionary:

image

Looking at the request payload I could see two resource GUIDs were included:

image

Looking at the grid data there was only one resource present:

image

Looking back in the Resource Center, I did have two resources selected:

SNAGHTML586d081

One being a Cost resource, I deselected the Capex resource and tried the Export to Excel from the Capacity Planning page and all worked as expected.

If you do run into the issue with exporting the Capacity Planning grid to Excel, check the resource types you have selected, deselect Cost and Material resources then try again and hopefully that will resolve the issue for you. I will mention this to the Project team at Microsoft to see if this is something they are already aware of.

Advertisements

Change required for #SharePoint Online / #ProjectOnline REST API calls when using WebRequest #PowerShell #dotnet #office365dev

May 9, 2018 at 7:00 am | Posted in .Net, Administration, Customisation, Functionality, Information, Issue, PowerShell | 2 Comments
Tags: , , , ,

Just a quick blog post to highlight a change the is required when querying Project Online / SharePoint Online REST APIs in code when using the WebRequest class. Previously the PowerShell code sample below would work and authenticate with no issues:

#add SharePoint Online DLL - update the location if required
$programFiles = [environment]::getfolderpath("programfiles")
add-type -Path $programFiles'\SharePoint Online Management Shell\Microsoft.Online.SharePoint.PowerShell\Microsoft.SharePoint.Client.dll'

#set the environment details
$PWAInstanceURL = "https://PWAURL"
$username = "username" 
$password = "password"
$securePass = ConvertTo-SecureString $password -AsPlainText -Force

#set the Odata URL with the correct project fields needed,
$url = $PWAInstanceURL + "/_api/ProjectData/Projects()?`$Filter=ProjectType ne 7&`$Select=ProjectId,ProjectName,ProjectPercentCompleted,ProjectOwnerName"

#get all of the data from the OData URL
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass)  
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()
$reader = New-Object System.IO.StreamReader $response.GetResponseStream()
$data = $reader.ReadToEnd()
$results = ConvertFrom-Json -InputObject $data
$results.d.results 

There has been a change in Office365 and this would now generate a 401 unauthorized error as seen below:

image

It is now required to use the authentication cookie, not sure if this is a permanent change or a temporary issue. Adding the line below resolves the issue:

$webrequest.Headers["Cookie"] = $spocreds.GetAuthenticationCookie($url)

#get all of the data from the OData URL
[Microsoft.SharePoint.Client.SharePointOnlineCredentials]$spocreds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($username, $securePass)  
$webrequest = [System.Net.WebRequest]::Create($url)
$webrequest.Credentials = $spocreds
$webrequest.Accept = "application/json;odata=verbose"
$webrequest.Headers["Cookie"] = $spocreds.GetAuthenticationCookie($url)
$webrequest.Headers.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f")
$response = $webrequest.GetResponse()

This change would be applicable to all of my PowerShell code samples that query the Project Online OData API found here: https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=User&f%5B0%5D.Value=PWMather&sortBy=Date

Hope that helps

#ProjectServer / #ProjectOnline error opening Enterprise Resource Pool #MSProject #Office365 #PPM

October 10, 2016 at 8:17 am | Posted in Administration, Functionality, Information, Issue, Workarounds | Comments Off on #ProjectServer / #ProjectOnline error opening Enterprise Resource Pool #MSProject #Office365 #PPM
Tags: , , , , ,

A quick post to highlight an issue and workaround for opening the Enterprise Resource Pool in Project Pro using the Open button on the Resources tab in the Resource Center:

image

If you try and click the Open button with no resources selected in the grid you will get the error below:

“This action couldn’t be performed because Office doesn’t recognize the command it was given” :

image

Select at least one resource in the grid then this command will work fine.

Error creating Project Sites from custom site template in #ProjectOnline / #SharePoint Online #PPM #Office365

September 1, 2016 at 4:30 pm | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | Comments Off on Error creating Project Sites from custom site template in #ProjectOnline / #SharePoint Online #PPM #Office365
Tags: , , , , ,

A quick post, if you are finding that all of a sudden your project sites are failing to create with the error below:

CreateWssSiteContent: Creating project site failed! Project Uid= <site details> Microsoft.SharePoint.SPException: The site template requires that the Feature {e995e28b-9ba8-4668-9933-cf5c146d7a9f} be activated in the site collection. at Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag

Chances are you using a custom site template and this stopped working within the last week or so. The feature ID SharePoint is complaining about is a “MobileExcelWebAccess” feature. This can’t just be enabled.

The fix is straightforward, locate the site which you used to create the site template and save that site as a template again with a different name / version then link this to the Enterprise Project Type/s. Repeat this for all custom site templates.

#SSRS native report render issue in #SharePoint #SP2013 with #IE 10 or later #PS2013 #BI #SQL

January 15, 2014 at 6:03 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue, Reporting | 1 Comment
Tags: , , , , ,

This post covers an the details around an issue I came across the other day and I wanted to make you aware to help in your deployments / system design. The issue is with displaying SSRS Native mode reports on a SharePoint 2013 page using a page viewer web part when using IE 10 or later. Our preference and recommendation is to usually use SSRS Integrated mode but on occasions some of our clients use SSRS 2008 R2 / 2012 Native mode. This issue doesn’t exist for SSRS Integrated mode.

****** Update ************

This issue is resolved by updating the document mode for the ReportViewer.aspx pages, updating this from <meta http-equiv=”X-UA-Compatible” content=”IE=5″>   to  <meta http-equiv=”X-UA-Compatible” content=”IE=8″> or later did resolve this issue for us. The file can be found on the report server in the following location: C:\Program Files\Microsoft SQL Server\MSRSx.InstanceName\Reporting Services\ReportServer\Pages. Please note, this will impact all the reports on that report server so test on a test server before a production server.

**************************

The issue is that the SSRS reports are not displayed correctly on the page, they are truncated:

image

Other standards-compliant browsers are ok, Chrome is:

image

IE 8 and 9 also work fine.

The page viewer web part with SSRS Native reports worked fine in SharePoint 2010 in any browser.

I have tested with the SSRS Report viewer web part (the 2008 R2 version as the SQL 2012 version doesn’t deploy to SharePoint 2013) from the RSWebParts.cab file, this has the same issue.

One of our devs had a quick look at this and it stated it was because the web part uses a table that is 3 cells wide. 2 of the cells are related to the document map while the 3rd contains the report itself. The document map cells are hidden by default.

In older versions of IE, a hidden cell in a table counted towards with width of the table, this was against the standard. Now with more standards compliant browsers, hidden cells do not count towards the width of the table.

This means that the report cell is the only cell defined for the row, so the browser forces it into the left most cell space. The end result of this is the SSRS report is truncated to the right as that is the limit of the size of that column.

So the answer going forward if your client wants to embed SSRS reports in SharePoint 2013 pages and they use IE, recommend (and use) SSRS 2012 Integrated mode.

#ProjectServer 2013 Project Center view failed to load #PS2013 #SP2013

November 20, 2013 at 10:33 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Workarounds | 2 Comments
Tags: , , , ,

I have seen this issue a few times now in Project Server 2013 where users see the error “View Failure The view failed to load. Press OK to reload this view with the default settings. Press Cancel to select another view”

image

Clicking OK gives another error: “You don’t have permissions to view any projects”

image

This isn’t the case in this example.

There are two scenarios that I know of that cause this particular issue, these are described below:

Note: My farm is in the Project Server permission mode.

For an existing user:
•    Log in as User A, access the Project Center, access “View A” – all works great
•    Change the permissions so that User A no longer has access to “View A” or delete “View A”
•    Log in as User A, access the Project Center, User A will see the View failed to load error

For a new user – never accessed the farm before:
•    Prevent access to the default Project Center “Summary” view for the Team Members Group but allow access to other Project Center views
•    Create a new user (User B) that is only in the Team Members Group
•    Log in as User B (a new user on the farm), access the Project Center, User B will see the View failed to load error

The ULS logs gives the following error:

Error is: GeneralSecurityAccessDenied. Details: User does not have permission to this view. . Standard Information: PSI Entry Point:  Project User: i:0#.w|support\userb Correlation Id: 2f5e74c7-c751-e311-9419-00155d15d154 PWA Site URL: http://vm753/PWA SA Name: ProjectServer PSError: GeneralSecurityAccessDenied (20010), LogLevelManager Warning-ulsID:0x347A6230 has no entities explicitly specified.               ea70589c-4f64-e059-ef52-a016cf63c1ed

InitViewReportInfo ViewUid:63d3499e-df27-401c-af58-ebb9607beae8 is not found.        ea70589c-4f64-e059-ef52-a016cf63c1ed

The remote command PWAProjectGetProjectCenterProjectsForGridJsonRemoteCommand encountered an unexpected exception. ea70589c-4f64-e059-ef52-a016cf63c1ed

If you have removed the default Project Center Summary view, either removed access to it or deleted it (new user scenario), or removed any other Project Center views that users may have accessed last (existing user scenario), the known workaround at this point is as follows. Click the Projects Tab, select a view from the view menu then refresh the page. At this point the view will load and the Project Center will continue to load successfully.

Changing #SharePoint Central Admin Regional Settings stops the #PowerPivot Dashboard timer job #SP2013 #PS2013

November 1, 2013 at 11:22 am | Posted in Administration, Configuration, Customisation, Fixes, Functionality, Information, Issue, Reporting, Workarounds | 1 Comment
Tags: , , ,

Take care when updating the Central Admin regional settings as certain things stop working. The link to update the region settings doesn’t exist on the Site Settings menu probably for this reason but you can type the URL manually and access the page. Just add _layouts/15/regionalsetng.aspx to the URL.

Central Admin region settings were updated to English (United Kingdom), which is ID 2057.

An example of functionality that stops working is the PowerPivot Dashboard Processing Timer Job:

image

For the benefit of the search engines:

‘The Execute method of job definition Microsoft.AnalysisServices.SPAdding.UsageProcessingTimerJob(ID 5144359a-e86d-429f-8a5c-8c06cca109ee) threw an exception’

The following error is thrown in the URL logs:

image

For the benefit of the search engines:

Failed to load ‘http://sp13:15000/PowerPivot%20Management/567b4062-7a0b-4b24-a7f5-994bbed90cf1/2057/Server%20Health.xlsx&#8217; with error: ‘The workbook does not exist at the specified location’

This error lead us to the fix. Notice the 2057 in the URL. Navigating the the PowerPivot Management library, there was no 2057 folder, only a 1033 folder.

A 2057 folder doesn’t exist, on 1033 – for English (United States):

image

At this point you can either create a a new folder for the correct locale in this case 2057 for English (United Kingdom), then copy the 3 documents shown below from the 1033 folder to the 2057 folder:

image

The timer job will now run successfully and the dashboard will update. The other option is to set the regional settings for Central Admin back to English (United States) – probably the recommended fix!

The the Dashboard will update and show data:

image

Take care when deleting the #Project Ideas list in #ProjectServer #PS2013 #SP2013 #SharePoint #ProjectOnline #PPM

October 14, 2013 at 8:24 pm | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue | 1 Comment
Tags: , , ,

Just a quick blog post to ensure you take care when deleting the project ideas list and to let you know of potential issues with deleting projects that were created via the deleted project ideas list.

This post covers the issues you will see when trying to delete a project from Project Server that was created from a project ideas list after the list was deleted.

****Update – this issue should be resolved in SP1****

Example Project Ideas list:

image

Project created in Project Server from the Project Ideas list above:

image

Delete the Project Ideas list from the “List Settings”  > “Delete this list” option.

Now try to delete the project that was initiated from the Project Ideas list, in this example delete the PM Test Project from the Delete Enterprise Objects menu in server settings. Navigate to the Project Server queue and you will notice that Project Delete job fails:

image

The key error is:

Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.RemoveIdeaListLinkMessage‘ messageID=’8′ stage=” blocking=’Undefined’

You will see the the project still exists in the Project Center:

image

But trying to access the project details gives an error:

image

Checking the Delete Enterprise Objects page shows that the project is not visible when selecting “Delete draft and published projects”:

image

Change to “Delete only published projects” shows the project:

image

Attempting the delete again throws the same error.

My advice at this stage is to recover the deleted Project Ideas lists if possible. In this example I still had the Project Ideas list in the PWA site recycle bin. After restoring this deleted list, the subsequent delete job for the “PM Test Project” completed successfully.

With this in mind, I would recommend that you do not delete any PWA lists that have been used to create projects in Project Server.

#ProjectServer #PS2013 / #SharePoint #SP2013 site template issue

September 4, 2013 at 10:02 am | Posted in Administration, Configuration, Customisation, Functionality, Information, Issue, Workarounds | 2 Comments
Tags: , , , , , ,

When creating new site templates in SharePoint 2013, ensure you check the box to include content. If you don’t do this, any sites created from your new template will have the “Change the look” functionality missing, it will load a blank page as shown below:

image

To resolve this, include the content when saving the new site template. Ensure that there is no test data on the lists / libraries etc.

Include content enabled:

image

After creating a site from this new template, the “Change the look” functionality will work as expected:

image

#ProjectServer #PS2013 #Excel Pivot Table limitation

July 4, 2013 at 11:38 am | Posted in Administration, Customisation, Functionality, Information, Issue, Reporting, Workarounds | 1 Comment
Tags: , , , , ,

Just a quick post to highlight a limitation / issue with Excel Pivot Tables that I hadn’t seen before, details below.

This particular Pivot Table uses a Data Model that contains two OData feeds from Project Server 2013, one for Project details and one for Task details. The connections can been seen below:

image

The relationship has been set up as follows:

image

I have added Programme, Project Name, Task Name and Task Start to the Pivot Table. Programme and Project Name are from the Projects table and Task Name and Task Start are from the Tasks table. The Project Name is filtered to just one project:

image

Looking at the Pivot Table, it looks the CPS Test project has many tasks but in fact this project only has 4 tasks:

image

To resolve the issue you have to add a numerical field from the Tasks table to correct the aggregation:

image 

Hope that helps Smile

Next Page »

Blog at WordPress.com.
Entries and comments feeds.