Share-n-dipity

SharePoint serendipity is the effect by which one accidentally discovers something fortunate, especially while looking for something else entirely. In this case, it is the occassional musings, observations, and Ouija board readings about the phabulously

Another BCS Hybrid Tip - Fixing "The Type name for the Secure Store provider is not valid" Error

Another BCS Hybrid Tip - Fixing "The Type name for the Secure Store provider is not valid" Error

  • Comments 3
  • Likes

Here's another error that are actually pretty likely to see if you are setting up BCS hybrid.  When you configure your BCS connection in o365 to connect to your on premises data source, one of the things you need to configure is the security that's going to be used to make the call into your data source.  In many cases you will want to use a Secure Store Service application and keep a set of credentials in there.  You can configure your connection to do that just fine, but when you try and import your data model in o365 you will get an error message that says "The type name for the secure store provider is not valid".  If you look into this error further in your on prem ULS logs you will see something to the effect that it's asking for version 16.0.0.0 of the secure store assembly.  That's the version that's running in o365 today, but on premises today you have version 15.0.0.0.

After looking at some different options, we ultimately decided that for now the best way to work around this problem is to add an assembly binding redirect to the web application in the on premises farm.  When I say "the web application", what I mean is the web application your BCS connection in o365 points at in the connection.  In the connection itself, you will need to have an endpoint for the client.svc, and to do that you use a web application that you have published through your reverse proxy.  So if your web application is at https://www.foo.com, then in BCS you would configure the endpoint as https://www.foo.com/_vti_bin/client.svc

So...in the web.config for that web application you would add an assembly redirect that looks like this:

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
 <assemblyIdentity name="Microsoft.Office.SecureStoreService" publicKeyToken="71e9bce111e9429c" culture="neutral" />
 <bindingRedirect oldVersion="16.0.0.0" newVersion="15.0.0.0" />
</dependentAssembly>

I'll have more details on this and all the rest at the post-SPC training that Bill Baer and I are doing.

Comments
  • Im having this very issue, the OnPremises web.config for the outward facing (reverse proxy exposed) web app already had the downgraded config as you have above. I double checked my SSOProviderImplementation property in the ECT and it is correct also. but the problem still persists. any other insights you can provide? thanks. ill be at SPC14 as well perhaps we can meet up

  • Nevermind.. I got it working. there were several places in the web.config where SecureStore was mentioned also I started over from scratch & now works make sure to check out #SPC319 session at #SPC14 :-) cheers

  • Same happens for anything Project Online related...use 16.0.0.0 instead of 15.0.0.0.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment