Backup exec server service not starting. exe --genidentity. Error Message. Execute the following command : 4. However we keep having problem in the upgrading process. If this is selected without a central administration server present in the environment then the Installation will complete but the Backup Exec Server Service will fail to start. Start the service SQL Server (BKUPEXEC) 3. Opening up BEutility. backup exec would not start. Start the Backup Exec Services. Sep 23, 2021 · Backup Exec services don't start automatically after the backup exec server is rebooted, even though the startup type is set to Automatic. I try to restart the service using services. Tried rebooting but did not solve the problem. exe, version 12. Solution. 5 and 2010 R3 and have had the same problem shortly after installation. and (7001) "The Backup Exec Job Engine service depends on the Backup Exec Server service which failed to start because of the following error: Been running Backup Exec 9. 5). Permission issue querying the status of the Windows Operating System "server" service. In Services: Backup Exec Job Engine NOT starting Backup Exec Server is Starting (state is not changing Backup Exec Server is Starting (as above) other related Backup services HAVE started ok. Does anyone know why this is happening? An exception occured starting remoting services for Backup Exec Management Service: System. Event ID 7034. This is Backup Exec 11. x or 12. Same when i run the environment check. Rebooted last Wednesday. Everything was working fine until suddenly the services now fails to start. Add a Windows Scheduled Task to start the file BESTART. 183, time stamp 0x4d5ab262, faulting module kernel32. Launch the Backup Exec Utility by running the BEUtility. The two services that will not start are the 'Backup Exec Server' service and the 'Job Engine' service. Eventid 26: Application popup: : \SystemRoot\system32\DRIVERS\VirtFile. Select May 5, 2011 · Greetings everyone - Operating System: Server 2008 32-bit Backup Exec Version: 2010R2 Recently I’ve run into a problem on my sole Server 2008 (nonR2) server. log . Message: The Backup Exec Server service on Local Computer started and then stopped. msc and I get the following: The Backup Exec Server service on Local Computer Started and the stopped. This started out of the blue with nothing else out of the ordinary. My Backup Exec Server service stopped at 10:06 this morning. I can't stop it because all greyed out. pls see the below logs for those 3 services. msc the following services are not running: Backup Exec Agent Browser; Backup Exec Job Engine; Backup Exec Server; Attempting to start the services through Backup Exec console or beutility gives a “The dependency service or group failed to start” error. The MMS remain as BE12. After reboot of Windows 2012 server, starting the backup exec 15 manager resulted in this error:The BackupExec Management Service was unable to startThe Logging into the server and then into Backup Exec 2012, I find that I am unable to connect to the Backup Exec Server. The in Feb 23, 2005 · Before today we have had no trouble using Version 10 of Backup exec until this morning. Here is something you might want to try. When restarted Backup Exec Server service stuck as "starting". This is usually in C:\program files\Symantec\Backup Exec. dll, version 6. 12. Jul 1, 2014 · Looking in services. I used Veritas update to install all the patches this morning and now after a reboot a Message appears at login that a service has failed to start. Refer to the database recovery log for details. Change Directory to Backup Exec Install Path 3. I have found the following in the Event Log. after the installation i booted the server, but the service "backup exec server" did not start or hang in starting state. The messages we get in Eventlog is these: (7022) "The Backup Exec Server service hung on starting". Mar 11, 2019 · 6. In the middle pane of Backup Exec Utility, expand Known Computers > All Media Servers. Since october, the program was running ok, but sudently the situation changed. Note: Postgresql service should be running while the above command is being executed. Kindly advise. Restart the computer, and then start Backup Exec. Solution Sometimes, after a version upgrade or a server migration, the services do not start properly and remain starting. 1 in NetBackup 02-03-2023 May 8, 2023 · For account security, your password must meet the following criteria: At least ten (10) characters, A lowercase letter, An uppercase letter, A number, A symbol, Does not include your username, Is not any of your last 4 passwords. I can connect to it using SQL's mgmt console and i am able to see the database (BEDB) created by BE 2012 and the user account that i used to run the all BE service is assigned with sysadmin role in my SQL 2k8 R2. UMI Code: V-379-58068. I set up a brand new Virtual Machine in VMWare so I could test Backup Exec 2012. 3) First start the SQL Server service, then Device&Media service, then Server service followed by Job Engine and Agent Browser. I ran sgmon. Reboot every few weeks to apply windows updates. 0" from the install media, one of the results include a section called Windows Server Service Check - FAILED. 0 on a Win 2003 standard server all of the services will not start. May 16, 2015 · Hi all, I am really having bad experience with Symantec backup exec. exe and running a repair of the BEDB. It has done this 49 time(s). Dec 28, 2020 · Storage. . I did some modification in dns and ip system due to some new requirements. Or. Edit the newly After upgrading version 16 to 20. I though it was an activation issue, I got into We have some servers where Backup Exec job engine is not able to start automatically on reboot. 2. Logon as the local Initial Backup Exec installation. Refer to the database recovery log for details" occurs. 2) Configure the Backup Exec Device & Media, Server Service, Job Engine & Agent Browser service with the domain admin account. The following services do not start automatically, I have to start them manaully otherwise the networker will not work. I go this message: The Backup Exec Server serivce on local computer started and then stopped. Apr 4, 2018 · This issue occurs when the Backup Exec service(s) is starting up with a user account and the password has been changed on the domain but was not updated on Backup Exec. When trying to start the 'Backup Exec Server' service through the services panel it creates this event in the applications event viewer: Feb 9, 2021 · The Backup Exec Remote Agent for Windows service depends on the Backup Exec Lockdown Server service which failed to start because of the following error: After starting, the service hung in a start-pending state. same problem. Ensure that the specified database is running, and then try starting the service again. Hi, Open up BEutility, right-click the name of your server and choose the option to change the service account details. Dec 5, 2017 · The Backup Exec Device & Media Service does not start after a server name change or a Backup Exec version upgrade. "The Windows Server service was not started. 5. I put the CD in. Jun 30, 2021 · 2. Start this service before continuing with the installation of Backup Exec. Lately the MMS failed to work with CASO and Symantec support advise us to upgrade the MMS to BE14. I swapped out the NIC and Windows would not boot. 2213. " UDL connectivity test with the Backup Exec Database also fails with "Cannot generate SSPI context" Dec 5, 2017 · Trying to start the Backup Exec Device and Media service fails with "The Backup Exec Device and Media Service could not start because the database recovery has failed. BAT after a server reboot. 0 on a 2003 machine and everytime that the machine has to reboot, the server service will not start. in NetBackup 08-11-2023 Backupexec Device and media service failed to start. The Service Control Manager (SCM) uses default time-out value of 30 seconds for service communication. Mar 31, 2017 · The Backup Exec Server service will no longer start, when it attempts to start it automatically fails and the following event logs get generated; Faulting application beserver. However, the services can be started manually. 0. Oct 16, 2007 · The event viewer wasn't helpful either. Cause. Please use the SQL Management Tools to determine if the BKUPEXEC BEDB SQL database is in Single User mode. It started when the NIC was not working properly and the activation had apparently timed out (thought I activated it but apparently not). Hi, after i have install the Backup Exec 2010 R3 64bit update on my Windows Server 2008 R2 operating system, the Backup Exec Device and media service not Feb 9, 2022 · The Backup Exec service 'Backup Exec Remote Agent for Windows Systems' cannot start because there is a pending request from the Backup Exec installation to restart the computer. 1 the Backup Exec server service won't start. The Backups will run and then they'll just stop with certain services no longer being able to start. When running the "Backup Exec Environment Check 2. exe from X:\Program Files\Symantec\Backup Exec\ (where X: represents the drive where Backup Exec is installed) 4. Solution . I restarted the server: no change. See attached screen shot. Nov 22, 2023 · Managed Backup Exec Server checkbox should not be selected for a Standalone Backup Exec Installation. 7. Restart the Backup Exec Server service. From there, go into the \Data folder. Jan 26, 2012 · For account security, your password must meet the following criteria: At least ten (10) characters, A lowercase letter, An uppercase letter, A number, A symbol, Does not include your username, Is not any of your last 4 passwords. 6 and Netbackup 9. Stop all Backup Exec services. An attempt to enter a username and password to connect to the server yields: Dec 30, 2011 · Hello, I've used 2 different versions of Backup Exec on a SBS 2008 Server. It said: The Backup Exec Server service terminated unexpectedly. If issue still persist, Verify Job log path in rejistry - which is by default (C:\Program Files\Symantec\Backup Exec\Data) Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. There are 3 services which fails to start. 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. 1 Authorization Service wont start now after server went down. 2 Master Server in NetBackup 10-27-2021 The SQL Server Service is Running Fine it is a standalone full version of SQL SErver,. (Figure 3) Figure 3 6. Following a server reboot, some Backup Exec services are not starting up despite being set to Automatic startup. Over the last 6 weeks, when I reboot my SBS 2003 server, my Backup Exec service does not start automatically. 1. Some serivces stopped automatically if they have no work to do, for example the Performance logs and alerts service Jul 28, 2022 · For account security, your password must meet the following criteria: At least ten (10) characters, A lowercase letter, An uppercase letter, A number, A symbol, Does not include your username, Is not any of your last 4 passwords. I installed some verison 10 and some with server service did not start. 1 on our Windows Server 2003 R2 successfully for many years. Start the Backup Exec Deduplication Engine Service. Event Id 26: Application popup: : \SystemRoot\system32\DRIVERS\VirtFile. Sep 4, 2020 · "The Backup Exec Device and Media Service could not start because the database recovery has failed. 2 - Unable to backup to tape, disk does work in Backup Exec 08-08-2023 System-Root Full - 5230 Appliance in Appliances 12-21-2022 Cannot make Virtual Netbackup Appliance 3. in Backup Exec 06-28-2023 RHEL 8. Nov 22, 2018 · By default, the service name for the instance is "SQL Server (BKUPEXEC)" The user specified to start the Backup Exec services does not have the appropriate rights Oct 19, 2021 · The Windows Server Service was not started. Aug 12, 2005 · After installing Backup Exec 10. I upgraded my CASO to from BE 12 to BE 14. I have to run checkdisc to get the system back up. 1. Running a repair of the application through Add/Remove Programs. Stop all Backup Exec services . Dec 15, 2009 · Hi, i'm going to resume the problem. 19623, time stamp 0x56ec4631, exception code 0xe06d7363, fault offset The server service is complaining about initializing your security configuration. Case A: This issue can occur if the Backup Exec Service Account (BESA) is not able to connect to the SQL instance that hosts the Backup Exec Database (BEDatabase). It runs a bit then the error: The Server service was not started. Here is my recommendation, 1) If the server installed MSOffice/Outlook, make sure it has a default profile configured. This user can be granted access rights to the Backup Exec SQL Database by following these instructions: 1. Jan 11, 2016 · 5. i made a deinstallation and an new installation. If I tr Sep 27, 2005 · I have installed Veritas Backup Exec version 10. The event log reads as follow "The Backup Exec Server service did not start. x (I'm typing this from home and can't recall which versionI want to say 12. Installed Windows Server 2008 Standard R2, and updated it to SP1. Article: 100022440 Mar 30, 2018 · The Backup Exec Server service will not start if the Backup Exec SQL database (BEDB) is in Single User Mode. The above should create that file in \Storage\Data folder. " Feb 9, 2021 · The Backup Exec Remote Agent for Windows service depends on the Backup Exec Lockdown Server service which failed to start because of the following error: After starting, the service hung in a start-pending state. Jun 6, 2011 · We have installed Symantec BAckup Exec 2010 R2 on Windows 2008 Server. Dec 4, 2017 · Solution. This has happened twice now, once with the services set to log on as the BackupExec service account and once as Local System. Put in your username: DOMAIN\user_name and the password and let BEutility reset this. exe and collected the attached log, but I can't discern from it what could be the cause; even when compared to another sgmon log from a working server it wasn't clear what the problem was. Starting Backup E Apr 12, 2016 · The install looks to have gone through fine and the updates ran through without issue, after a restart i noticed that some of the backup exec services were not running, Backup Exec Server, Backup Exec Agent Browser, Backup Exec Job Engine & Backup Exec Management Service. I've installed backupexec 2010 trial on my server, with an appropriately-privileged AD account, but get errors when starting the required services from the login page: Processing services Start Stop any running BE service and rename the existing msgq files (Found in \Program Files\Symantec\Backup Exec\Data) and then restart all services. I can uninstall, clean up the 'leftovers' and rei Aug 28, 2007 · Windows Netbackup 9. Apr 15, 2016 · Backup Exec 22. sys failed to load. Some services stop automatically if they are not in use by other services or programs. AI model training drives up demand for high-bandwidth memory. After changing the NDMP port on a remote server, ensure that the firewall on the remote server allows both inbound and outbound access to the new port. Solution Oct 31, 2019 · The Backup Exec Device and Media Service will not start and "Event id 58068, the database recovery has failed. -----Event ID: 7023 Description: The Backup Exec Device & Media Service service terminated with the following error: The database specified does not exist. Sep 1, 2008 · Backup Exec 12D . ServiceModel. May 1, 2015 · Hi Guys, I am having an issue where my Backup Exsec Management Service is not starting. If this is a remote database, also ensure that the firewall is properly Jan 14, 2021 · NOTE: Backup Exec for remote agent requires the NDMP port on the Backup Exec server and the one used by the Backup Exec Remote Agent on the remote server should be the same. Developed over a decade ago, high-bandwidth memory is experiencing a sharp uptick in popularity due to the demand for high-end After I change to have all services run on local, I am still unable to start Backup Exec Server. Propmted to Login, and when I do so, Veritas respponds by telling me that Backup Exec Server service is not responding. I let it auto-run, in the hta i click Start the Backup Exec Installation. Jan 31, 2014 · The Backup Exec Server service terminated unexpectedly. This can also happen if one of the passwords of Backup Exec services has been changed for no apparent reason. Sart this service before continuing with the installation of Backup Exec. 1) Logon to the server as the Backup Exec service account and perform the install or upgrade. ", and the remote Backup Exec Database (BEDB) is detached on the SQL server. I ran a repair install and when it starts up I get the following message in the even viewer. TXT and place it in \Program Files\Symantec\Backup Exec\RAWS. Aug 13, 2015 · * By default, the dbrecover log is located here: C:\Program Files\Veritas\Backup Exec\Logs\dbrecover. AddressAlreadyInUseExce Nov 22, 2023 · Connection String = "DRIVER=SQL Server;SERVER=Server Name\BkupExec;DATABASE=BEDB;App=BEWS PVL" The Backup Exec Device and Media Service could not connect to the specified database. 5502. Create BESTART. 6002. Dec 7, 2017 · This can occur if the server has an excessive amount of startup activity that delays the service from starting within the Windows Service timeout period. Mar 8, 2005 · Hi Hotshots, Not sure if this is the same. Jul 21, 2024 · Hello, i installed backup exec 2010 on a windows server 2008 r2. Go into the Backup Exec install directory. Hello, My server had a bad hard drive in a RAID5 Array. If the server service still fails to start, rerun the -console command. Start the SQL Server (BKUPEXEC) service. Stop all of the Backup Exec services. Had to change the SQL server (BKUPEXEC) service to log on as the Local System account and had to reboot after the change (for some reason it did not work just changing it and trying to start the service). I've done Repair in Add Programs, then reboot server. Jun 15, 2009 · Hi guys, I have a problem with the backup server when I reboot the server. Some of the services have stopped, including Backup Exec Server. The service in question is Backup exec Server service. Look in Services and confirm the user name that is specified for the Backup Exec Server service. spoold. Before starting the SQL SERVER (BKUPEXEC) service remove the "READ-ONLY" attribute from the database and log files that were just renamed. Also unable to start the application. It has done this 6 time(s). psjhykxcyzucohilergadnmxawotujvaibdmhhjfssuubwlgoolg
