Hello again SharePointers!
I wanted to get the word out on another bug that seems to have reappeared in Performance Point in SharePoint Server 2013. Originally this issue popped up as a problem with the grid view being cut off towards the top. Example below:
This issue was corrected in the June 2013 CU for SharePoint Server here
But after testing both before SP1 (August 2013 CU) and after SP1 in my farms, I see the following issue pop up when multiple pages exist in the web part. This is referred to pagination I believe and causes a behavior that we see in our farm like the screenshot below:
For us it’s more of an issue about our users not being able to view the proper info they need. I have filed a case with Microsoft support and will keep everyone up to date on how it progresses.
Fortunately as I was typing out this post I got a message from someone that this is an official bug and will be submitted to the product group to be fixed.
So I am glad that it is not just my farms that see this issue… 🙂 But I also hope that this provides some help for those of you seeing this issue as well. As soon as I get word on which CU this new fix will be in, I will let everyone know.
Thanks for visiting!
In my previous two posts I focused on a problem created by the install of the October 2013 CU for SharePoint 2013 Server. It basically disabled the ability of your users to launch dashboard designer (DD) after installing the cumulative update.
In December 2013 another CU was released, but didn’t do anything to address the problem of not being able to launch DD. If anyone of you have a SharePoint 2013 farm and use BI, this is kind of important. It’s kind of like owning a cheese factory and someone comes along and disables all of your cows from giving milk.
Good news though! After checking the MSDN forums I came across the following article:
Originally this article listed 3 files that needed to be replaced in all of your SharePoint farms to correct the CU issue, but initially I tried this and it did not resolve the problem. But after a few days two more files were added to be replaced as well.
The great news is that I confirmed that this does fix the original issue brought on by KB2825647 and now we can launch DD with the October 2013 and December 2013 CU applied to my SharePoint 2013 farm! Oh happy day!!
Maybe this will get integrated into the February 2014 CU, but secretly I hope we get to see SP1 for SharePoint 2013 before that.
We’ll just have to wait and see. Happy SharePointing everyone!
Hello again from SharePoint land!
It’s been a while since we talked about KB2775353 and how it made our SharePoint 2010 servers where I work extremely sad and kept them from correctly displaying our BI dashboards in 2010 (see here).
I was originally told when I found this bug that the fix would be put into a patch around the August 2013 CU timeframe, and sure enough with the newest round of patches released I went and got my grubby little hands on it. It took a few days for us to properly test it here, but I can confirm from our internal testing here that this patch corrects our display issue with our dashboards! Yay!!!!
Just to be clear, this is my personal scenario of how things went, YMMV.
We originally patched our farm to the April 2013 CU for SharePoint Server 2010 due to an incorrectly applied patch that came in from windows update, so we were originally forced to move to the April 2013 CU. For the meantime we have been working around this issue by displaying our dashboard items in a different way. We notified MS support of our issue and verified it was indeed a bug and they went to work on correcting it.
So when the August 2013 CU for SP2010 came out a few days ago, I had a couple of options on how to bring my farm up to the latest patch level. What I ended up doing was patching my farm with SP2 and then after checking to make sure everything applied correctly from this patch, applied the August 2013 CU for 2010.
After this, we had to redeploy our dashboards back to how they were before the April 2013 CU mess and verified that everything looks good and is back to normal.
Now I can put all of this mess behind me and work towards upgrading everything to SharePoint 2013. I hope this helps anyone else who runs across this scenario with their BI setup in SharePoint 2010.
Thanks for all the twitter questions and replies to my previous post everyone! I think with 2013, I will be more conservative in my patching going forward…
I thought I would take this opportunity to let everyone know about a bug that was discovered by our BI team this week with the April 2013 CU for SharePoint 2010.
The bug is mainly affecting PerformancePoint Services in SharePoint 2010 Server.
Background: Our users have a set of KPI’s that are published on a couple of dashboards that contain operational data. Normally when the dashboards load, these graphs, charts, and reports are hidden to improve initial loading performance. When the user clicks on the proper cell for each KPI, the dashboard will create 1-3 graphs, charts, reports or a mash up of the 3 to display further details.
Issue: We noticed earlier this week in our environment that when we would click on a cell for a KPI, none of the charts, graphs, or reports for that KPI would display properly. It was just like they weren’t being displayed when the user clicked on a cell. Our users have many important reports they get to by this process, so this affects us in a big way.
One odd thing to note that we found in our troubleshooting of this issue is that if you edit the page in SharePoint that each dashboard is on, the graphs and charts and reports show up just fine. When you stop editing the page in SharePoint, the dashboards go back to not showing them. Weird, huh!!??
Workaround: For now the only workaround we have for this issue is to display all of our charts and graphs and reports on the dashboards at the same time. This does slow down our performance a bit, but this is better than the users just not being able to see the information they need at all.
As we learn more about this, I will update this post.