Recapping Microsoft Ignite 2016 Conference, Atlanta, GA

I had the privilege to attend Microsoft Ignite 2016 at Atlanta on Sep 26th-30th this year. This is Microsoft’s signature technology conference which is in the 2nd year after combining all the Office and TechEd conferences last year. If you have read my previous year’s Ignite recap, I wasn’t happy with how it turned out in Chicago especially with logistics issues, and I wasn’t excited this year either being Atlanta as host. As it turned out, I really enjoyed the conference especially technical content and roadmap delivered at the conference, and I must say – Microsoft has earned my faith in Microsoft Ignite event and can’t wait for more for of it next year.



Day 1 of Microsoft Ignite was divided into multiple keynotes – starting with Scott Guthrie lead main conference keynote, followed by sub keynotes from each area (Office, Infrastructure, Security, Communication, etc.), culminating in grand Innovation keynote by Satya Nadella.

I personally didn’t enjoy the main conference keynote. I felt it was Azure heavy with lots of Windows 2016, Visual Studio, and Xamarin updates. My takeaway here was it was mostly boring, nothing new because most of the announcements were already made. There was hardly anything mentioned for Office innovations. My personal favorite from the morning keynote was a huge announcement of Microsoft joining hands with Adobe and Adobe hosting their all clouds including Marketing cloud in Azure. Apart from that, I was disappointed with this keynote.

What morning keynote couldn’t deliver, delivered by Innovation keynote by Satya in the late afternoon. I had an enormous fun listening to Satya and Microsoft’s vision of how Office, Azure, and Windows can deliver innovations in IoT, Analytics, and Cloud computes automation. This is must watch for anyone in technology field despite your interests in Microsoft technologies.

Technology Updates

I was excited with what and how Microsoft delivered Technology updates at Ignite. My interest this year was Office 365, Azure, SharePoint, Power BI, and related technologies. Day 1 and Day 2 was kind of boring with most of the roadmap updates which I had already learned in regular Microsoft Office updates. As I dived into more deep dive sessions on Day 3 and Day 4, I was impressed with all the new technology innovations Microsoft has made in Office 365.

One of the key things stood out for me was Level 100-200 sessions and how Microsoft delivered their roadmaps for 2016-17. They were honest in their delivery. There weren’t afraid of sharing what’s coming and what’s in design. Everyone was graceful in their delivery without any arrogance. It was refreshing to see this new Microsoft which has Satya’s stamp all over it. I personally think Microsoft Ignite still missed out many in-depth Level 300-400 sessions.

As far as technologies update, I loved many announcements including Office 365 Groups, Yammer Integration, OneDrive for Business Sync client, PowerApps, Flow, MyAnalytics, Microsoft Word TAP, SharePoint 2016 Feature Pack 1, and SharePoint Hybrid innovations, especially Hybrid Taxonomies. I can’t wait to deep dive into all of these technologies and master them.

If you are Microsoft especially Office 365/SharePoint professional, you would require learning Microsoft Graph, SharePoint Framework, React JS, TypeScript, Office UI Fabric, Windows 2016 Docker containers. Attending deep dive Level 200 sessions on Day 3 and Day 4 for these technologies was conference highlights for me as a technologist.

Conference Logistics

Anytime you need to host 25-30K IT professionals under one roof, it would become logistically tricky. Microsoft Ignite will face common challenges like lodging, transportation, food, session rooms layout regardless of wherever they plan (except Las Vegas) to host this event. Last year at Chicago, one of the biggest challenges they faced off the isolated location of conference center from the world. This year at Atlanta, they faced another challenge and mostly focused on transportation and lodging.

Before we start with what went wrong (we all love negatives), I must say there were lots of positives at this conference. Georgia Conference Center was a great location especially its proximity to Philips Arena and other downtown happening places. The location itself had lots of excellent facilities, and one of them was a patio where you can relax in sunny fall weather with lounge chairs, live music, games, and smoothies center. Ignite Mobile App was another clear winner for me especially scheduling and live streaming of sessions. This is one of the best conference apps at Microsoft events I have seen. I was able to get extra sleep (much needed for conference attendees) because I could live stream first session while commuting to the conference center. Another great idea this year was concurrent 20 minutes, 45 minutes, and 75 minutes’ breakout sessions. This gave attendees ample options of what sessions to attend and what to skip or view the live stream. Also – Microsoft showcase booths at expos were informative. Meeting with product groups was one of my favorite activities in between sessions.

