Veeam Explorer for SharePoint shows as empty while restore

We are unable to view any site/content in Veeam Explorer for SharePoint when I initiate restore, it looks empty under content DB path. We kept the screen more than an hour but no use. 

Here is the solution:

1.Please make sure there is no backup job running or wait for some time to complete all the backup jobs.
2.Stop Veeam console and Veeam services (also from the remote proxies):

• Veeam Backup for Microsoft Office 365 service (Veeam server)
• Veeam Backup Proxy for Microsoft Office 365 services. (Veeam server & remote proxies)

3.Go to Veeam Backup for Office 365 - %programdata%\Veeam\Backup365\config.xml and proxy.xml
4.Edit the config.xml in a text editor.
5.Edit the proxy.xml in a text editor.
 
Add the bold text as per examples below:
 
The config.xml for Backup365 should be like this:
<Veeam>
  <Archiver OperationTimeout="1200">
   ….
    <WCF OperationTimeout="1200" />
   ….
  </Archiver>
</Veeam>
 
The proxy.xml from Veeam server should be like this:
<Veeam>
    <Archiver OperationTimeout="1200">
      <RemoteConnection Timeout="10:00:00" />
      <WCF OperationTimeout="1200" />
       ….
  </Archiver>
</Veeam>
 
We`ll need to increase the timeout for the SharePoint explorer in order to have time to load all the items in the GUI. To do this we`ll need to modify the config.xml.
 
In order to view to config.xml, we need to enable extended logging in the SharePoint explorer. To enable extended logging, please do the following:
 
1)Open the Sharepoint explorer
2)Go to General Options -> Advanced
3)Click on "Enable extended logging"
 
After this go to C:\ProgramData\Veeam\Backup\SharePointExplorer and you`ll have the config.xml. Before we edit it please stop both VBO365 services:

• Veeam Backup for Microsoft Office 365 Service
• Veeam Backup Proxy for Microsoft Office 365 Service

 
Add the bold text as per examples below:
 
The SharePoint Explorer config.xml should look like this:
<Veeam>
<Archiver OperationTimeout="1200">
    <RemoteConnection Timeout="10:00:00" />
    <WCF OperationTimeout="1200" />        
….
 </Archiver>
</Veeam>
 
 
The proxy.xml from the remote proxy, should be like this:
<Veeam>
  <Archiver OperationTimeout="1200>
      <RemoteConnection Timeout="10:00:00" />
      <WCF OperationTimeout="1200" />
   ….
  </Archiver>
</Veeam>
 
The issue should fix now. If the issue persists, please change the value "1200" to "2400" and check again.

Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]

We recently faced backup failure for Application aware backup in Veeam for MSSQL server. The error is listed below,

Processing <VM_Name> Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data.

A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}].

Instance ID: [{41239125-29f6-4455-9bc1-32439ceebe75}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].]

Normally this is caused by NTDS writers issue and we can easily fix it by restating the below services,

before restarting, I listed 'vssadmin list writers' through cmd, I found that, writer was in failed state

Writer name: 'SqlServerWriter'

Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

Writer Instance Id: {41239125-29f6-4455-9bc1-32439ceebe75}

State: [8] Failed

Last error: Inconsistent shadow copy

So I have restarted the below services and ran above cmd  again and no error found.

COM+ Event System

Volume Shadow Copy

MSSQL VSS services.

Here backup will success after the retry.

Today, I got same error and I tried same fix, however got same error and it was surprise to me.

I checked the Log for the Veeam backup in MSSQL  server and found the below error,

                Connecting to mssql, connection string: Provider='msoledbsql';Data Source='Server_Name';Integrated Security='SSPI';Persist Security Info=False, timeout: 15

                Instance '' connection problem: Code = 0x80040e4d

         Code meaning = IDispatch error #3149

           Source = Microsoft OLE DB Driver for SQL Server

             Description = Login failed for user 'user_Name'.

We found that there were some new MSSQL instance created in this server and the service account was not added for those instance to access and backup.

Finally we provided permission to same account to newly created instances and issue got fixed.