Amazon S3 Migrator fails connectivity test.
Article ID: 100052391
Updated On:
Description
Error Message
A pop up stating the following will appear:
"Migrator Configuration Test has failed."
"Reason: An unexpected network error occurred."
Dtrace will show the following:
84 15:16:49.362 [11160] (StorageManagement) <216> EV:M OST Streamer: [TID:2128] [Plugin] amazon: Error checking credential, HTTP code 403, server error code RequestTimeTooSkewed, The difference between the request time and the current time is too large.. Returning 2060019
85 15:16:49.362 [11160] (StorageManagement) <216> EV:M OST Streamer: [TID:2128] [Plugin] libsts opensvh() 22/02/02 15:16:49: v11_open_server failed in plugin C:\Program Files (x86)\Enterprise Vault\OST\x64\libstspiamazon.dll err 2060019
86 15:16:49.362 [11160] (StorageManagement) <216> EV:M OST Streamer: [TID:2128] OST API sts_open_server() failed with error: 2060019 - 'error occurred on network socket'.
87 15:16:49.362 [11160] (StorageManagement) <216> EV~E Event ID: 28944 The 3rd party storage system application 'OST Streamer' has logged the following message: |CStreamerObject::Init(): method failed|Reason = 0x8007003b|Description = OST API sts_open_server() failed with error: 2060019 - 'error occurred on network socket'. |
88 15:16:49.362 [11160] (StorageManagement) <216> EV:M [CMigratorToStreamerBridge::InitStreamer] Exiting with HRESULT 0x8007003b
89 15:16:49.362 [11160] (StorageManagement) <216> EV:M [CMigratorToStreamerBridge::TestConfiguration] Exiting with HRESULT 0x8007003b
The event log will show the following:
Log Name: Veritas Enterprise Vault
Source: Enterprise Vault
Date: 2/2/2022 3:17:59 PM
Event ID: 28944
Task Category: Storage Management
Level: Error
Keywords: Classic
User: N/A
Computer: evserver.evlab.local
Description:
The 3rd party storage system application 'OST Streamer' has logged the following message:
CStreamerObject::Init(): method failed
Reason = 0x8007003b
Description = OST API sts_open_server() failed with error: 2060019 - 'error occurred on network socket'.
Cause
This issue has been witnessed in Enterprise Vault 14.1.0 and 14.1.2 and due to a defect in the product.
Resolution
To resolve this issue upgrade Enterprise Vault to 14.2.
Issue/Introduction
