Browse or backup of remote SQL server instance fails with 0xe000848c - Unable to attach to a resource

Problem

The agent backup of a remote SQL instance may fail with error shown below.  Browsing the backup selections for the backup job and attempting to expand the SQL instance to show its databases will also result in an error.

Error Message

For backup the error message is:
V-79-57344-33938 - Snapshot Technology: Initialization failure on: "SQLSVRNAME\MSSQLSERVER". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot technology error (0xE0008492): Database Query Failure. See the job log for details.

For browse the error message is:
Browse Failure
Failure to browse 'SQLSERVERNAME'
Microsoft SQL Server does not appear to be running or network connections
are preventing access to it



The debug of the backup from the SQL server will show:
[0868] 2017-07-11T12:41:02.374 [fsys\sql2] - SQL_ATTACH called
[0868] 2017-07-11T12:41:02.382 [fsys\sql2] - ListenerCacheStart
[0868] 2017-07-11T12:41:02.382 [fsys\sql2] - FindListener MSSQLSERVER
[0868] 2017-07-11T12:41:02.382 [fsys\sql2] - ListenerCacheStop
[0868] 2017-07-11T12:41:02.383 [fsys\sql2] - attempting attach to: MSSQLSERVER
[0868] 2017-07-11T12:41:34.245 [fsys\sql2] - SQL Error GUID: 3f77c30
[0868] 2017-07-11T12:41:34.245 [fsys\sql2] - SQL Error Source: Microsoft OLE DB Provider for SQL Server
[0868] 2017-07-11T12:41:34.245 [fsys\sql2] - SQL Error Description: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
[0868] 2017-07-11T12:41:34.245 [fsys\sql2] - SQL Error State: 08001
[0868] 2017-07-11T12:41:34.246 [fsys\sql2] - SQL Error Number: 18
[0868] 2017-07-11T12:41:34.246 [fsys\sql2] - SQL2_Connect failed.
[0868] 2017-07-11T12:41:34.246 [fsys\sql2] - SQL_ATTACH failed. calling detach for cleanup

Cause

The Backup Exec SQL agent relies on an OLE DB connection for SQL server.  When encryption is enforced for the OLE connection, Backup Exec may not be able to connect to SQL.  A quick test to determine if the OLE connection is working is running a User Data Link (UDL) test (see related articles). Note that the connections made for Backup Exec for browse and backup of SQL are always made locally on the SQL server. 

There are a couple of security settings for SQL that can cause these symptoms, see below.

Solution

1) In the SQL Server Client Network utility, Cliconfig.exe, typically located in c:\windows\system32, uncheck 'Force protocol encryption'.



2) If Transport Layer Security (TLS) is desired for SQL enable TLS version 1.0
3) If versions of TLS other than 1.0 are in use and TLS 1.0 is disabled, the 'System cryptographay: Use FIPS compliant algorithms for encryption, hashing, and signing' policy can be enabled to allow TLS 1.0 connection.