Now, let’s focus on what can be improved. Lots of lines – There were lots of long walk in between buildings (especially if you have sessions in A and C) in addition to a lot of lines everywhere. I am not sure how Microsoft can improve logistically, but I turned away many times from to either attend session or event just because of lines especially it between sessions. After the event, activities was another big issue. If you have been in Atlanta, you know that it isn’t much as far as after event activities except bars, restaurants, and few baseball games in September. Lodging was another big issues. Unlike Chicago, Atlanta doesn’t have a large concentration of hotels in downtown area. Other two major locations were 30 minutes away at Buckhead and Airport. This is where Las Vegas would actually help where lodging, dining, and after event activities are no major concern.

Last but not least, Microsoft needs to stop serving boxed lunch. Even SharePoint Saturdays or conferences don’t have boxed lunch. It was one of the worst (worse than Chicago last year) conference food I ever had. I was done with cold sandwiches after the 2nd day. Luckily there were few other options nearby, but good conference meal should be one of the musts in Microsoft’s checklist. I do understand why Microsoft may have done it due to concurrent sessions but having both boxed and warm buffet meal would cater both audiences.


Parting Notes

Despite all these hate and love for Microsoft Ignite, I enjoyed this conference and can’t wait to attend future events. I personally would like to thank Slalom for letting me attend this conference and learn Microsoft’s direction for 2016-17.

Posted in Conferences | 1 Comment

Future of SharePoint Keynote Summary and My Key Takeaways

Ever since Microsoft RTMed SharePoint 2016 in March 2016, one event every SharePointers were looking forward to was – “Future of SharePoint” on May 4th, 2016.


Even though this event was marked as SharePoint 2016 GA availability, how Microsoft used it to instill the confidence in SharePoint community is a masterstroke in my book. Personally, I was looking forward to this event to see where I want to focus shortly as far as technology. As a SharePoint brand, there were few questions and Microsoft needed to answer. I won’t lie if I say I was approaching this event very cautiously but after the event – my faith in SharePoint on both Office 365 and On-premises have been restored.

In a nutshell, this was a vision and roadmap event specifically focused on SharePoint. As expected, the event was well marketed and well attended. There were some bold announcements and demos. Most of them are in the process of being rolled out in the SharePoint Online. This tweet at the end of the event summarizes what I felt of SharePoint shortly at that time.


Here are my key takeaways:

  • SharePoint is here to stay!! In fact, it’s been revitalized and modernized. The message has been reinforced – Innovations happens in a cloud, and few features will trickle down to the on-premises over the time.
  • “SharePoint” as a brand is brought back in Office 365!! No more, it’s branded as “Sites” app. It’s a small change like this regains confidence from the community.
  • Office 365 Groups are the NEW center of gravity in a cloud product. SharePoint team sites are re-branded with Office 365 Groups UI, but two-way integration will challenge traditional hierarchical information architecture. Documents will flow horizontally across products rather than hierarchical SharePoint team sites in Office 365. Additionally, tight integration of SharePoint Online, OneDrive for Business, Office 365 Groups, and other Office 365 products will reinvent what we think of a modern collaboration on office platforms.
  • Although Microsoft has delivered contextual and relevant SharePoint Online home page (similar to Delve UI) as Intranet in your pocket offering, my take here is that most of the organizations will create their own intranet home pages powered with Office Graph & Delve based UI. Ability to support customized version of Intranet home pages is critical. There will be requirements from customers to support customized version of the home page on “SharePoint” mobile app and browser experiences home page.
  • SharePoint On-premises are here to stay!! SharePoint Online & Office365 will innovate first, and particular features will be pushed down to the On-Premises as feature backs. I won’t be surprised if feature packs replace existing service pack model.
  • SharePoint Hybrid is must have best of both worlds. New SharePoint browser & mobile apps would require hybrid infrastructure to display data from both cloud and on-premises.
  • Office 365 Graph and new SharePoint client side framework are must in developers’ toolkit. Both of them are built on a modern JavaScript and REST-based programming standards. Developers will require learning 6th development/customization model in last 6 iterations of the product. Microsoft continues pushing developing on a platform rather than service based on solutions they must have seen in their customer experience programs. It’s time to learn web stack if you haven’t already – Node.Js, Yeoman, Gulp, TypeScript, Visual Studio Code, etc. It should be noted here is this is one more additional framework, it doesn’t replace Add-ins model released in SharePoint 2013 or Full trust model introduced in SharePoint 2007.
  • SharePoint and Office 365 professionals will have more challenges to architect solutions based on Office 365 only, SharePoint On-Premises only, or hybrid investments. Great SharePoint professional is key to success. The question of what’s supported/not supported, what’s licensed/not licensed, what’s enabled/disabled, architectural trade-offs will factor in how you architect information architecture and business processes. This is not new as of now, but tight integration with Office 365 Groups and SharePoint Online will create many challenges for customers who won’t use capabilities of whole Office 365 suite.

