Forum Discussion
Deleted
Jun 09, 2017Provision Search on SP 2016 error: Operation is not valid due to the current state of the object. at
Hello,
I am trying to create the Sharepoint Search Services Application on a Sharepoint Server 2016. The server was configured with minrole and I selected SEARCH when installing it, however Search Service Application was not provisioned
And the detailed error when creating it, its this:
Se detectaron errores durante la configuración de la aplicación del servicio de búsqueda.
System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.SharePoint.Administration.SPDatabase.Update() at Microsoft.Office.Server.Search.Administration.SearchDatabase.BaseUpdate() at Microsoft.Office.Server.Search.Administration.SearchDatabase.CreateCleanDatabase[T](String searchApplicationName, ISearchDatabaseParameters databaseParameters) at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Create(String name, SearchQueryAndSiteSettingsService service, SPIisWebServiceApplicationPool applicationPool, SPIisWebServiceApplicationPool adminApplicationPool, ISearchDatabaseParameters adminDBParameters, ISearchDatabaseParameters searchSettingsDBParameters, IEnumerable`1 crawlStoreDBsParameters, IEnumerable`1 analyticsStoreDBsParameters, IEnumerable`1 linksStoreDBsParameters, SPPartitionOptions partitionOptions, Boolean cloudIndex) at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Create(String name, SearchQueryAndSiteSettingsService service, SPIisWebServiceApplicationPool applicationPool, SPIisWebServiceApplicationPool adminApplicationPool, ISearchDatabaseParameters adminDBParameters, ISearchDatabaseParameters searchSettingsDBParameters, IEnumerable`1 crawlStoreDBsParameters, IEnumerable`1 analyticsStoreDBsParameters, IEnumerable`1 linksStoreDBsParameters, SPPartitionOptions partitionOptions, Boolean cloudIndex) at Microsoft.Office.Server.Search.Administration.SearchService.CreateApplication(String name, ISearchDatabaseParameters adminDBParameters, ISearchDatabaseParameters searchSettingsDBParameters, IEnumerable`1 crawlStoreDBParameters, IEnumerable`1 analyticsReportingStoreDBParameters, IEnumerable`1 linksStoreDBParameters, SPIisWebServiceApplicationPool applicationPool, SPIisWebServiceApplicationPool adminApplicationPool, SPPartitionOptions partitionOptions, Boolean cloudIndex) at Microsoft.Office.Server.Search.Administration.SearchService.CreateApplicationWithDefaultTopology(String name, Boolean cloudIndex, SPIisWebServiceApplicationPool applicationPool, SPIisWebServiceApplicationPool searchAdminApplicationPool) at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.CreateSearchApp() at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication() at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
09/06/2017 16:27:32
anyone?
- Gan GanCopper Contributorany solution? I got same question, installed the last patch of sharepoint 2016. the question still appear.
- Deleted
wbaer maybe you can tag someone who can help here.?
- Nelson Estrada OquendoCopper Contributor
I want to add additional information to this error:
1. When checking on the SQL server, the search database is created, but only the main one, not the other databases.
On the ULS logs I see this:
if I check the DB server, that user is sysadmin, so I still dont understand why this is happening.
06/09/2017 15:01:11.20 OWSTIMER.EXE (0x0614) 0x117C SharePoint Foundation Database 880i High System.Data.SqlClient.SqlException (0x80131904): Cannot open database "Aplicación_del_servicio_de_búsqueda_1_DB_4e59ed0edffb4f09b3436c41ab0931bc" requested by the login. The login failed. Login failed for user 'XXXX\shbd'. at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection() ClientConnectionId:ffcec509-0fd3-4517-9eea-2d8ca28009ad Error Number:4060,State:1,Class:11 e009fa9d-9c53-40c6-ae1b-1e371b07e0a8