For the past year I’ve been working on an enterprise search solution for a Canadian federal government client employing SharePoint Server 2013 / 2016 and integrating with line-of-business data via Business Data Connectivity Services (BCS, formerly BDC) with a BDC .NET Connector. The elements of this solution, notably SharePoint Search and Business Data Connectivity Services, encompass a complex set of technologies which would easily occupy a blogger for months if not years. On this occasion we’ll delve into one small but important part, creating BDC Profile Pages in a host header / host named site collection context.
Some time ago one of my colleagues reported an issue in our development and testing environments; when we attempt to generate a profile page for an external content type in the BDC service application:
We get this warning:
With the text:
This content cannot be displayed in a frame
To help protect the security of information you enter into this website, the publisher of this content does not allow it to be displayed in a frame.
What you can try:
Open this content in a new window
Traditionally as a SharePoint developer or designer your skills and toolkit were quite different from those of a standard web developer. While that used to be essential to your success, in today’s web-centric world as you transition your skills it might mean you overlook the obvious when troubleshooting. Recently I was helping a developer colleague resolve one of those eponymous “Sorry, something went wrong” messages that SharePoint 2013/2016 is so famous for, when it drove home this point: Always start with the web-dev basics!
As a SharePoint Technology Architect you have to know a little bit of everything in the platform stack from Windows Server to Active Directory to DNS to networking, and much more, a veritable jack-of-all-platform-trades. On a recent project I was working with an IT Pro to prepare a new server virtual machine for a proof-of-technology for SharePoint 2016 when I was reminded of this.
This project teanm is hard up for infrastructure so we are scrounging for virtual machines and have to make do with a refurbished hand-me-down VM. The server team re-imaged the VM with Windows Server 2012 R2 as is required for SharePoint 2016. The initial sanity check of the refurbished VM is good, we can RDP to it and Server Manager Dashboard shows a healthy server, all services running normally.
Next step is we have to request a DNS entry for the Central Admin site for SharePoint 2016, hence we need the IP address(es) of the new VM. As a quick step I ping the VM rather than RDP’ing to inspect its network adaptor configuration:
Whoa, ping does not respond! How can that be? I just RDP’ed to the server and it was fine.
I’ll be speaking at the SharePoint Summit Toronto 2014 on Tuesday, May 27, 9:50am on the topic How to be Social with My Sites in SharePoint 2013.
In this session learn about the social features in SharePoint 2013, why you will absolutely love them, and how they will make you more productive. My Sites and user profiles have huge improvements, follow sites, people and documents, micro-blogging with mentions and hash tags, ratings and likes, People search, and other professional social network capabilities.
If you are going to be at the conference be sure to look out for me and say hi.