Search Engine: Elastic

Article ID: 131910, created on Dec 13, 2017, last review on Dec 18, 2017

  • Applies to:
  • Operations Automation 5.5

Symptoms

Hosted Exchange tasks fail on requests to WPE. The following output is registered in the tasks:

Provisioning request failed. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Type: System.Data.SqlClient.SqlException.

Inner exception(s):
-------------------
Logon Failure: The target account name is incorrect
Type: System.ComponentModel.Win32Exception.

The following error can be found in wpe.log:

ERROR   2017-12-13 14:52:50 (2208/2796): Error System.Reflection.TargetInvocationException will be thrown as SOAPException.
ERROR   2017-12-13 14:52:50 (2208/1880): -- Error: Exception has been thrown by the target of an invocation.(System.Reflection.TargetInvocationException)
...
        -- Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(System.Data.SqlClient.SqlException)
...
                -- Error: Logon Failure: The target account name is incorrect(System.ComponentModel.Win32Exception)

Cause

There is an issue with the SQL server cluster, which is running WPE database. The following errors can be found in the Event Viewer of the WPEDB server:

EventID 1069:

Cluster resource 'SQL Network Name (wpesql)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.


EventID 1027:

Cluster network name resource 'SQL Network Name (wpesql)' cannot be brought online. The computer object associated with the resource could not be updated in domain 'cloud.local' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.

The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.


The cluster identity 'WPESQLCL$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Resolution

Please contact Microsoft Technical Support in order to resolve the issue with the SQL cluster.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF