none
The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU - SharePoint Foundation 2013

    Question

  • After sucessfulling installing the SharePoint Foundation 2013, when i try to access the Secure Stored Service Application i get the below error

    Secure Store Service Error in SharePoint Foundation 2013

    11/16/2012 18:13:02.84  w3wp.exe (0x1774)                        0x15E8 Secure Store Service           Secure Store                   g0n6 High     The trial period for this product has expired or this feature is not supported in this SKU. b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84  w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        8nca Medium   Application error when access /_admin/sssvc/ManageSSSvcApplication.aspx, Error=The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU.   at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.Execute[T](String operationName, Boolean validateCanary, ExecuteDelegate`1 operation)     at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.IsMasterSecretKeyPopulated()     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.SSSAdminHelper.EnsurePrerequisite(SecureStoreServiceApplicationProxy proxy, String& errorMessage)     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.ManageSSSvcApplication.InitializeGridView()     at Microsoft.Office.SharePoi... b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84* w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        8nca Medium   ...nt.ClientExtensions.SecureStoreAdministration.ManageSSSvcApplication.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84  w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          Runtime                        tkau Unexpected Microsoft.Office.Server.ProductExpiredException: The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU.    at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.Execute[T](String operationName, Boolean validateCanary, ExecuteDelegate`1 operation)     at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.IsMasterSecretKeyPopulated()     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.SSSAdminHelper.EnsurePrerequisite(SecureStoreServiceApplicationProxy proxy, String& errorMessage)     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.ManageSSSvcApplication.InitializeGridView()     at Microsoft.Office.SharePoint.ClientExtensions.SecureSto... b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84* w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          Runtime                        tkau Unexpected ...reAdministration.ManageSSSvcApplication.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84  w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        ajlz0 High     Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.Office.Server.ProductExpiredException: The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU.     at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.Execute[T](String operationName, Boolean validateCanary, ExecuteDelegate`1 operation)     at Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplicationProxy.IsMasterSecretKeyPopulated()     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.SSSAdminHelper.EnsurePrerequisite(SecureStoreServiceApplicationProxy proxy, String& errorMessage)     at Microsoft.Office.Sha... b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84* w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        ajlz0 High     ...rePoint.ClientExtensions.SecureStoreAdministration.ManageSSSvcApplication.InitializeGridView()     at Microsoft.Office.SharePoint.ClientExtensions.SecureStoreAdministration.ManageSSSvcApplication.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.HandleError(Exception e)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.Htt... b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.84* w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        ajlz0 High     ...pApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) b3b6e19b-7de2-e016-ad32-0fc975829ef0
    11/16/2012 18:13:02.86  w3wp.exe (0x1774)                        0x15E8 SharePoint Foundation          General                        aat87 Monitorable   b3b6e19b-7de2-e016-ad32-0fc975829ef0

    Is it a bug or any issue in configuration?


    Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    Friday, November 16, 2012 12:50 PM

All replies

  • Hi Raghavendra.

    Not sure if this applies here, but this was a rather common issue in 2010. Then, it could many times be resolved by running the PSConfig utility(Config Wizard) with the secureresources flag.
    Run a command prompt as admin, then browse to the psconfig file, located in the 15 hive under \BIN
    (c:\program files\common files\microsoft shared\web server extesions\15)

    psconfig.exe -cmd secureresources
    

    The other less attractive option is to add the Application pool account to the local administrators group, but since that would be a bad idea from a security standpoint, I do not recommend it.

    Hope that helps

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Saturday, November 17, 2012 4:52 PM
  • Hi Thomas,

     Will try the psconfig cmd and will update if this still holds true.

    Since its Integration environment for developers the app pool account is already a part of administrators group and still the error exist.

    I wonder if it was a common issue in 2010 why its still not fixed? Any specific reason?


    Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    Monday, November 19, 2012 4:40 AM
  • Hi Thomas,

    The issue still exist even after running the psconfig command. Any other options?

    Note: The configuration wizard ran successfully after the completion of SharePoint Setup


    Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    Monday, November 19, 2012 4:49 AM
  • I meet the same Issue in SharePoint Foundation 2013!!!

    Anyone can give me a resolution?

    I also wonder if it was a common issue in 2010 why its still not fixed? Any specific reason?



    • Edited by jianyi Thursday, November 22, 2012 12:22 PM
    Thursday, November 22, 2012 12:22 PM
  • Hi.

    I git a tip from a friend who has experienced this issue with 2010...it happened when he used one account(setup account) to install and configure the farm initially, then he added a service(OWA) and when running the config Wizrd or PSConfig, he got the Trial expired error. He logged on again with the account used to install and it worked like a charm.

    The reason for this can be, that the setup account is given some special permissions and memberships during setup that is not cpoied by simply adding Another account to the farm administrators Group for instance.

    Try this and get back to us on the progress.

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here


    Sunday, November 25, 2012 4:13 PM
  • I ran everything from start to finish as the domain administrator on my local VMs (i.e. logged on as the administrator, did the install and tried to create the Secure Store Service App by both the UI and the AutoSPIntaller approach (which needed to be modified to bypass the server version check). I get the error also.
    Friday, December 7, 2012 12:09 PM
  • has anybody some solutions. have the same issue.

    teddy

    Thursday, December 13, 2012 2:22 PM
  • Hi Ramle.

    If none of the above worked, then try this:

    If this is using a farm admin account on the SP server, then you get a lot of defferent behaviour and missing features etc. in CA.
    Start IE 'as administrator' and then try it.

    Any difference?

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Thursday, December 13, 2012 2:28 PM
  • Hi Thomas

    no, it did not help. I tried any combination nothing helps. I have installed different SPF2013, standalone and two tier. always the same. Any Ideas?

    Regards


    teddy

    Thursday, December 13, 2012 2:42 PM
  • Same problem to me:

    SharePoint Foundation 2013 Standalone.

    None of the above listed suggestions was solving the problem.
    Thursday, December 20, 2012 11:20 AM
  • None of the solution is working. We are facing this issue from past 10 days and raised with MS but did not resolve the issue. Not sure what the problem is! The website was working like a charm for a year and suddenly one fine day it stopped working and saying "trial period of the product is expired".
    Friday, December 21, 2012 5:50 AM
  • I am having the same problem and have tried all the above as well.  Has anyone come up with a solution to this problem yet?  I get it on others besides just the SecureStore as well.  Any assistance would be appreciated.  Thanks!
    Thursday, January 3, 2013 8:19 PM
  • Has MS some new infos, bugfix?
    Also waiting for more Infos!


    teddy

    Thursday, January 3, 2013 9:43 PM
  • Hi, the same issue :(

    Russian version of this exception is "Истек пробный период для этого продукта, или общая служба Secure Store не поддерживается для этого номера SKU."

    Maybe Secure Store Service requires some other components? What to check?

    Tuesday, January 15, 2013 1:26 PM
  • Hello.

    I have now had this confirmed with MS Support.

    This is a known issue with Microsoft Foundation 2013.

    MS will be producing a Hotfix that will remove this feature - its only available in enterprise version

    In Effect the error message is correct.

    Thursday, January 31, 2013 1:52 PM
  • Seems like many people have that problem and good to hear, that MS will release a hotfix.
    In Fact, this is a feature of the SharePoint Server 2013 STANDARD Edition - not the Enteprise Edition.

    SharePoint Foundation contains the Business Connectivity Services. Secure Store was very helpful to us, when connecting to databases using BCS - so I wonder that it should removed ....
    Thursday, January 31, 2013 2:39 PM
  • Please let know here when this is fixed.

    By the way this could take me to the problem of not be able to deply sahrepoint hosted Apps?

    Thanks

    Sunday, February 3, 2013 6:51 PM
  • Hi JLSF

    The feature is not going to get added to Foundation, the "fix" is going to be removing the link from Foundation so we don't get the error message.

    It apparently is availible in Standard upwards

    Monday, February 4, 2013 7:43 AM
  • Thanks By the way this couldn't be a reason to not be able to deploy autohosted apps?
    Monday, February 4, 2013 8:01 AM
  • Are you building on-premise or Office365?  Follow this link if your building Apps Service.

    http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/eaf67b5b-76c2-44a4-8ebd-b5b896477e47/#45a9ffbc-153f-457e-a594-ebff2732a0e7


    Vien H. Lim

    Tuesday, February 5, 2013 6:28 PM
  • Could we get the hotfix from Microsoft so we can download it?

    Thanks,

    -V


    Vien H. Lim

    Tuesday, February 5, 2013 6:29 PM
  • Hello

    something should be related wuith this service, take a llok at my visual studio output whne I try to deplay and autohosted sharepoint app: (anyone can help)

    1>------ Build started: Project: MySharePointAppWeb, Configuration: Debug Any CPU ------

    1>  MySharePointAppWeb -> C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\bin\MySharePointAppWeb.dll

    2>------ Build started: Project: MySharePointApp, Configuration: Debug Any CPU ------

    2>C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\Web.Debug.config(34,4): warning : No element in the source document matches '/configuration/connectionStrings'

    2>  Transformed Web.config using C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\Web.Debug.config into obj\Debug\TransformWebConfig\transformed\Web.config.

    2>  Auto ConnectionString Transformed obj\Debug\TransformWebConfig\transformed\Web.config into obj\Debug\CSAutoParameterize\transformed\Web.config.

    2>  Copying all files to temporary location below for package/publish:

    2>  obj\Debug\Package\PackageTmp.

    2>  Packaging into C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointApp\obj\WebDeploy\MySharePointApp.Web.zip.

    2>  Adding sitemanifest (sitemanifest).

    2>  Adding IIS Application (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp)

    2>  Creating application (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp)

    2>  Adding virtual path (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp)

    2>  Adding directory (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp).

    2>  Adding directory (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin).

    2>  Adding directory (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\en).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\en\Microsoft.IdentityModel.resources.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\Microsoft.IdentityModel.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\Microsoft.IdentityModel.Extensions.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\Microsoft.SharePoint.Client.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\Microsoft.SharePoint.Client.Runtime.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\MySharePointAppWeb.dll).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\bin\MySharePointAppWeb.pdb).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\packages.config).

    2>  Adding directory (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Pages).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Pages\Default.aspx).

    2>  Adding directory (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Scripts).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Scripts\jquery-1.7.1.js).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Scripts\jquery-1.7.1.min.js).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Scripts\_references.js).

    2>  Adding file (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp\Web.config).

    2>  Adding ACL's for path (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp)

    2>  Adding ACL's for path (C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointAppWeb\obj\Debug\Package\PackageTmp)

    2>  Adding declared parameter 'IIS Web Application Name'.

    2>  Package "MySharePointApp.Web.zip" is successfully created as single file at the following location:

    2>  file:///C:/_works/visual%20studio%202012/Projects/MySharePointApp/MySharePointApp/obj/WebDeploy

    2>  To get the instructions on how to deploy the web package please visit the following link:

    2>  http://go.microsoft.com/fwlink/?LinkId=124618

    2>  Sample script for deploying this package is generated at the following location:

    2>  C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointApp\obj\WebDeploy\MySharePointApp.Web.deploy.cmd

    2>  For this sample script, you can change the deploy parameters by changing the following file:

    2>  C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointApp\obj\WebDeploy\MySharePointApp.Web.SetParameters.xml

    2>  Successfully created package at: C:\_works\visual studio 2012\Projects\MySharePointApp\MySharePointApp\bin\Debug\app.publish\1.0.0.0\MySharePointApp.app

    3>------ Deploy started: Project: MySharePointApp, Configuration: Debug Any CPU ------

    3>Active Deployment Configuration: Deploy App for SharePoint

    3>Uninstall app for SharePoint:

    3>  Skipping the uninstall step because the app for SharePoint is not installed on the server.

    3>Install app for SharePoint:

    3>  Uploading the app for SharePoint...

    3>  Creating a trusted root authority in SharePoint for IIS Express.

    3>  Installation is in progress (00:00:00)

    3>  Installation is in progress (00:00:01)

    3>  Installation is in progress (00:00:02)

    3>  Installation is in progress (00:00:03)

    3>  Installation is in progress (00:00:05)

    3>  Installation is in progress (00:00:06)

    3>  App failed to install, cleaning up...

    3>  App installation cleanup failed due to errors.  Please see the app on the SharePoint site’s “Site Contents” page for details.

    3>  App installation encountered the following errors:

    3> 

    3>  @"Error 1

    3>        CorrelationId: ceeeafab-3834-40ea-b360-c29d103e2248

    3>        ErrorDetail: The remote hosting service is not configured.

    3>        ErrorType: Configuration

    3>        ErrorTypeName: Configuration

    3>        ExceptionMessage: The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU.

    3>        Source: RemoteWebSite

    3>        SourceName: Remote Web Site Deployment

    3> 

    3>  @"Error 2

    3>        CorrelationId: ceeeafab-3834-40ea-b360-c29d103e2248

    3>        ErrorDetail: The remote hosting service is not configured.

    3>        ErrorType: Configuration

    3>        ErrorTypeName: Configuration

    3>        ExceptionMessage: The trial period for this product has expired or Secure Store Shared Service is not supported for this SKU.

    3>        Source: RemoteWebSite

    3>        SourceName: Remote Web Site Deployment

    3>Error occurred in deployment step 'Install app for SharePoint': Failed to install app for SharePoint. Please see the output window for details.

    ========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

    ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

    Wednesday, February 6, 2013 9:35 AM
  • The following microsoft document shows secure store service as a feature of sharepoint foundation 2013.

    http://office.microsoft.com/en-us/sharepoint-server-help/introduction-to-external-data-HA102891586.aspx

    That's contrary to al00fy's post. Also till today there is no hotfix (to avoid the error message) available.

    Friday, April 12, 2013 1:25 PM
  • I do have exactly the same problem. And as highlighted by Antraczek, I also saw several official Microsoft references where it was stated that "secure store" will be supported on foundation edition too.

    Regards.

    Sylvain

    Monday, April 15, 2013 3:05 PM
  • I decide to temporary work around the problem by enable RevertToSelf authentication for bcs because user authentication isn't an option for me. Maybe there will come a guy walking accross the water an tell us the truth.


    • Edited by Antraczek Tuesday, April 16, 2013 6:43 AM
    Tuesday, April 16, 2013 6:41 AM
  • Although not able to walk across the water, the information I got was from Microsoft Tech Support themselves, we even got our "question credits" refunded.

    If any of you have the same abilities in that you can ask MS directly please can you so we can get consensus.

    Tuesday, April 16, 2013 6:47 AM
  • Has anyone been able to correct this error? I am getting this on my 2013 Foundation dev farm and am not sure how to make it go away. I have tried the steps listed in the comments and the psconfig commands, but nothing has worked so far. Please let us know an update if this is going to be corrected in a hotfix.

    Thanks,

    BJ

    Monday, July 8, 2013 12:38 PM
  • From what I've discovered, it looks like the problem caused by SSS Application Proxy Execute method which checks for the license. For sure, the required native library (OfficeServerSettings.dll) isn't available in SharePoint Foundation hence the checking always fails.

    Microsoft should patch that checking out.

    Tuesday, August 27, 2013 2:16 AM
  • Had this issue in SP2010.. Turned out for us it was one of the following..

    1# Is the 'server' service started? If not start it and iisreset. 

    2# psconfig -cmd secureresources; Then iisreset

    Tuesday, August 27, 2013 2:29 AM
  • Microsoft support states that the document mentions to this feature is error.

    This feature will be removed in upcoming update.

    Case closed!

    Thursday, August 29, 2013 4:06 AM
  • I am getting the same issue in SharePoint Foundation 2013.

    The 'configure store service' info on Technet says it applies to both SP Server and SPF: http://technet.microsoft.com/en-us/library/jj683109.aspx

    Also this feature comparison says secure store service is available in Foundation: http://technet.microsoft.com/en-NZ/library/jj819267.aspx#bkmk_FeaturesOnPremise

    Wednesday, September 11, 2013 11:26 PM
  • They leave many evidences to that.

    Like here: http://technet.microsoft.com/en-us/library/cc298801.aspx and http://technet.microsoft.com/en-us/library/cc678868.aspx(SSS database in SPF)

    Why? Just omit one check and we are good to go. Why don't they do that?


    • Edited by BusyPart Thursday, September 19, 2013 7:50 AM Add more links
    Thursday, September 19, 2013 7:45 AM
  • I have two SharePoint Foundation 2013 single server builds with SQL Server 2008 R2 SP1, both flooding the error logs with event IDs

    121:

    The administration component for application Search Service Application failed with exception System.InvalidOperationException: This operation uses the SharePoint Administration service (spadminV4), which could not be contacted.  If the service is stopped or disabled, start it and try the operation again.

       at Microsoft.SharePoint.Administration.SPServer.AddMemberToLocalWorkerProcessGroup(String userName)

       at Microsoft.Office.Server.Search.Administration.AnalyticsServiceAdministration.ProvisionServiceInstance(SearchServiceApplication app)

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

    and

    6841:

    Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (fd1e3c8f-d591-482e-ae2e-a8c62d21104c).

    Reason: This operation uses the SharePoint Administration service (spadminV4), which could not be contacted.  If the service is stopped or disabled, start it and try the operation again.

    Technical Support Details:

    System.InvalidOperationException: This operation uses the SharePoint Administration service (spadminV4), which could not be contacted.  If the service is stopped or disabled, start it and try the operation again.

       at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

       at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

    So the theory at the time of writing is that this is 'by design' because Microsoft have limited a feature in Foundation and these events will be supressed in a future patch.

    Monday, March 24, 2014 8:49 PM
  • I am experiencing the exact same issue that Raghavendra first posted about and it's been nearly 18 months. 

    In my case, after installing SPF 2013 last week, I also installed the March 2013 Cumulative update and then the December 2013 Cumulative update.   If there were plans to issue a hotfix/update to remove the Secure Store Service feature, then it didn't happen for any of the 2013 calendar year CUs.    

    If Secure Store Service is not supposed to be included in SPF 2013, then why do all the following documents say it is?

    http://technet.microsoft.com/en-us/library/cc298801.aspx

    http://technet.microsoft.com/en-us/library/cc678868.aspx

    http://blog.blksthl.com/2013/01/14/sharepoint-2013-feature-comparison-chart-all-editions/   (Thomas Balkeståhl seems to be very conscientious about keeping this feature list up-to-date and accurate.)

    Just read today that SP1 for SharePoint Foundation 2013 was re-released a couple of days ago.  I haven't installed it yet, but I am wondering if this service pack will address this issue - one way or the other.  We will see.   In the meantime, I am wondering if I should remove the Secure Store Shared Service and try to see if is still an available managed service after SP1 is installed. 

    Thursday, April 24, 2014 8:56 PM
  • I have the same problem. 

    I find using reflector:

    1. Method 

    private Execute checks static property Licensing.HasExpired

    2. Licensing.HasExpired uses static field  m_ExpirationFileTime, witch is assigned in static ctor Licensing() by method  GetExpirationFileTimeFromRegistry()

    3. Method  GetExpirationFileTimeFromRegistry() calls native DLL OfficeServerSettings.dll from folder C:\Program Files\Microsoft Office Servers\15.0\Bin\

    The problem is that foundation do not have this DLL. And next if you copy this dll to 15\bin folder, I find the next error.

    I find in Process Monitor that it tries to access Registry Key HKLM\Software\Microsoft\Office Server\15.0\ServerSettings. This key is not present on server.

    10:41:21.9816883 AM w3wp.exe 8020 RegOpenKey HKLM\Software\Microsoft\Office Server\15.0\ServerSettings NAME NOT FOUND Desired Access: Read

    I do not try to copy this key from another server with SharePoint Server 2013 installed. I think this is not a good idea. 

    So I think this is a Microsoft bug or using SSS in foundation is not supported.

    public static bool HasExpired { get { if (Licensing.m_ExpirationFileTime == long.MaxValue) return false; else return DateTime.UtcNow.ToFileTime() > Licensing.m_ExpirationFileTime; } } static Licensing() { try { ULS.SendTraceTag(1634366517U, (ULSCatBase) ULSCat.msoulscat_OSRV_SetupUpgrade, ULSTraceLevel.High, "Initializing Licensing API. This trace forces the initialization of ULS"); Licensing.m_ExpirationFileTime = Licensing.GetExpirationFileTimeFromRegistry(); } catch (LicensingException ex) { ULS.SendTraceTag(926447969U, (ULSCatBase) ULSCat.msoulscat_OSRV_SetupUpgrade, ULSTraceLevel.High, "{0}", new object[1] { (object) ((object) ex).ToString() }); } }

      private static long GetExpirationFileTimeFromRegistry()
        {
          long expirationTime = 0L;
          int num = 0;
          try
          {
            using (Microsoft.Office.Server.Security.SecurityContext.RevertToSelf())
              num = Licensing.NativeMethods.GetExpirationTime(out expirationTime);
          }
          catch (Exception ex)
          {
            throw new LicensingException(StringResourceManager.GetString("Exception_Licensing_cs1"), ex);
          }
          if (num == 0)
            return expirationTime;
          throw new LicensingException(string.Format((IFormatProvider) CultureInfo.InvariantCulture, StringResourceManager.GetString("Exception_Licensing_cs2"), new object[1]
          {
            (object) num
          }));
        }


    10:41:21.9816883 AM w3wp.exe 8020 RegOpenKey HKLM\Software\Microsoft\Office Server\15.0\ServerSettings NAME NOT FOUND Desired Access: Read

    Friday, July 11, 2014 12:36 PM
  • Hi,

    I've right the same problem in a SharePoint 2013 Foundation installation.

    My question is:

    since this feature is no more available in Foundation edition, then why is it possible to install a Secure Store Service with the last SharePoint SP1 installer?

    Maybe I'm missing something but if I can't use it, then why can I install it?

    Thursday, August 28, 2014 1:09 PM
  • HI Raghav,please find the below link that exactly discussion about the issue that your seeing in your environment.

    http://expertsharepoint.blogspot.de/2014/06/the-trial-period-for-this-product-has.html


    Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

    Thursday, September 4, 2014 9:02 AM
  • Did you resolve?

    I have the same problem! 

    Monday, December 8, 2014 6:31 PM
  • I just found the thread here as we have the same issue on our Foundation Sharepoint Server. The server is fully patch and we have 2015. But its still possible to configure this... Currently no solution worked for me either ...

    This is very bad as sharepoint foundation is/was a great product to start with if a company is looking into sharepoint. However it looks like that MS didn´t really take care of it.

    Wednesday, September 16, 2015 9:26 AM
  • Hi Guys,

    I had came across same issue few months ago regarding secure store service.

    While working with MS it had been identified as bug with SPF 2013(specifically).

    However i am not sure if this bug has been fixed in any recently update. 

    Wednesday, September 16, 2015 4:46 PM
  • It likely won't be fixed. We had noted back in the pre-SP1 days the bug existed. Given Secure Store hasn't been removed, it likely won't be removed at this point.

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Wednesday, September 16, 2015 4:54 PM
    Moderator
  • Any updates with Secure Store support in Foundation, guys? I meet this bug in SPF 2013 + SP1 now..

    Independent SharePoint Developer, freelancer http://blog.sharepoint-develop.com/

    Saturday, January 23, 2016 5:10 PM
  • At this point in the product lifecycle, don't expect any changes.

    Trevor Seward

            

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Saturday, January 23, 2016 5:33 PM
    Moderator
  • In 2013 I'm trying to connect external list to SQL on another machine, and get 

    Message from External System : 'Login failed for user 'DOMAIN\USERNAME$'.'.
    Strange situation that I can input sa credentials in "Data source", but cannot do the same creating External Content type..

    I know for 2010 there is workaround - to install  Search Server Express (SSE) on 2010

    Or to use Dataview Web part instead of External Content Type like described here: http://whitepages.unlimitedviz.com/2010/08/connection-limitations-using-bcs-with-sharepoint-foundation-and-a-workaround/

    But I'd like to connect real sharepoint list, not DataView webpart..

    Secure Store is needed for this task, but maybe change to domain account for BCS Service Application will resolve..

    Update: Yes, if interested - domain account for Sharepoint Application pool resolves this problem.


    Independent SharePoint Developer, freelancer http://blog.sharepoint-develop.com/


    • Edited by Rockie_ Sunday, January 24, 2016 7:59 PM updated
    Saturday, January 23, 2016 7:48 PM