Hi,

We use Sharepoint 2013 and WorkFlow Manager 1.0. The certificate for the WorkFlow Manager farm has expired.  Is there some powershell commands I can run to update the certificate?  Most forums say I must uninstall Workflow Manager and then reinstall?  If this is the only option, can you point me to an article with the steps needed?

Thanks,

Regina 

SharePoint Farm Admin

Hi,

1) We are planning to install the security patches on PROD environment as below:

Latest Build Version Installed :- 15.0.5179.1000
Latest CU installed :- KB4484121

We have SQL always ON between PROD and DR database servers for  sharePoint Application content database.Hence, data are always sync between these 2 environments.

If we do not install these patches in DR i.e. delay by a month let say, and if we perform DR test (bringing PROD down and DR up) , would it cause any issue in DR environment for any of sharePoint related functionality ?

2) Is there any way to roll back these patches on PROD environment if something goes wrong ?

Hi Team,

We are planning to move Visual Studio to latest version 2019. So wanted to know the answer of the below question.

What is the highest version of .NET Framework supported by SharePoint 2013?

Thanks & Regards,

Gopi Thakur

Hello All,

Is SharePoint Profile Synchronization or Active Directory the best option for Profile Synchronization? And is it any Thorough documentation out there about the configuration process??

Mike W

SharePoint Engineer - Mike

Hi Team,

I wanted to install VS 2017 in one server and VS 2019 in another server where VS 2013  already exists.

Can VS 2013 and VS 2017 Co-exist in the same server?

Can VS 2013 and VS 2019 Co-exist in the same server?

Thanks and Regards,

Gopi Thakur

Hello Team,

Just curious, If we have multiple WFEs, Apps severs along with DB server, can we say sharepoint farm is actually the good example of distributed system?

Thanks.

Hi There,

I have the custom application in csharp using VS2013(.net Framework 4.5) and SharePoint 2013 in windows 2012 R2. 

Will it be opened without migration using VS2017 or VS2019 after setting the .net framework 4.5?

Thanks & Regards,

Gopi Thakur

Dears,

Kindly provide the Rest API/Java Script to download the file from SharePoint site.

Note: We have to make sure the script do not needs SP Context to Run. 

Environment: SP2013,WIN2012 

Limit the noderunner.exe High Memory:

We have been experiencing a very high memory utilization on both the index partitioning servers.

Search Topology Defined:

No.of searchable Items: 7,248,095 

Changing noderunning.exe.config is not supported (or) not recommended for Production environment. Solution available if to scale up the memory on the index servers.

Get-SPEnterpriseSearchService is set to "PartlyReduced"

We have applied the memory scale up to both the index partition component servers and after a week period we are receiving alerts on both the index servers with high memory consumption.

Please advice on how to limit the memory consumption on both the index servers

I have followed the steps in this TechNet blog post and it all seemed to go well until I try to actually log in using ADFS.

When I navigate to the web application, I am presented with a dropdown to select the credential type. I select ADFS and am sent to the ADFS login page. I enter the correct credentials and am then sent to https://WEB_APPLICATION_HOSTNAME/_trust, and this page displays an ASP.NET yellow screen of death with:

-----------------------

    Specified method is not supported.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.ServiceModel.FaultException`1[[System.ServiceModel.ExceptionDetail, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]: Specified method is not supported.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:


    [FaultException`1: Specified method is not supported.]
       Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response) +249
       Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) +83
       Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst) +33
       Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties) +1103
       Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf) +72
       Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments) +1859
       Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.OnSessionSecurityTokenCreated(SessionSecurityTokenCreatedEventArgs eventArgs) +590
       Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SetPrincipalAndWriteSessionToken(SessionSecurityToken sessionToken, Boolean isSession) +90
       Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request) +701
       Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) +323
       Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs eventArgs) +138
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +215
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +97

-----------------------

From the appearance of the error, it looks like SharePoint is internally sending a request to the security token service and the latter is responding saying that it's using an invalid SOAP method, but that is just a guess.

I have tried the steps from this Fiddler blog post to try to route these requests through Fiddler, but Fiddler doesn't capture anything.

Google searches for this situation aren't turning up anything remotely resembling my situation. What can I do to begin troubleshooting this?

Below are the ULS logs from the request to the _trust endpoint. Of note, the first line gives me some concern. The Uri here is the URN I added in step 7 of following the TechNet blog post, but it seems to be resulting in some sort of error.

-----------------------

    SharePoint FoundationGeneraladyrvHighCannot find site lookup info for request Uri urn:*******.
    SharePoint FoundationClaims Authenticationamb82UnexpectedCouldn't find a proper match for user email. User: '********************'.
    SharePoint FoundationClaims Authentication8307CriticalAn exception occurred in ADFS claim provider when calling SPClaimProvider.FillUserKeyForEntity(): Specified method is not supported..
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (SPClaimProvider.FillUserKeyForEntity()). Execution Time=120.4741
    SharePoint FoundationClaims Authenticationaf3zpUnexpectedSTS Call Claims Saml: Problem getting output claims identity. Exception: 'System.NotSupportedException: Specified method is not supported.    at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)    at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime tokenLifeTime)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentityForRequest(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope)'.
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (SPSecurityTokenService.GetOutputClaimsIdentity()). Execution Time=121.9425
    SharePoint FoundationClaims Authenticationfo1tMonitorableSTS Call: Failed to issue new security token. Exception: System.NotSupportedException: Specified method is not supported.     at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime tokenLifeTime)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.CreateTokenCacheReferenceFromUserId(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentTokenCacheReferenceClaim(SPRequestInfo requestInfo, IClaimsIdentity identity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.AugmentOutputIdentityForRequest(SPRequestInfo requestInfo, IClaimsIdentity outputIdentity)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.GetOutputClaimsIdentity(IClaimsPrincipal principal, RequestSecurityToken request, Scope scope)     at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)     at Microsoft.SharePoint.IdentityModel.SPSecurityTokenService.Issue(IClaimsPrincipal principal, RequestSecurityToken request)
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (SPSecurityTokenService.Issue). Execution Time=125.8951
    SharePoint FoundationTopologyaeaycHigh[Forced due to logging gap, cached @ 11/14/2019 01:19:26.79, Original Level: Verbose] The SecurityTokenServiceHeaderInfo including the correlation ID was added.
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (ExecuteSecurityTokenServiceOperationCaller:http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue). Execution Time=141.6527
    SharePoint FoundationClaims Authenticationfsq7HighSPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Specified method is not supported. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.NotSupportedException: Specified method is not supported.    at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime token...).
    SharePoint FoundationClaims Authentication8306CriticalAn exception occurred when trying to issue security token: Specified method is not supported..
    SharePoint FoundationClaims Authenticationaf3xxUnexpectedClaims Saml Sign-In: Could not get local token for trusted third party token. FaultException: 'System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Specified method is not supported. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.NotSupportedException: Specified method is not supported.    at Microsoft.SharePoint.Administration.Claims.SPTrustedBackedByActiveDirectoryClaimProvider.GetUserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProvider.UserKeyForEntity(SPClaim entity)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaimForTrustedUser(IClaimsIdentity claimsIdentity, SPClaim userIdentityClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKeyClaim(IClaimsIdentity claimsIdentity, SPClaim loginClaim)     at Microsoft.SharePoint.Administration.Claims.SPClaimProviderManager.GetProviderUserKey(IClaimsIdentity claimsIdentity, String encodedIdentityClaimSuffix)     at Microsoft.SharePoint.IdentityModel.SPSessionSecurityTokenCookieValue.Initialize(IClaimsIdentity identity, RequestSecurityToken request, DateTime token...).'. Stack: '   at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr)     at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo, SPRequestSecurityTokenProperties properties)     at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForOnBehalfOfContext(Uri context, SecurityToken onBehalfOf)     at Microsoft.SharePoint.IdentityModel.SPFederationAuthenticationModule.ExchangeArgumentTrustedThirdPartySessionSecurityTokenForLocalToken(SecurityToken thirdPartyToken, SessionSecurityTokenCreatedEventArgs arguments)'.
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (SPFederationAuthenticationModule.OnSessionSecurityTokenCreated). Execution Time=143.4391
    SharePoint FoundationMonitoringb4lyHighLeaving Monitored Scope (SPFederationAuthenticationModule.OnAuthenticateRequest::WifCodeCall). Execution Time=161.2515
    SharePoint FoundationMicro Traceuls4HighMicro Trace Tags: 0 adyrv,143 b4ly,0 fsq7,0 af3xx,0 b4ly,0 b4ly

Hi ,

We are using the URL field of Link to a document content type to store the url for link in SharePoint online App development.

We get issue for storing URL with more than 255 characters. From documentation it seems that now this limit is increased to 400 characters but we get this issue for SharePoint online

Can anyone suggest me a way to store URL with more characters? we want URL field only as user should be able to redirect to that url on click of link.

Thanks,
Swati

Hi All,

I have configured Office online Server  with SharePoint 2016. It was working fine. Yesterday my system gets shut down all of sudden due to some reason. When I tried to open office documents in our SharePoint Site in browser it gives below error.

I have checked "http://servername/hosting/discovery" also, its working fine. I am unable to fine the problem where it occurred all of sudden.

I am also not logged in Site with System Account.

Please help.

Is it possible for a document to be combination of a group of other documents and update dynamically?

For instance, if I had 3 word documents each representing the chapter of a book. Is it possible to have one book document that I could open to look at all chapters at once?

==

Question is is there an impact in SP (both in prod and dev) if they apply this change?

Hello -

Our SP environment has hundreds of sites/subsites, many of which probably haven't been accessed in years.   We are in the process of cleaning up inactive sites by trying to identify which sites haven't been accessed/modified in at least 2 years.   I found the PS query below that will at least give us an idea of sites not updated in that time, as well as who the site owners are so that we can contact them on cleaning up their sites (so that we can prep to move to SP Online).

With the content db being around 400 GB, I expect this to probably run for a couple of days.   Are there any suggestions on better alternative to create a report on site owners/last accessed date etc?  

Get-SPSite -Limit All | 
  Get-SPWeb -Limit All | 
  Where { $_.LastItemModifiedDate -lt ((Get-Date).AddMonths(-24)) } |
  foreach {
    # the URL""   #blank line
    $_.url"  LastItemModifiedDate: " + $_.LastItemModifiedDate"  Web has unique permissions: " + $_.HasUniquePerm

    # the Site Collection Administrators
    " Site Collection Administrators:"
    foreach ($user in $_.SiteAdministrators)
    {      "  " + $user.DisplayName + " " + $user.UserLogin
    }

    # full control users
    " Full Control Users:"
    foreach ($user in $_.Users)
    {
       if ( $_.DoesUserHavePermissions($user,[Microsoft.SharePoint.SPBasePermissions]::FullMask) )      
       { "  " + $user.DisplayName + " " + $user.UserLogin
       }
    }
  }

Hi,

We use Sharepoint 2013 and WorkFlow Manager 1.0. The certificate for the WorkFlow Manager farm has expired.  Is there some powershell commands I can run to update the certificate?  Most forums say I must uninstall Workflow Manager and then reinstall?  If this is the only option, can you point me to an article with the steps needed?

Thanks,

Regina 

SharePoint Farm Admin

Hi,

I was able to connect to an external search service available from an external search farm (publishing farm).
Now the "Search Service Application Proxy" is available in the list of services on the farm that will consume the data from the external farm.

Should I remove local SSA if exists next to remote SSA proxy?

Now I would like to create a search result source based on an external search service (proxy) from the powershell/

Is it possible?

Thank you in advance.

After upgrading a SharePoint 2013 On-Prem farm from June 2017 CU level to the January 2018 CU level, I encountered the following exception(s) on step 9 of 10 of the first run of the Configuration Wizard:

Configuration Failed
One or more configuration tasks failed. . .
Failed to upgrade SharePoint Products.
This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: ... An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information:
Error running SQL DDL Script:                 IF  EXISTS (SELECT TOP 1 1 FROM sys.database_principals WHERE name = N'db_owner' A.... System.Data.SqlClient.SqlException (0x80131904): Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.ClientConnectionId:7454882a-1aa0-43bc-bc05-84e79ec5d989Error Number:15151,State:1,Class:16        (EventID:al2pi)
Upgrade [SPSubscriptionSettingsDatabase Name=SPI_Prod_SubscriptionSetting...] failed.        (EventID:ajxnm)
Exception: Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.        (EventID:ajxnm)
(EventID:ajxnm)
Upgrade Timer job is exiting due to exception: System.Data.SqlClient.SqlException (0x80131904): Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.

Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.

   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Running [PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures] failed with the same exception(s) at task 5 of 6:

The farm is being upgraded in the timer service process. The task is 14.71% completed.
Failed to upgrade SharePoint Products.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: The upgrade command is invalid or a failure has been encountered.
Error running SQL DDL Script: IF  EXISTS (SELECT TOP 1 1 FROM sys.database_principals WHERE name = N'db_owner' A.... System.Data.SqlClient.SqlException (0x80131904): Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.ClientConnectionId:5395f82b-1016-4eb6-a18c-a11e7958406cError Number:15151,State:1,Class:16 (EventID:al2pi)
Upgrade [SPSubscriptionSettingsDatabase Name=SPI_Prod_SubscriptionSetting...] failed.   (EventID:ajxnm)
Exception: Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.     (EventID:ajxnm)(EventID:ajxnm)
Upgrade Timer job is exiting due to exception: System.Data.SqlClient.SqlException (0x80131904): Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner', because it does not exist or you do not have permission.Cannot alter the role 'db_owner',because it does not exist or you do not have permission.

Research suggested a few possibilities.

Some forum posts showed some people who encountered this type of error could get past it by opening SQL Management Studio, drilling down to the subscription settings service database > drilling into the security folder of that database > drilling further down to Users > finding and right-clicking the account that you're using to run the ConfigWiz in the list of users > Properties > Owned Schemas > select "db_owner" and click OK.  But that didn't help me. I did it several times and ran into the exact same exceptions every time I ran psconfigUI.exe or psconfig.exe. Also, the permissions I added were stripped away every time I ran configwiz.

Two forum posts I found suggested this was related to SQL Always-On and/or Availability-Groups. I removed the subscription database from the AO AG and that didn't help either. Same exceptions. But I did not set it from full recovery mode to simple recovery mode like some suggested.  So maybe I didn't go far enough with this.