Error in ULS:
02/06/2018 14:31:52.29 OWSTIMER.EXE (0x04B0) 0x0FD8 SharePoint Foundation Timer 6398 Critical The Execute method of job definition Microsoft.SharePoint.Administration.SPServiceApplicationInstanceProvisioningJobDefinition (ID 64a8d164-df91-49b2-b568-462a12a1cb71) threw an exception. More information is included below. Invalid provider type specified. 8cf6479e-5da4-5081-f6a1-6b94c53300d8

02/06/2018 14:31:52.29 OWSTIMER.EXE (0x04B0) 0x0FD8 SharePoint Foundation Timer 72ae Unexpected
 Exception stack trace:
 at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)
 at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)
 at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair()
 at System.Security.Cryptography.X509Certificates.X509Certificate2.get_PrivateKey()
 at Microsoft.SharePoint.Administration.SPCertificateProvisioningAssistant.ProvisionCertificate(String storeName, StoreLocation storeLocation, SecureString exportedCertificate, CryptoKeySecurity security)
 at Microsoft.SharePoint.Administration.SPCertificateAuthority.ProvisionCertificate(String storeName, StoreLocation storeLocation, SecureString exportedCertificate, CryptoKeySecurity security)
 at Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceApplication.ProvisionLocal(SPServiceInstance serviceInstance)
 at Microsoft.SharePoint.Administration.SPServiceApplicationInstanceProvisioningJobDefinition.Execute(Guid targetInstanceId)
 at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)
 8cf6479e-5da4-5081-f6a1-6b94c53300d8

 CERT_KEY_PROV_INFO_PROP_ID(2):
 Key Container = CertReq-8186d92c-a1ba-4a0d-8057-2c6e164e54c2
 Unique container name: 19a9eec0e1d58579ec9521356b1f3dab_7b6bef17-b3d8-4810-b027-f4271b5b8c99
 Provider = Microsoft Software Key Storage Provider
 ProviderType = 0
 Flags = 20 (32)
 CRYPT_MACHINE_KEYSET -- 20 (32)
 KeySpec = 0 -- XCN_AT_NONE

However, a working certificate will have below details:
 CERT_KEY_PROV_INFO_PROP_ID(2):
 Key Container = 27925d79f29201c6ff775267682bcdec_7b6bef17-b3d8-4810-b027-f4271b5b8c99
 Simple container name: te-1a815876-5775-40db-b18f-9829d9aead99
 Provider = Microsoft Strong Cryptographic Provider
 ProviderType = 1
 Flags = 20 (32)
 CRYPT_MACHINE_KEYSET -- 20 (32)
 KeySpec = 1 -- AT_KEYEXCHANGE

1. Export the certificate including private key to a PFX file.
2. Delete the existing certificate
3. Open an elevated PowerShell command prompt and import the PFX file using the cmdlet syntax below, specifying the AT_KEYEXCHANGE value: certutil –importpfx certfile.pfx AT_KEYEXCHANGE
4. Restart the service.

Error in fiddler POST https://<Site URL>/_vti_bin/client.svc/ProcessQuery HTTP/1.1 Date: Fri, 21 Apr 2017 18:09:41 GMT MIME-Version: 1.0 Accept: */* X-RequestForceAuthentication: true X-RequestDigest: 0xA17F63D097A8EADBA2EC36CFAF8B1F978EDEE81350DE11A167F062732783488D3DCAC1BC57C5193807679BCD4FAA1D510392C6E52C8696C5A6EF83D8F26C79D8,21 Apr 2017 18:09:40 -0000 User-Agent: Mozilla/4.0 (compatible; MS FrontPage 15.0) Host: teamdev2013.borderstates.com Accept-Language: en-us, en;q=0.1 Accept: auth/sicily X-FORMS_BASED_AUTH_ACCEPTED: T Content-Length: 773 Content-Type: text/xml X-Vermeer-Content-Type: text/xml Accept-encoding: gzip, deflate Connection: Keep-Alive Cache-Control: no-cache

Cause: This is a know issue with Workflow Manager Known Issues in Workflow Manager 1.0

Solution: Run the client application using elevated permissions and run these commands to solve the issue.

On WFM server
$sec = New-Object Microsoft.Workflow.Client.Security.WindowsSecurityConfiguration("All Users") 
$sec.WorkflowAdminGroupName = "Users" 
Set-WFScopeSecurity -ScopeUri https://<WFM server FQDN>:12290/ -SecurityConfiguration $sec

On SP server 
Register-SPWorkflowService –SPSite "https://<Site URL>/" –WorkflowHostUri "https://<WFM server FQDN>:12290/" –AllowOAuthHttp –Force

• You have an account that has permissions to administer the Business Data Connectivity Service Application
• You have an account that has permissions to administer the Secure Store Service service application

Users are unable to use the Drag and Drop functionality in SharePoint Environments.

Symptoms:

Fiddler trace indicated that there was 401 Unauthorized responses being seen during the upload requests.

Cause:

The F5 virtual server’s HTTP Profile -> “Response Chunking” was set to “unchunk”

Resolution:

The F5 virtual server’s HTTP Profile -> “Response Chunking” was set to “selective”

More information:

Response Chunking: specifies how the system handles HTTP content that is chunked by a server. The default is Selective. The behavior in each mode depends on whether the server sends chunked or unchunked responses.

For content that is chunked:

Preserve: Specifies that the system processes the HTTP content, and sends the response to the client unchanged.

Selective: Specifies that the system unchunks the HTTP content, processes the data, re-adds the chunk headers, and then sends the chunked request or response to the client. Note that for chunked content, this mode is the same as the Rechunk mode.