Here are my notes from the keynote:


  • SharePoint 2016 On-Premises and Office Online Server (2016 version of Office Web Apps) GA available from today
  • SharePoint 2016 isn’t the last release, but it’s a foundation for future – forged in cloud, first cloud run source code packaged for on-premises, probably enhanced by feature packs rather than service packs

Future of SharePoint

  • Microsoft’s current focus is on 3G’s – Groups, Graph, and Governance (Notice – no SharePoint, rather than focusing on products vertically, Microsoft’s focus is across products and security/compliance).
  • New SharePoint Principles – In Cloud, On your on-premises, and In your Pocket, in other words – cloud first, mobile first but still supported for on-premises.
  • SharePoint is Core of Office 365 productivity suite – No kidding!!!!
  • SharePoint On-Premises Updates – Feature Packs for SharePoint – Subset of features available on top of SP2016, starting from 2017.

Files Access & Sharing Innovations

futuresharepoint-file access and sharing roadmap

  • A simple and powerful file on any device – intuitive browser experience.
  • Selective sync for OD4B & SPO document libraries. Sync shared folders in a roadmap.
  • Move or Copy OD4B files and folders to SharePoint.
  • New activity view pan for files (replacement for versioning?).
  • File Share/Document Analytics in OD4B (Likes and Shares coming in future as well).
  • Mobile app for SharePoint Online (SharePoint On-Premises support in roadmap including SharePoint 2013).

Reinventing SharePoint Intranets and Team Sites

futuresharepoint-intranet roadmap

  • Modern Intranets
    • Next-Gen, Responsive, and Mobile & Touch Friendly Intranets
    • Innovate on all three fronts – communication, collaboration, and custom apps.
    • Intranet on your pocket
      • New SharePoint home page, powered by Office Graph, contextual information, looks much similar to Delve UI. Show frequently visited sites or suggested sites based on your profile activities. It can show sites from both cloud and on-premises (requires hybrid configuration).
      • The intelligent discovery of content based on your activities. It shows pages, libraries, lists, and people. Again, similar to Delve UI.
      • New team and organizational news feature – News feature out of the box, will roll out in H2.
    • Intranet Web Experience
      • Renamed “Sites” tab to “SharePoint” to match mobile app name.
      • Frequent sites, suggested sites, Tiles view.
      • Instant search – people, sites, files, etc.
      • Easy new site creation – simplified and faster, requires you to select collaboration or publishing sites, you can also create Office 365 group in this wizard, will require enforcement of governance.
  • Modern Team Sites
    • Groups Integration – Each Team Site creation will create Office 365 Group and same true on another way around as well. Groups are tightly integrated into Office 365 with SharePoint team sites. Will roll out in H2.
    • Power Apps and Microsoft Flow integrated with SharePoint Online out of the box. This would allow it use SharePoint document libraries and lists as a data source. Possible replacements for workflow & forms workloads. Both products are in preview now. Will roll out in H2 this year.
    • New Home Page experience – Tied to group,  group name & members shows up, left-hand navigation still exists, you can bring in group features on team sites (e.g. conversations, etc.), by default – news & activities are available as tiles view, you can highlight document or blog article in news section, activities are documents with tiles view. It’s rolling out now.
    • New Pages experience – Mobile and touch friendly pages authoring experience, you can add documents, links, medias, etc. You have a gallery of OOB web parts (similar as Adobe AEM). It’s rolling out now.
    • New Document Library experience – looks & feels like OD4B, consistent experience. Quick contextual metadata editing experience, grid/thumbnail view experience, ability to pin feature, everything on your fingertip either via quick action bar or information panel, no more ribbon. It’s rolling out now.
    • New SharePoint Lists experience – Integration of OOB Microsoft flow UX and Power Apps and context are passed to these apps.  It’s rolling out now.
    • Team site activities and analytics – Modern graphical analytics.  It’s rolling out now.

Platform Extensibility

futuresharepoint-openconnected roadmap


  • Data Layer – Office Graph API – REST based, single end-point – we will have SP REST API available via Office 365 API shortly.
  • UI Layer – New SharePoint Framework – New JavaScript-based client side development layer, it’s backward compatible, it will be open source, client-side web parts & client side page/canvas applications framework – this framework will be released in Q3 for SPO as First Release and for on-premises as features packs hopefully in 2017.
  • SharePoint Bench – A SharePoint particular mock debugging environment to test development without needing of SharePoint in local VM.
  • Microsoft will deliver few responsive experiences based new SharePoint Framework. New SharePoint online document library experiences, Delve UI, & lightweight publishing model (Delve blog) are some of them.

Community and Microsoft Resources

New SharePoint Framework Reactions

Happy SharePointing!!!

Posted in Uncategorized | 2 Comments

Modernizing SharePoint? – My thoughts on SharePoint Online Document Library Experience Updates

Update on May 5th – Drawbacks mentioned in this article are no longer drawbacks if you are using new SharePoint Online experiences. New SharePoint Online experiences announced as “Future of SharePoint” event on May 4th spans not only document libraries but throughout SharePoint including new SharePoint Team Site experiences. See Updates herehere, and here. I never had a blog article invalidates itself in few weeks. It’s a power of modern product updates & release cycle. I still think communication and feature rollout could have been better.

Microsoft has pushed out one more “Sneaky” release in Office 365 relating to SharePoint Online document library experiences. If you have “First Release” tenant, you will start noticing the new banner on SharePoint online document library page stating – “Check out new document library look!”.

Doc library UX Banner

I call this “Sneaky” release. Even though this is a huge change in SharePoint (first significant Document Library UI change since SharePoint 2003/2007 days, almost 10-12 years ago), it was never announced on Microsoft Office blogs. I have heard this news on Twitter after seeing few posts from MVPs and other community leaders regarding this release.

Unlike MVPs or other community leaders, my thoughts on this change are bitter-sweet. On the one hand, I love this new modern experience with lots of core features stands out in UI for end-users. On the other hand, I hate the navigation experience from SharePoint Online document library UI to One Drive for Business document library UI. More on navigation concerns later.

If you have never seen new SPO document library experience, here is the preview:

This is a classic SharePoint Online document library experience with the invitation to try out new experience:

SPO OLD Doc Library UX

This is how new SharePoint Online document library experience looks like (with an ability to rollback to classic view for the time being):

SPO New Doc Library List View UX

SPO New Doc Library Grid View UX

Let’s first talk about Pros. I hugely welcome modern UI of new SharePoint Online user experiences. Not only Microsoft had bubbled up many key features like easy actions but modernized the UI along with it.

Here are some of the highlights of new features and I must say – I love them all.

  • Library Level Features
    1. Ability to Pin documents as Highlights above the library view
    2. Ability to “Alert Me” from quick action bar
    3. Ability to have Grid view with previews, rather than traditional list view
  • Document Level Actions
    1. Ability to see “History” on the right bar
    2. Document Action Bar – Ability to get a link, ability to Move to another location (one of the long standing issues with traditional UI)

Now, let’s talk about major drawback. With all the love for new UI, one of the major downside of this new update is what happens to the existing collaboration sites. Even though Office 365 have new workloads rolling out every few months to tackle modern collaboration like Yammer Groups, Office 365 Groups, Planner, Delve, many of our customers are still using SharePoint team sites for document collaboration.

Along with SharePoint team sites, they are accustomed to using “Blue” SharePoint/Office 365 global OOB UI and SharePoint Online ribbon bar. One of the major issues with new UI is end-users will require traversing back and forth between SharePoint Online UI (Blue Globar bar with Ribbon) and OneDrive for Business UI (Black Global bar without Ribbon) while using document libraries and that’s where the challenge is.

Many of us additionally apply SharePoint online themes (recommended by Office 365 PnP as supported version of branding), which would affect seamless UI experience and navigation as users are accessing team sites, document libraries, and documents. My only hope here is Microsoft have further plans to roll out SPO changes to reflect this new UI in SPO to match overall Office 365 experience.

But, Wait – There is a solution to all these – Having all said that, Microsoft didn’t leave us with this as forced update. You have the option to use old or new experience depending on your organization’s appetite for change. Each document library has the option to use new or old experience. This would allow document library owners to use whatever experience they like. Additionally, there is a global SharePoint Online administrative setting to apply this change to all document libraries in SharePoint online team sites. Few tips here – library-level settings will definitely affect the governance policies and how organizations want to standardize the document library experiences. Few more things to worry about as you trying to govern your environment. 🙂

