08-22-2019 07:31 PM - edited 08-22-2019 07:33 PM
To save you troubleshooting - To save the hassle of troubleshooting i believe this is the exact same proxy issue i experienced when trying to configuring AWS S3 storage where the Backup Exec configuration setup wizard isnt smart enough to picking up the default proxy like the rest of Backup Exec is doing for updates and so forth.
Last time we got around this from this workaround https://vox.veritas.com/t5/Backup-Exec/Unable-to-connect-to-AWS-S3-Storage-BEMSDK-Failure-code-E0009... where we located the C:\Program Files\Veritas\Backup Exec\libstspiamazon.dll which is not readable and dropped in a file containting the proxy settings called "libstspiamazon.pref" to write the changes to the libstspiamazon.dll
So here is my question: there is another one for Azure called libstspiazure.dll .
Q1. How can i view and edit the libstspiazure.dll and libstspiamazon.dll to revert the settings with and without a proxy?
Q2. If i do the same thing as before but this time creating a libstspiazure.pref . Will using the same details it work with the azure file? or will the details within the .pref file need to be slightly different ? For instance should it start with AMZ or something else?
08-22-2019 09:47 PM - edited 08-23-2019 01:01 AM
for azure proxy is not supported
(corrected the above link)
08-23-2019 12:47 AM
Here is the public link to the article that Gurvinder mentioned: