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.