none
SharePoint 2016 - Can't Open Secure Store Service RRS feed

  • Question

  • Hello Community!

    I'm working in SP 2016, with full server and platform rights, I have created a Secure Store Service Managed Service but I can't open the service!  I click on the link, I'm navigated to the page, but nothing displays and no error messages are shown.  Has anyone else seen this problem and if so please LMK how you resolved it.

    Thanks!

    Tom


    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Tuesday, May 7, 2019 7:14 PM

Answers

  • Ah ha? So you might need a new Enterprise license key for your SharePoint?

    Not sure but is Secure Store service only available in SharePoint server but not foundation?


    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Please Vote and Mark as Answer if it helps you.

    • Marked as answer by Tom Molskow Friday, May 31, 2019 5:18 PM
    Thursday, May 23, 2019 12:48 AM
  • Hi Tom,

    I suggest you could check if the trial period for your SharePoint product has expired.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    • Marked as answer by Tom Molskow Friday, May 31, 2019 5:17 PM
    Thursday, May 30, 2019 9:45 AM
    Moderator

All replies

  • Hi

    Do you mean you meet a blank page? Have you tried to use different web browser?


    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Please Vote and Mark as Answer if it helps you.

    Wednesday, May 8, 2019 1:49 AM
  • Hi Tom,

    To troubleshoot the issue, check things below:

    1. Go to IIS->application pools->restart ”SecurityTokenServiceApplicationPool”.

    2. IIS reset.

    3. Create a new Secure Store Service application and check if the same issue will occur.

    More reference:

    Cannot Complete This Action as the Secure Store Shared Service is not Responding.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.


    Wednesday, May 8, 2019 7:19 AM
    Moderator
  • Yes, just a blank page - I did try a Chrome, IE, and FireFox - Same results

    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Wednesday, May 8, 2019 3:09 PM
  • Are the web requests normal when you access the site? by using Fiddler or network watcher.

    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Please Vote and Mark as Answer if it helps you.

    Thursday, May 9, 2019 1:11 AM
  • Hi Tom,

    How is everything going?

    Is there anything update about this issue?

    If the reply is helpful to you, you could mark the helpful reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, May 10, 2019 8:05 AM
    Moderator
  • Hi Tom,

    I am checking to see how things are going there on this issue. Please let us know if you would like further assistance.

    If the issue was resolved, you can mark the helpful post as answer to help other community members find the helpful information quickly. 

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, May 16, 2019 2:39 AM
    Moderator
  • Hey Justin,

    Sorry for the late reply, here is the fiddler traffic - it looks normal:

    Request Count:   1
    Bytes Sent:      751		(headers:751; body:0)
    Bytes Received:  788		(headers:788; body:0)
    
    ACTUAL PERFORMANCE
    --------------
    ClientConnected:	15:53:31.243
    ClientBeginRequest:	15:53:31.259
    GotRequestHeaders:	15:53:31.259
    ClientDoneRequest:	15:53:31.259
    Determine Gateway:	0ms
    DNS Lookup: 		0ms
    TCP/IP Connect:	0ms
    HTTPS Handshake:	0ms
    ServerConnected:	15:53:31.259
    FiddlerBeginRequest:	15:53:31.259
    ServerGotRequest:	15:53:31.259
    ServerBeginResponse:	15:53:31.259
    GotResponseHeaders:	15:53:31.259
    ServerDoneResponse:	15:53:31.259
    ClientBeginResponse:	15:53:31.259
    ClientDoneResponse:	15:53:31.259
    
    
    RESPONSE BYTES (by Content-Type)
    --------------
    ~headers~: 788
    
    
    ESTIMATED WORLDWIDE PERFORMANCE
    --------------
    The following are VERY rough estimates of download times when hitting servers based in Seattle.
    
    US West Coast (Modem - 6KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (Modem)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (Modem)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    US West Coast (DSL - 30KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (DSL)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (DSL)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    
    ________________
    Learn more about HTTP performance at http://fiddler2.com/r/?HTTPPERF
    

    Request Count:   1
    Bytes Sent:      807		(headers:807; body:0)
    Bytes Received:  514		(headers:514; body:0)
    
    ACTUAL PERFORMANCE
    --------------
    ClientConnected:	15:53:31.243
    ClientBeginRequest:	15:53:31.259
    GotRequestHeaders:	15:53:31.259
    ClientDoneRequest:	15:53:31.259
    Determine Gateway:	0ms
    DNS Lookup: 		0ms
    TCP/IP Connect:	0ms
    HTTPS Handshake:	0ms
    ServerConnected:	15:53:31.259
    FiddlerBeginRequest:	15:53:31.259
    ServerGotRequest:	15:53:31.259
    ServerBeginResponse:	15:53:31.275
    GotResponseHeaders:	15:53:31.275
    ServerDoneResponse:	15:53:31.275
    ClientBeginResponse:	15:53:31.275
    ClientDoneResponse:	15:53:31.275
    
    	Overall Elapsed:	0:00:00.015
    
    RESPONSE BYTES (by Content-Type)
    --------------
    ~headers~: 514
    
    
    ESTIMATED WORLDWIDE PERFORMANCE
    --------------
    The following are VERY rough estimates of download times when hitting servers based in Seattle.
    
    US West Coast (Modem - 6KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (Modem)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (Modem)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    US West Coast (DSL - 30KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (DSL)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (DSL)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    
    ________________
    Learn more about HTTP performance at http://fiddler2.com/r/?HTTPPERF
    
    

    Request Count:   1
    Bytes Sent:      682		(headers:682; body:0)
    Bytes Received:  4,943		(headers:569; body:4,374)
    
    ACTUAL PERFORMANCE
    --------------
    ClientConnected:	15:53:31.243
    ClientBeginRequest:	15:53:35.026
    GotRequestHeaders:	15:53:35.026
    ClientDoneRequest:	15:53:35.026
    Determine Gateway:	0ms
    DNS Lookup: 		0ms
    TCP/IP Connect:	0ms
    HTTPS Handshake:	0ms
    ServerConnected:	15:53:31.259
    FiddlerBeginRequest:	15:53:35.026
    ServerGotRequest:	15:53:35.026
    ServerBeginResponse:	15:53:35.042
    GotResponseHeaders:	15:53:35.042
    ServerDoneResponse:	15:53:35.042
    ClientBeginResponse:	15:53:35.042
    ClientDoneResponse:	15:53:35.042
    
    	Overall Elapsed:	0:00:00.016
    
    RESPONSE BYTES (by Content-Type)
    --------------
    application/json: 4,374
           ~headers~: 569
    
    
    ESTIMATED WORLDWIDE PERFORMANCE
    --------------
    The following are VERY rough estimates of download times when hitting servers based in Seattle.
    
    US West Coast (Modem - 6KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (Modem)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (Modem)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    US West Coast (DSL - 30KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (DSL)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (DSL)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    
    ________________
    Learn more about HTTP performance at http://fiddler2.com/r/?HTTPPERF
    

    Request Count:   1
    Bytes Sent:      647		(headers:647; body:0)
    Bytes Received:  491		(headers:491; body:0)
    
    ACTUAL PERFORMANCE
    --------------
    ClientConnected:	15:53:31.243
    ClientBeginRequest:	15:53:43.796
    GotRequestHeaders:	15:53:43.796
    ClientDoneRequest:	15:53:43.796
    Determine Gateway:	0ms
    DNS Lookup: 		0ms
    TCP/IP Connect:	0ms
    HTTPS Handshake:	0ms
    ServerConnected:	15:53:31.259
    FiddlerBeginRequest:	15:53:43.796
    ServerGotRequest:	15:53:43.796
    ServerBeginResponse:	15:53:43.811
    GotResponseHeaders:	15:53:43.811
    ServerDoneResponse:	15:53:43.811
    ClientBeginResponse:	15:53:43.811
    ClientDoneResponse:	15:53:43.811
    
    	Overall Elapsed:	0:00:00.015
    
    RESPONSE BYTES (by Content-Type)
    --------------
    ~headers~: 491
    
    
    ESTIMATED WORLDWIDE PERFORMANCE
    --------------
    The following are VERY rough estimates of download times when hitting servers based in Seattle.
    
    US West Coast (Modem - 6KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (Modem)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (Modem)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    US West Coast (DSL - 30KB/sec)
    	RTT:		0.10s
    	Elapsed:	0.10s
    
    Japan / Northern Europe (DSL)
    	RTT:		0.15s
    	Elapsed:	0.15s
    
    China (DSL)
    	RTT:		0.45s
    	Elapsed:	0.45s
    
    
    ________________
    Learn more about HTTP performance at http://fiddler2.com/r/?HTTPPERF
    


    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Monday, May 20, 2019 3:58 PM
  • How is the network watcher?  Like below picture from Chrome F12.

    I think the issue has two possibilities.

    1# Fake blank, often caused by client web browser. Since you have tried different web browser.. How many servers in your farm? Try a different server to access it.

    2# Real blank that caused by some errors which should be reacted in network monitor..


    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Please Vote and Mark as Answer if it helps you.

    Tuesday, May 21, 2019 6:18 AM
  • Hi Tom,

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, May 22, 2019 6:55 AM
    Moderator
  • @Justin - Sorry, after deleting and reinstalling the Secure Store Service I now get this error - 

    Sorry, something went wrong

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

    Here is the Correlation error.


    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Wednesday, May 22, 2019 2:28 PM
  • Ah ha? So you might need a new Enterprise license key for your SharePoint?

    Not sure but is Secure Store service only available in SharePoint server but not foundation?


    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Please Vote and Mark as Answer if it helps you.

    • Marked as answer by Tom Molskow Friday, May 31, 2019 5:18 PM
    Thursday, May 23, 2019 12:48 AM
  • Hi Tom,

    The Secure Store service is available in SharePoint Foundation, SharePoint standard and SharePoint enterprise.

    To troubleshoot the issue, you could clear SharePoint configuration cache and then create the Secure Store Service application.

    More reference:

    SharePoint 2013 Standard vs. Enterprise vs. Foundation Feature Comparison Matrix.

    Clearing the SharePoint Configuration Cache.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, May 23, 2019 7:38 AM
    Moderator
  • Hi Tom,

    How is everything going?

    Is there anything update about this issue?

    If the reply is helpful to you, you could mark the helpful reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, May 27, 2019 2:19 AM
    Moderator
  • @Sara - sorry, I did follow your instructions, but now I'm back to having just a blank page when I click on the Secure Store Manage icon.

    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Monday, May 27, 2019 6:16 PM
  • Hi Tom,

    To troubleshoot the issue, check things below:

    1. Switch to another browser.

    2. Switch to another server and open the Secure Store Service application to check if the same issue will occur.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, May 28, 2019 7:26 AM
    Moderator
  • @Sara - I followed those steps, now I get this message in all browsers and on all servers:

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

    Urggghhhh!  This thing's a real mystery.


    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy



    Tuesday, May 28, 2019 4:46 PM
  • Hi Tom,

    I suggest you could check if the trial period for your SharePoint product has expired.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    • Marked as answer by Tom Molskow Friday, May 31, 2019 5:17 PM
    Thursday, May 30, 2019 9:45 AM
    Moderator
  • @Sara - Yep, it was as simple as that - thanks Sara!

    Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award - Linked-In - SharePoint Gypsy

    Friday, May 31, 2019 5:17 PM