Sharepoint 2013 Sorry

• 
• Updated engagement Oct 07, 2019

• twenty.9k
• 1

In this web log we will learn that how to fix "Lamentable, something went incorrect. There was an exception in the Database. Please retry your operation and if the trouble persists, contact an ambassador" in SharePoint search.

Introduction

Nosotros don't know when what types of issue will occur in the SharePoint server. Everything is working fine but all all of a sudden some functionality breaks - this is a common behavior in the SharePointing world. As an example, we tin can give, "Search service" and "User Profile Service". Here I will explain about one of the uncertain incidents nosotros have seen in our server just in the recent past - all of a sudden nosotros SharePoint search stopped working, we did all traditional ways of troubleshooting but nothings piece of work, finally found a solution which I will explain here. I idea of sharing this with the community so that others might be benefitted. And I believe troubleshooting in SharePoint is i of the major skills where SharePointers struggle to deal with the uncertain mistake.

All of a sudden, when our SharePoint 2016 search is stopped working. From the browser we got the below error:

ULS log written report from front end terminate server:

SearchServiceApplicationProxy:: I sUrlMappingCachedWithHash--Error occured: System.ServiceModel.FaultException`one[System.ServiceModel.ExceptionDetail]: There was an exception in the Database. Please retry your performance and if the problem presists, contact an administrator. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=truthful, whose value is: Microsoft.Office.Server.Search.Query.Pipeline.SearchObjectDatabaseException: There was an exception in the Database. Please retry your operation and if the problem presists, contact an ambassador.

at Microsoft.Function.Server.Search.Query.Pipeline.QueryPipelineErrorHandler.TranslateSqlException(SqlException ex)

at Microsoft.Function.Server.Search.Query.UrlMapping.UrlMappingDatabaseManager.GetUrlMap(Tuple`3 fundamental)

at Microsoft.Part.Server.Search.Administration.SearchServiceApplication.IsUrlMappingCachedInternal(Guid subscriptionId, SPUrlZone zone, String siteCollectionHash)

at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.IsUrlMappingCachedWithHash(Guid subscriptionId, SPUrlZone zone, String siteCollectionHash)

at SyncInvokeIsUrlMappingCachedWithHash(Object , Object[] , Object[] )

at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object case, Object[] inputs,...).

ULS log report from application with search server:

System.Data.SqlClient.SqlException (0x80131904): Procedure or part proc_MSS_GetUrlMapping has besides many arguments specified.

at Organisation.Information.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

at Organization.Data.SqlClient.SqlDataReader.get_MetaData()

at Arrangement.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)

at System.Information.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)

at Arrangement.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Cord method, TaskCompletionSource`one completion, Int32 timeout, Task& job, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)

at System.Information.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

at Arrangement.Information.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)

at Microsoft.Office.Server.Data.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock) ClientConnectionId:92965ffb-2fb0-4b24-8915-6d20c50568a1 Error Number:8144,Country:two,Grade:sixteen

Analysis (solution):

Run the SharePoint Configuration wizard in Application with search server successfully, and then the search starts working as normal.

Notes:

1. To be on safer side, before running the SharePoint Configuration sorcerer nosotros must have following backups in the server:

• Accept server snapshot or epitome backup of all servers(including the SQL server) in the farm.
• Take all service awarding database backup.
• Have all content database fill-in.
• Take SharePoint_Config database backup.

2. Need to remove the "WSS_UsageApplication" database from availbiltiy group:

If you accept an availability group in identify in the SQL, we need to remove the "WSS_UsageApplication" database (logging database) from availbiltiy grouping otherwise while running the SharePoint configuration wizard volition get an mistake and will non exist able to complete the magician running successfully. And after successfully running the wizard we need to add dorsum the "WSS_UsageApplication" database back to the availability grouping.

Summary

Thus, in this blog nosotros have learned virtually how to fix the mistake "Sorry, something went wrong. There was an exception in the Database. Delight retry your functioning and if the problem persists, contact an administrator" in SharePoint 2016 search.

wilsonourre1966.blogspot.com

Source: https://www.c-sharpcorner.com/blogs/fix-sorry-something-went-wrong-there-was-an-exception-in-the-database-in-sharepoint-search

Share this post