Error 1068: the dependency service or group failed to start
Today I changed all the Backup Exec services that were using the Administartor account to logon using an account that I created that is a member of Backup Operators group. Now when I try to start Device & Media, Job Engine and Backup Exec Server services, I get this 1068 error, with 7001 and 7023 error logs in Event Viewer. Did some research.... I checked these 2 issues: - Made sure the MSSQL$BKUPEXEC service was started - Checked folder permissions on the Veritas folder under Program Files I found the suggestion below but, there is no Bewinui.ini file. I did this same thing, change the service logon accounts, on a server running BE 8.6 and had no problems. Any suggestions? ----------------------------------- This error message can also occur if the Backup Exec service account password have been changed. To resolve this issue do the following: 1. If the Operating System is Windows NT4, Click on Start | Settings | Control Panel | Services or If the Operating System is Windows 2000, click on Start | Programs | Administrative Tools | Services 2. While the Backup Exec services are stopped for each Backup Exec service, type in the password and confirm the password. 3. Then Open Windows Explorer 4. Navigate the Backup Exec directory (the default directory is C: Program files/Veritas/Backup Exec/NT/ Data) to the Data sub directory. 5. Rename the Bewinui.uni file in the Data folder to Bewinui.old. 6. Close Windows Explorer and Start the Backup Exec services. Warning: As a results of renaming the Bewinui.uni file all user -defined shares will be lost. Thus, all user-defined shares will need to be re-created, all stored authentication will need to be re-entered, and all notifications will need to be re-created. ----------------------------------- ------------------------------------- Event ID: 7001 Description: The Backup Exec Server service depends on the Backup Exec Device & Media Service service which failed to start because of the following error: The database specified does not exist. -------------------------------------- ------------------------------------- Event ID: 7023 Description: The Backup Exec Device & Media Service service terminated with the following error: The database specified does not exist. -------------------------------------Solved16KViews1like3CommentsBackup FAILED: An error occurred retrieving the WMI repository..
An error occurred retrieving the WMI repository data directory. The WMI repository could not be backed up. I have been getting this error for 2 weeks now and every nights backup fails because of it, I have tried the fixes in the knowledge base and have even written a batch file to automatically rebuild the repository on the main server (on which backupexec is installed). We are using this to back up 7 servers, can someone please tell me if its a different server I should be concentrating on or is it contained to the server backup exec is installed on?? Also can someone please tell me how to get rid of this error as it doesn't seem like veritas' OR microsofts solutions work:/10KViews0likes161CommentsV-79-57344-65247 - A failure occurred reading an object.
I'm getting this error every time I backup Shadow Copy Components on a Windows 2003 server. When I search http://support.veritas.com I'm pointed to this document: http://seer.support.veritas.com/docs/265282.htm But I have never moved Event Logs to a different direction and therefor I can't make the suggested solution. Can anyone help me to solve this problem ? Thanks in advance, Jens Jönsson jcj@itf.dk8.3KViews1like33CommentsHow to Add a Tape Drive
I have an older system running Windows Server 2003 Enterprise and Symantec Backup Exec 10d. The internal tape drive (Dell DLT-VS160) has gone bad. Ihave connectedan external tape drive (Dell PowerVault 110T) to the SCSI connection on the back of the server. However, Backup Exec does not yet "see" this new tape drive. Wht must I do so that the system and Backup Exec see this tape drive and so that Backup Exec can use it? Thanks for the help.Solved8KViews1like7CommentsAlert Media is write protected but it is not.
Write protected problem Specs: w2k3 server SP2 , backupexec 10.1 SP3 rev 5629,LTO2 400Gb tapes, HP Storageworks Ultrium 448. Always used the same tape with the same drive and now all of a sudden I get the alert that my tape is write protected and that I should remove the write protect tab. Of course the write protect tab is not used. I' am able of doing an inventory but a quick erase or write to the tape results in the alert. Please can anyone tell me what is going on? Thanks!Solved7.4KViews1like13CommentsFailing backup with e000848c - Unable to attach to a resource.
I'm using BEWS 10d+SP2 to backup a local server and 3 remote servers. One of the remote servers (Win2k Server, with McAfee ePO 3.61) now refuses to backup cleanly. The job log shows the error: Network control connection is established between 10.4.187.241:3288 <--> 10.4.187.1:10000 Network data connection is established between 10.4.187.241:3292 <--> 10.4.187.1:2467 Unable to attach to NCLTW-PRS0002. V-79-57344-33932 - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. But then looking at the component parts for PRS0002's backup, it seems to succeed. I've read Document 266177, so going through the points: 1) The account is valid, and a member of local admins on the remote server. The same account is used to back up the other servers. 2) See 1) 3) The server is definitely there, and there are no suspicious errors in the Event logs. 4) Remote Agent is started, there is no firewall on the machine. I've unchecked the SQL server option, but the same error is thrown for the system state and c:. 5) I've removed and re-installed the Remote Agent. 6) The agent should be current, since it was installed from the server. Anyone any ideas? update: while typing this, I've been using VxMon on PRS0002 to see what's happening. The log file (amongst other things) shows this: first load attempt of esebcli2.dll failed: The specified module could not be found. and eventually, this dll isn't loaded. Then there's this: ERROR: CreateBSD: Couldn't find NCLTW-PRS0002 startBackup: CreateBSD() failed! I don't have an SQL agent on this server (it's only ePO; I can rebuild it if something happens) but it's never bothered it in the past...Solved7.4KViews1like3Comments