Unchunk: Specifies that the system removes the HTTP transfer encoding headers, removes the chunk headers, processes the HTTP content, and then sends the unchunked response to the client. The system closes the connection once it sends all data.

Rechunk: Specifies that the system unchunks the HTTP content, processes the data, re-adds the chunk headers, and then sends the chunked request or response to the client.

For content that is unchunked:

Preserve: Specifies that the system processes the HTTP content, and sends the response to the client unchanged.

Selective: Specifies that the system processes the HTTP content, and sends the response to the client unchanged.

Unchunk: Specifies that the system processes the HTTP content, and sends the response to the client unchanged.

Rechunk: Specifies that the system processes the HTTP content, adds the transfer encoding and chunk headers to the response, and then sends the chunked response to the client.

Additional Technical Details:

https://devcentral.f5.com/questions/how-to-configure-sharepoint-2013-on-bigip 

In FAST ESP user administration, you accidently enabled “This User will be authenticated by an external User Management System” for the only Admin user and now after logout can’t access ESP Admin GUI. Now the next time you try login using the same “Admin” account, you receive the below error –

“There was a problem with your login request. Please verify that the username and password is correct. If you are still unable to log in please contact your administrator. [Try again.]”

To fix this issue create “Admin” user in you AD and then finish the configuration steps given TechNet article: FAST ESP / Enable ESP Administrator to use Active Directory accounts for Authentication - https://support.microsoft.com/en-us/kb/2441205

Once you are able to login using the AD “Admin” account you can then revert back the original accidental changed.

Alternately, you can follow the below steps to “Disable ESP Administrator to use Active Directory accounts for Authentication” by modifying the VESPA DB

•Log into the vespa db 

1.  Execute the command: cd %FASTSEARCH%\rdbms\bin

2.  Execute the command: psql --username fast -p 16070 vespa (If prompted for password enter ‘fast’)

•Run the below query to view the user information

           select * from espuser;

It would show the results like this where value of “imported” column will be set to “t” for external users

vespa=# select * from espuser;

  id  | imported | name  | email |             password             |   realname    | userpreferencesid | linksid

------+----------+-------+-------+----------------------------------+---------------+-------------------+---------

1962 | f        | user  |       | 34713bd1f6da11114559900354032c6b |    |                   |

    0 | t        | admin |       | 34713bd1f6da11114559900354032c6b | Administrator |                 1 |

(2 rows)

•Run the below query to update the “imported” column value of the affected user

update espuser set imported = 'f' where name = 'admin';

It would complete like below

vespa=# update espuser set imported = 'f' where name = 'admin';

UPDATE 1

•Verify if the data in espuser table was update

select * from espuser;

It would show the results like this where value of “imported” column will be set to “f” for FAST internal users

vespa=# select * from espuser;

  id  | imported | name  | email |             password             |   realname    | userpreferencesid | linksid

------+----------+-------+-------+----------------------------------+---------------+-------------------+---------

1962 | f        | user  |       | 34713bd1f6da11114559900354032c6b |    |                   |

    0 | f        | admin |       | 34713bd1f6da11114559900354032c6b | Administrator |                 1 |

(2 rows)

•Restart the adminserver using below command

nctrl stop adminserver

nctrl start adminserver

•Login to the FAST home using the Admin account and the old password

•Once logged in using the “Admin” account, disable ESP Administrator to use Active Directory accounts for Authentication in User administration setting “This User will be authenticated by an external User Management System”

Note:- Before making the changes in Vespa DB remember that editing database might lead you to an un-supported state

Steps

• Create 2 Search service application namely “Search Service Application 1(Consuming)” and “Search Service Application 2(Publishing)”

• Create 2 web application “SSA1” and “SSA2” for 2 search center sites

SSA1 https://sp:5001/  

SSA2 https://sp:5002/

• Create 2 Enterprise search center site collection on these web applications

SSA1 site: https://sp:5001/sites/Search5001   (Consuming)

SSA1 site: https://sp:5002/sites/Search5002   (Publishing)

• Added 2 different content sources to each Search Service application as below

For Search service application 1:

1. 1. Local SharePoint resource : https://sp:5001

For Search service application 2:

1. 1. Local SharePoint resource : https://sp:5002
   2. Websites: https://onlinehelp.microsoft.com/en-in/bing/ff808487.aspx

• Perform full crawl on all the content sources in both the Search service applications
• Change the proxy associations of the 2 web applications as given below, deselect the other search service application proxy

SSA1 web application - Search Service Application 1  [default]

SSA2 web application - Search Service Application 2  [default]

• Verify if you can search and get the results on both the search center sites according to the content source added to it

https://sp:5001/sites/Search5001/Pages/results.aspx?k=site

https://sp:5002/sites/Search5002/Pages/results.aspx?k=site

• Now open Search service application 1, go to Result sources
• Add new result source with name “SSA2”

• Configure this “SSA2” result source as below

Protocol: Remote SharePoint

Remote service URL: https://sp:5002/sites/Search5002/

• Go to consuming search center site -> pages library -> Create a page  with name “SSA2”

• Now go to site setting and then Search settings -> Configure Search Navigation
• Add link -> Select the new created page “SSA2” with title “SSA2”

• Edit the existing “Everything” link as “SSA1”

• Click Ok to save and apply
• Now consuming Search center site should look like below

• Edit the search center site and edit the search result web-part query to display the results from result source created “SSA2”

• Save the webpart and then the page.
• Clicking the Search vertical links namely “SSA1” and “SSA2” will display results from corresponding search service application

Note:- You can modify the result source or the search result web part query to display the results differently for both the Search service applications in the consuming search center site

Document.docx