Verify Distributed Component Object Model (dcom) settings.
Download this free guide, download our editors ransomware guide, in which youll discover the server 2012 r 2 iso full value of mature DRaaS, blockchain technology, and copy data management techniques in detecting and fighting the scourge of ransomware.
Â Verify that the Backup Exec System Recovery client is pointing to the DNS server on same domain as the share.
Sometimes Error 1053 is related to a permissions problem that keeps the database or one of the Backup Exec Services from starting.Click start (if not started) for Service status.In some cases, it can be related to a problem with the Microsoft.NET Framework.If that doesn't work, check the Application and System logs in the Event Viewer.Error Message, cause, this issue will come up if WMI is not functioning properly on the server.Select Automatic for the Startup Type field. .
Symantec Backup Exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market.You can pinpoint the problem service by opening the Service Control Manager and checking to see which service failed to start.(Please, see the related documents 'How to use dcomcnfg to configure permissions).Dcom permissions are configured on the user accounts, to allow the local and remote access, for the Symantec Backup Exec System Recovery (besr) agents.Related Articles, subscribe to this Article, manage your Subscriptions.EXE, and then click,.