Forum Widgets
Latest Discussions
Clean up missing dependencies - Access Services
We migrated our farm from SharePoint Server 2019 to SharePoint Server Subscription Edition (SE) using the Database Attach method. When running Test-SPContentDatabase against our content database , we receive missing feature errors for deprecated Access Services: 744b5fd3-3b09-4da6-9bd1-de18315b045d and d2b9ec23-526b-42c5-87b6-852bd83e0364. The "Locations :" field in the output is completely blank/null. We removed the feature from our site collections. How can we resolve the issue.
SharePoint SE: Unable to Join New WFE Server Due to License State Mismatch
Hello Community, We're unable to join a new SharePoint Server Subscription Edition (SE) WFE server to an existing farm. Environment SharePoint Server Subscription Edition Existing farm build: 16.0.19725.20384 New server build: 16.0.19725.20384 English (1033) and Hindi (1081) language packs installed on both servers KB5002873 installed on both servers Farm was migrated from SharePoint 2016/2019 to SharePoint SE using the supported database attach method Issue During PSConfig, the server fails to join the farm. ULS logs show the failure in: SPFarm.EnsureCurrentServerProductsMatchFarmProducts() The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm. The license state for the current server doesn't match the farm's license state. Show more lines What we've verified SharePoint build versions match (16.0.19725.20384) Microsoft.SharePoint.dll versions match Get-SPProduct -Local output matches Language packs match KB5002873 installed on both servers Config DB Versions table shows successful upgrades through 16.0.19725.20384 Has anyone encountered a similar license-state mismatch when adding a new server to a SharePoint SE farm, particularly one migrated from SharePoint 2016/2019? Any guidance on additional licensing checks performed during SPFarm.Join() would be appreciated.SP SE Migration: Test-SPContentDatabase reports missing Access Services feature with Null Locations
We are migrating our farm from SharePoint Server 2019 to SharePoint Server Subscription Edition (SE) using the Database Attach method. When running Test-SPContentDatabase against our content database (WSS_Content), we receive missing feature errors for deprecated Access Services: 744b5fd3-3b09-4da6-9bd1-de18315b045d and d2b9ec23-526b-42c5-87b6-852bd83e0364. The Locations : field in the output is completely blank/null. We already deactivated the Access features. The SharePoint Configuration Wizard crashes. How we can completely get rid of it.SharePoint SE – Unknown SQL Exception 18452 occurred. Login failed.
This month we applied OS updates to the DB Server. Site was up. Then we applied OS Updates to App server, site went down and we reverted it. Then we applied OS updates on WFE server. The site is up. However, in WFE when running Get-SPFarm or running PSConfig on the WFE, it throws the following errors: PowerShell / PSConfig: “Cannot access the local farm. Verify that the local farm is properly configured…” Configuration Wizard: “Failed to detect if this server is joined to a server farm.” The Error Logs: Checking the Windows Event Viewer on the WFE during a database connection attempt shows: Unknown SQL Exception 18452 occurred. Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. Network connectivity is fully operational. AD Domain trust is healthy. Local machine groups are clean: NT AUTHORITY\SYSTEM is not present inside the local WSS_WPG or IIS_IUSRS groups. DisableLoopbackCheck is already set to 1 in the registry. Any help on how to get the error is greatly appreciated.
SharePoint SE - Distributed cache service is not enabled in this deployment.
Hi everyone, I have been struggling for a few weeks now with a Distributed Cache issue in my SharePoint farm. The service configuration seems completely out of sync between my two Web Front Ends (WFEs). 1 Root Cause / History: Originally, the Distributed Cache was working perfectly. However, after a Windows Update, both of our original WFE servers broke completely (we couldn't repair them using DISM). Because of this, we built two brand new WFE servers to replace them. Crucially, because the old servers were broken, we performed the steps in this order: 1. We built and added the two new WFE servers to the farm first. 2. After adding the new ones, we removed the two broken ones using the Configuration Wizard, and subsequently deleted them from Central Administration since they were still showing up. Because the old servers were never gracefully decoupled from the Distributed Cache before they died and were removed, the internal Distributed Cache configuration in the SharePoint configuration database is now corrupted. 2 Environment & Farm Topology: • SharePoint Version: SharePoint Subscription Edition (SE) • OS: Windows Server 2025 • Database: SQL Server 2025 • Topology: 2 Web Application servers (App servers) and 2 brand new Web Front End servers (Server 1 and Server 2). • Note: All required Distributed Cache firewall ports (22233, 22234, 22235, 22236) are completely open on both servers. 3 The Current Symptoms on the New WFEs: • Server 1: The Windows Configuration Wizard runs and completes successfully. However, in Central Administration, the Distributed Cache service status for this server is stuck on "Error Stopping". • Server 2: Distributed Cache does not work at all. Running Get-SPCacheHost prompts for a HostName, indicating it cannot find the host in the cache configuration. • Cache Health Error: Running Get-SPCacheClusterHealth fails completely with: ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster • Health Analyzer Errors: 1. "Distributed cache service is not enabled in this deployment." 2. "Server role configuration isn't correct." (Specifically flagging Server 2). 4 What I Have Tried So Far: 1. Cleaned up old servers from Config: I exported the cache cluster config (Export-SPCacheClusterConfig), manually removed the two old, decommissioned servers from the XML file, and imported it back. 2. Repair via Central Admin: Tried to use the built-in repair and fix options in CA, but without success. 3. Attempted Fix from Microsoft Learn: I followed the steps outlined in this Microsoft Learn thread regarding a renamed server issue: [https://learn.microsoft.com/en-ie/answers/questions/5907941/distributed-cache-not-working-on-a-renamed-sharepo] 4. Forced Deletion on Server 2: Because Remove-SPDistributedCacheServiceInstance failed with a cacheHostInfo is null error, I used PowerShell to force-delete the service instance object on Server 2: PowerShell $instanceName = "SPDistributedCacheService Name=SPCache" $serviceInstance = Get-SPServiceInstance | ? { ($_.Service.ToString()) -eq $instanceName -and ($_.Server.Name) -eq "Server02" } $serviceInstance.Delete() 5. Re-adding Server 2: When I now try to re-add the instance on Server 2 using Add-SPDistributedCacheServiceInstance, it fails with: ErrorCode<HostAlreadyPresent>:SubStatus<ES0001>:Host name Server02 is already present in cluster configuration. 6. Configuration Wizard on Server 2: Running the SharePoint Configuration Wizard (PSConfig) on Server 2 fails with: An exception of type System.InvalidOperationException was thrown. Additional exception information: cacheHostInfo is null. 7. Farm Rejoin: I completely removed Server 2 from the SharePoint farm and added it back again. Unfortunately, this did not resolve the Distributed Cache mismatch. 5 Summary of the Problem: Server 1 is stuck on "Error Stopping" in CA. Server 2 is completely disconnected from the cache cluster (Failed to connect to hosts in the cluster). SharePoint throws HostAlreadyPresent when trying to add Server 2, but throws cacheHostInfo is null when trying to configure or remove it, while complaining that Server 2's role configuration is incorrect. Any help would be greatly appreciated!Error Patching SharePoint SE to Feb 2026
Recently we tried a SPSE patch from CU July 2023 to CU Feb 2026. Seems the leap was too big for SharePoint. The patch destroyed the farm: 1. Took 2 hours to complete 2. Successfully ran PSconfig 3. Sharepoint would just not start. HTTP 500 everywhere (Central Admin, all site collections) Pinned down the error to: Source: mssearch.exe y w3wp.exe ( App Pool web apps) System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.OnPrem.Flighting.SPOnPremFlight.IsFlightEnabled(Int32 flightId) System.UnauthorizedAccessException: Access is denied. (HRESULT: 0x80070005) at Microsoft.SharePoint.SPGroup.InitMember() at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass60_0.b__0() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.OnPrem.Flighting.ECSSPFlightDataProvider.InitializeEnabledFlightsInfoDict() at Microsoft.SharePoint.OnPrem.Flighting.ECSSPFlightDataProvider..cctor() at Microsoft.SharePoint.OnPrem.Flighting.SPOnPremFlight..cctor() at Microsoft.SharePoint.OnPrem.Flighting.SPOnPremFlight.ensureDebugFlightIdsInitialized() at Microsoft.SharePoint.OnPrem.Flighting.SPOnPremFlight.IsFlightEnabled(Int32 flightId) This seems to be something related to a OnPrem.Flighting.SPOnPremFlight service. No idea what that is. So: 1. Do I need to upgrade the SP Workflow Manager first? 2. The SYSTEM account was on WSS_WPG before the update (confirmed it was). Need to remove it before patch? 3. Do I need to enable AMSI before the update? Had to restore the VMs and all is working fine. Would you think I should: 1. Patch to August 2025 16.0.18526.20508 first and check the farm? (pre-september 2025) 2. Then jump to April 2026? Thanks for any pointers
Third party oidc authentication with SPSE failed
Following the new https://docs.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication , I managed configuring oidc authenticate in SPSE with ADFS. I then tried third party oidc authentication in SPSE with Keycloak, but failed with following errors : 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Monitoring nasq Medium Entering Monitored Scope (Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F)). Parent=None 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhz Medium SPRequestModule.BeginRequestHandler End, SP Build Version: '16.0.14326.20450' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brd4 Medium SPContextCookie : Using full host domain for cookie. CookieName: 'nSGt'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brdr Medium SPCryptoContextCookie : Initial Secondary certificate is null and we did not receive a secondary certificate thumbprint. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brc8 Medium SPNonceCookie : The Identifier is set successfully. Identifier: '', NonceToSendToIdentityProvider: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A-CB0F14DA2F6FF1E6302B9120B3FDACE0CE6B228FA26DC9915A3264E4EEF4FA74'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w647 Medium Using input cookie name. CookieName: 'nSGt-2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brbv Medium SPNonceCookie : Successfully read nonce cookie. Version: '0', Seed: '94DC58B58F1B35EFF01163B1124CC9539C338C80D3829F09', Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brc8 Medium SPNonceCookie : The Identifier is set successfully. Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A', NonceToSendToIdentityProvider: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A-CB0F14DA2F6FF1E6302B9120B3FDACE0CE6B228FA26DC9915A3264E4EEF4FA74'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w647 Medium Using input cookie name. CookieName: 'nSGt-2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Authentication Authorization deffe Medium The browser does support SameSite at revision 3 of RFC6265. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Nonce Cookie 9brbj Medium SPNonceCookie : Deleted nonce cookie if present. Identifier: '2C4E2FE7F0728A63048D3F2F9AE63C6814916757CF55CC2A'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Security Token Handler 8p0r7 Medium Audience GUID matches trusted login provider default client identifier. Audience: 'new-sharepoint', provider Default Identifier: 'new-sharepoint', provider Uri: ''. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.07 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Topology aeayb Medium SecurityTokenServiceSendRequest: RemoteAddress: 'http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Security.IWSTrustChannelContract' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:8ed01142-6684-422a-8d99-6028560b88a0' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Topology aeax9 Medium SecurityTokenServiceReceiveRequest: LocalAddress: 'http://spdev-se1.:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:8ed01142-6684-422a-8d99-6028560b88a0' 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Monitoring nasq Medium Entering Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6kv Medium STS Call: Creating Claims Operations Scope for Applies To Uri: 'https://teamse1/'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Claims Authentication a6oo7 Medium Created claims operation context from uri. ContextUri: 'https://teamse1/', Source: 'SiteWithoutSiteSubscription'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6k3 Medium Creating SPSecurityTokenRequestContextV2 object for security token service Issue request. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Security Token Service 9w6k0 Monitorable STS Call: Failed to issue new security token. Exception: 'System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceV2.Issue(ClaimsPrincipal principal, RequestSecurityToken request)'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.08 w3wp.exe (0x40E4) 0x33E4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (ExecuteSecurityTokenServiceOperationServer) 执行时间=3.7961; CPU Milliseconds=3; SQL 查询计数=0; Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Security Token Service Caller btgia High SPSecurityContext: Request for security token failed with exception. Exception: 'System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 8306 Critical An exception occurred when trying to issue security token: Validate signature failure : no found matched security key for token signature.. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w636 Unexpected Claims Saml Sign-In: Could not get local token for trusted third party token. FaultException: 'System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。'. Stack: ' 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenFo... 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09* w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication 9w636 Unexpected ...rLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments)'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhw Medium SPRequestModule.ErrorAppHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/Authenticate.aspx, Error=Validate signature failure : no found matched security key for token signature. 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequestBase request) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnAuthenticateRequest(Object sender, EventArgs eventArgs) 在 System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在 System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 在 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime tkau Unexpected System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]: Validate signature failure : no found matched security key for token signature. 在 System.ServiceModel.Security.WSTrustChannel.ReadResponse(Message response) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) 在 System.ServiceModel.Security.WSTrustChannel.Issue(RequestSecurityToken rst) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) 在 Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequestBase request) 在 System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) 在 Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModuleV2.OnAuthenticateRequest(Object sender, EventArgs eventArgs) 在 System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() 在 System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) 在 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously... 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09* w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime tkau Unexpected ...) 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Validate signature failure : no found matched security key for token signature. (错误详细信息等于 很可能由 IncludeExceptionDetailInFaults=true 创建的 ExceptionDetail，其值为: System.IdentityModel.Tokens.SecurityTokenException: Validate signature failure : no found matched security key for token signature. 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateSignature(String token, TokenValidationParameters validationParameters) 在 System.IdentityModel.Tokens.JwtSecurityTokenHandler.ValidateToken(String securityToken, TokenValidationParameters validationParameters, SecurityToken& validatedToken) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(String tokenString, TokenValidationParameters validationParameters, SecurityToken& token) 在 Microsoft.SharePoint.IdentityModel.SPOpenIDSecurityTokenHandlerV2.ValidateToken(SecurityToken token) 在 Microsoft.SharePoint.IdentityModel.SPSecurityTokenRequestContextV2..ctor(ClaimsIdentity identity, RequestSecurityToken request, Boolean initializeForActor, SPSecurityTokenRequestTypeV2 overrideRequestType) ...)。 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General aat87 Monitorable 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=False, UserIdentityName=, ClaimsCount=0 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.09 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation General agxkz High calling GetCurrentGenericSetupPath for a versioned path: TEMPLATE\LAYOUTS 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s97c Medium SPApplicationAuthenticationModuleV2.IsBearerChallengeRequested: Return 'False'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s97n Medium The request isn't made to a page which allows NeverAuth to be specified in the query string 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Claims Authentication crpqx Medium STS setting for SuppressModernAuthForOfficeClients:'True'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Application Authentication 9s976 Medium IsClaimsTrustedAuthenticationOnly: 'False', IsOfficeClientIDCRLRequest: 'False', HasSPTrustedSecurityTokenIssuer: 'False', ForceIdcrlForOfficeClients: 'True'. 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwh5 Medium SPRequestModule.PreSendRequestHeaders End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwhx Medium SPRequestModule.ErrorAppHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwia Medium SPRequestModule.PostLogRequestHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwib Medium SPRequestModule.PostLogRequestHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwic Medium SPRequestModule.EndRequestHandler Begin 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 avwhy,0 nasq,0 avwhz,0 9brd4,0 9brdr,0 9brc8,0 9w647,0 9brbv,0 9brc8,0 9w647,0 deffe,0 9brbj,2 8p0r7,0 aeayb,11 btgia,0 9w636,0 avwhw,0 8nca,0 tkau,0 ajlz0,1 aat87,5 agb9s,0 agxkz,1 9s97c,0 9s97n,0 crpqx,0 9s976,0 avwh5,0 avwhx,0 avwia,0 avwib,0 avwic 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Runtime aoxsq Medium Sending HTTP response 200 for HTTP POST request 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Unified Audit bm7sm High SPRequestModule::CreatePageViewedAuditEntry: Required parameters not set properly,exiting creating PageViewed SPUnifiedAuditEntry 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope: (Request (POST:https://teamse1/_layouts/15/Authenticate.aspx?Source=%252F)) 执行时间=29.1365; CPU Milliseconds=18; SQL 查询计数=0; Parent=None 28bc00a0-1979-300a-3da4-d9c46cbf4124 11/07/2021 16:48:29.10 w3wp.exe (0x0C38) 0x4AB0 SharePoint Foundation Asp Runtime avwid Medium SPRequestModule.EndRequestHandler End 28bc00a0-1979-300a-3da4-d9c46cbf4124 Through browser F12 debug, the authentication flow had successfully gone from Keycloak to Sharepoint : _layouts/15/Authenticate.aspx?Source=%2F, and id_token successfully generated and could be verified through https://jwt.ms/ How to integrate 3rd party oidc server with SPSE?
Patching SSSE
Having read all the documentation about CUs for SSSE I am still none the wiser as much of what is written, in the many related webpages, appears ambigous, unclear and contraditory to me. Could anyone clarify two points: If, say,the December 2025 CU is installed, does it included all security and non security fixes for all features in SSSE? Will Windows Update install the latest CE every month without any intervention including upgrading databases etc? Thanks for any advice ZDSharePoint Server Subscription Edition (on-prem) REST API call via oAuth
This is a SharePiont Server Subscription Edition on-prem farm. and Extrnal application needs to use data from SharePoint via REST api calls. Need to setup external application to use SharePoint data from REST api via oAuth. 1) What are the steps i need to follow? 2) can this be supported by SharePoint Only App authentication (https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azureacs) for SPSE on-prem? Any sample REST based API calls to get tokens and call SharePoint would be really helpful. 3) Is it possible to use Azure AD app in for the same? if so how to configure trust between Azure AD and SPSE on-prem farm?
SharePoint Designer 2013 is deprecated
I am not sure that this topic has been discussed before. https://learn.microsoft.com/en-us/sharepoint/what-s-new/what-s-deprecated-or-removed-from-sharepoint-server-subscription-edition According to this page the, July 14, 2026 after that date, SharePoint Designer 2013 will no longer be supported. But it looks like we still can create a publish workflows? Does any body have suggestion for 3. Parties’ solution for that. Did checked Nintex K2 and its very expensive. We just have 10 workflows send email with content in body. And one approval workflow. Any solution i can create with SPFX or in SP to have this opportunity to create WF. I know about VS but there are not that simple.