After upgrading VBO to version1.5, out of date repository upgrade fails with an “Upgrade failed: Repository does not exist” error.
The following can be found in the proxy log files:
[Timestamp] 99 (6232) Error: Access is denied
[Timestamp] 99 (6232) Stack:
[Timestamp] 99 (6232) at Veeam.Engine.FreeSpaceController.FreeSpaceInfo.GetFreeSpaceInfo(String uncPath)
at Veeam.Archiver.Proxy.ProxyFileSystemProvider.GetFreeSpaceInfo(String path)
at Veeam.Archiver.Proxy.Proxy.ProxyFileSystemService.GetDiskInfo(String path)
at Veeam.Archiver.Proxy.Proxy.ProxyAdmin2.GetDiskInfo(String path)
at SyncInvokeGetDiskInfo(Object , Object , Object )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object inputs, Object& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
This issue occurs if the services were running under a domain account prior to the upgrade and the repository was located on an SMB share. After upgrading to v1.5, access to this share may be lost, because services in the new version run under the local system account.
Give the account running the services on your VBO server access rights to the repository ([DOMAIN\]VBOSERVERNAME$). Do not change this account for Veeam Backup for Microsoft Office 365 Service.
More information about known issues in v1.5 can be found here.
Please be aware that starting from September 2018 downloading updates will require an active contract for the corresponding product.