You can manage list document library experiences settings from library’s advanced settings page. There are three options here:

SPO Library Admin Settings

  • Default experience set by my administrator – Configured at the SharePoint Online Administrative page.
  • New experience – New experience with OD4B UI
  • Classic experience – Classic Old and Gold SharePoint document library view

Here is the screenshot of SharePoint Online Admin Setting.

SPO Admin Settings

Here are my initial reactions on Twitter. I am hoping to have more positive reactions and better document library experience stories as we go through initial period.

Nik's reaction 0.PNG

Nik's reaction 1.PNG

Nik's reaction 2.PNG

SharePoint Online is changing!!! Good luck SPO!!!

Additional Resources and Community Reactions

Posted in Uncategorized | Leave a comment

Nik’s SharePoint Saturday Chicago Suburbs 2016 Session Deck on Modern Intranet Development on SharePoint and Office365 is Available

Thanks to everyone who was able to attend my session at the SharePoint Saturday Chicago Suburbs 2016. It was a great to see familiar faces and old friends in a reasonably attended session.

I had a fantastic fun walking attendees lessons I have learned while developing Intranets on SharePoint and Office 365 last few years. It’s great to share some of the best practices I have compiled and how I would design intranet on these platforms in future.

Title: Best Practices for Intranet Development on SharePoint and Office 365 Platforms
Session Abstract – Development of successful Intranets on ever changing SharePoint and Office 365 platform requires an understanding of available options and how to apply them. Nik Patel from Slalom Consulting has designed and built four different intranets in four years with various best practices each with unique flavors and customization options available at that time. Nik will take attendees through architecture options in past and future and provide practical guidance for future Intranet development on SharePoint and Office 365 platform. This session is for both beginners and advanced level developers and architects.

As promised, here is my session deck available through Slide Share. Feel free to download and reach out to me if you have any questions.

I have recently posted few SharePoint development best practices articles. These can be used as additional sources along with Office 365 PnP to make the decision in tricky architectural trade-offs.


Posted in Speaking | Leave a comment

Cheat Sheet to Troubleshoot SharePoint Provider hosted High-Trust Add-ins – 401, 403, 404, and Misc Errors

Anyone who has worked on provider hosted high-trust add-ins for SharePoint 2013 on-premises environment knows if an environment works, it works like a charm. If it fails, it’s worst thing as IT Pro you may encounter. Most of the errors while troubleshooting provider hosted high-trust configuration are mostly related to authentication and add-ins & SharePoint communication. Many of these errors are so generic like 401, 403, and 404 errors that it can quickly raise the frustration level along with the waste of hundreds of hours.

With this cheat sheet, I am planning to share my usual suspects and hoping to keep it updated as I encounter more weird errors in SharePoint provider-hosted high-trust add-ins configuration.

Microsoft Resources for Troubleshooting Apps

Usual Suspect Areas to look at

  • Expired certs on IIS, local Windows cert store, and SharePoint trust store (including all the chain certs)
  • Invalid Get-SPTrustedSecurityTokenIssuer
  • Invalid Get-SPTrustedRootAuthority
  • Invalid Cert Serial Number or Certs information in web.config
  • Invalid Alternate Access Mapping
  • Invalid HTTP or HTTPS binding in IIS
  • Missing DNS entries
  • Depending on your needs, you would need to set App permission in App Manifest
  • Validate Provider Hosted App IIS site – Enable Windows Auth, NTLM as preferred provider, App pool runs under 4.0 and ApplicationPoolIdentity

Myths – Invalid Causes called out in blogosphere

  • Certs Chain must be installed and imported in both local Cert store and IIS on both SharePoint and Provider Hosted Apps servers.
    • Removing RootCA & High Trust cert from SharePoint trust store (accessible from central admin) not affecting how Provider-hosted apps work, it works regardless.
    • According to API cert expert, Brian… IIS should have only lowest level cert what’s needed for binding, all parent chain certs shouldn’t be in IIS.
  • No Routing Web App on SharePoint Servers – This throws 404 error for SharePoint hosted, and Store hosted apps but works fine for Provider-hosted apps, routing web app is required for SharePoint hosted app.
  • You need to disable Anonymous Authentication on Provider hosted app IIS website – no reason to do this unless you want to do this as best practice.
  • NTLM has to be preferred provider (above Kerberos) for Windows Auth on Provider hosted app IIS website – no reason to do this unless you want to do this as best practice.
  • To get the title of the site, you would need to set App permission in App Manifest Depending – No need for this for title info.
  • SharePoint and App hosting servers should be in same time zone. No need for this either.

Error – An Unexpected error has occurred while installing app

  • This may happen if App was already installed with upper version and you are redeploying app using lower version to the same site. e.g. I had a site collection where I deployed an app with version. I have uninstalled an app and repackaged with version and deployed to the App Catalog. This caused an error while installing an app to the same site collection again. New version app would work fine with new site collection where this app never been installed earlier.
  • Myth – Many blogs and forum say – cleanup App Catalog recycle bin and that didn’t fix my issue.

Error – Blank Page while accessing installed app

Error – 401 Error – Unauthorized while accessing installed app


  • Possible Causes:
    • No Windows Auth is enabled on the Provider Hosted App IIS website.

Error – 401 Error – Unauthorized while running app, SharePoint-App communication issue

401-Unauthorized 2.PNG

  • Possible Causes:
    • Issuer ID is invalid or has uppercase letters or Issuer ID has space in Appweb web.config file.

Error – 403 Error – Forbidden while accessing installed app, SharePoint-App communication issue


  • Possible Causes:
    • Client ID is invalid, or Client ID has space in Appweb web.config file.
    • Get-SPSecurityTokenServiceConfig AllowOAuthOverHttp setting is invalid. It must be true if one of the SharePoint web application or Provider hosted App IIS website have HTTP binding. If both SharePoint and Add-ins using SSL, it should be false. In many cases, if you have HTTP binding on SharePoint in addition to SSL and if Add-ins using SSL with AllowOAuthOverHttp=false, may cause an error.

Error – 404 Error – While accessing installed app


404 2

  • Possible Causes:
    • DNS Entry Issue – Either Wrong or NO DNS entries – Try to ping the app URL to see if it reaches to correct server IP or F5 App Pool IP.

Error – An error occurred while processing your request – while accessing installed app

  • Background Note – This error gets generated by Visual Studio boilerplate code for SharePoint Context and TokenHelper.
  • Possible Causes:
    • Certificate Serial Number is invalid in Appweb web.config file.

Error – Keyset does not exist – while accessing installed app

Background Note – This error is related to SharePoint app running in IIS can’t access High Trust configured on Provider hosted cert store to initiate communication to SharePoint.

Possible Cause – If IIS_IUSERs don’t have permission to high trust on local cert store, it will throw Keyset doesn’t exist error – For the separate IIS server hosting Add-ins, configure BUILTIN\IIS_IUSRS users to the full control permission to cert. This allows apps running on IIS to access cert for high-trust SharePoint communication. On Windows Server 2012 R2, Use command line tool – Windows HTTP Services Certificate Configuration Tool – WinHttpCertCfg.exe. On Windows Server 2008 R2, you can use Microsoft WSE 2.0 SP3 GUI tool, look up wildcard cert (e.g. *.niks.local) and gave full control IIS_IUSRS from the machine, restart the IIS.

Error – Sorry, Something went wrong – while adding/installing an app to the site – App differs from another App with the same version and product ID

Sorry something wrong

This is worst kind of error where it’s really hard to troubleshoot. In most cases – you have to look into ULS logs to troubleshoot as this isn’t a glaring mistake. Luckily, that mistake does provide you ULS correlation ID which you can use to troubleshoot.

In my case – I had come across this error in ULS log.

Issue – 11/03/2015 14:44:28.00   w3wp.exe (0x1C28)                       0x0548  SharePoint Foundation                 General                                       ajlz0       High       Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.InvalidOperationException: The provided App differs from another App with the same version and product ID.     at Microsoft.SharePoint.Lifecycle.SprocWrappers.CreateApp(SqlSession dbSessionWrapper, Byte[] fingerprint, Guid siteId, Guid productId, Version version, String title, String contentMarket, String assetId, SPAppSource source, String tempIconUrl)     at Microsoft.SharePoint.Administration.SPApp.CreateAppAndCommitPackage(SqlSession session, Byte[] fingerprint, String path, Guid siteId, String assetId, String contentMarket, SPAppSource source)     at Microsoft.SharePoint.Administration.SPApp.CreateAppUsingPackageMetadata(Stre… 4d143e9d-3578-6086-1f97-858d6df686c1

There are various online articles and places this error has been discussed and folks have solved many different ways –

Have you come across any other scenarios not discussed here? Plan to post in the comments section to increase awareness of your particular situation. You never know – it may help someone out there.


Posted in Uncategorized | 2 Comments