10-28-2015 10:43 AM
Hello everyone,
I installed Backup Exec15 in a Windows Server 2008R2, the preinstallation and the installation was Ok, it was executed with no problem, but when i tried to run Exec15, it requests the username and password, I use the local administrator account and then it displays a Message error "the backup exec database was offline" and the application cannot be executed.
I enter to the SQL Studio, and tried to restart the Database but it displays another error message in where the SQL$BACKUPEXEC service cannot be started.
Please can you help me with this?
Thanky you in advance.
Greetings!
10-28-2015 12:48 PM
Backup Exec should not be using a local admin account for the services, but rather a domain admin account (if you're running a domain). To change this, open up BEutility.exe and after right-clicking the server name, select the option to change the service account.
The rights for BE should be as per the TN below:
https://www.veritas.com/support/en_US/article.TECH184449
This might explain why you can't access the SQL server to get to the BEDB.
Thanks!
10-28-2015 04:32 PM
Hello CraigV,
Thank you for your support. I did that as you said, change the local user for a Domain Admin User, but the problem continues.
10-28-2015 06:50 PM
Go to the Windows Services, make sure that the service for the SQL instance BKUPEXEC is running as a LSA and start it. Then make sure that all the BE services are running as a domain administrator, except for the BE remote agent service which should be running as a LSA. Start all the BE services. If there are any errors, check the Windows eventlog to see what the errors are and correct them.
Once all the BE services are start, you can logon to the BE console with a domain administrator id.
10-29-2015 10:00 AM
I've done what you said, the BKUPEXEC is running as LSA and the other as Domain Administrator, but the problem continues, I've checked the event viewer and it shows this message:
10-29-2015 06:27 PM
Go to Programs and Feature and do a repair of BE. If this does not help, I would suggest that you log a support case so that the Veritas engineers can take a look at the problem
10-29-2015 10:37 PM
Try these steps -
1) Do ensure TCP/IP and Named Pipes protocols are enabled.
2) Port 50106 should be open for use by the BE Management Service
3) Follow this KB - https://www.veritas.com/support/en_US/article.TECH195492
11-16-2016 09:09 AM
Problem with Backup Exec 15 "the backup exec database was offline"
Unable to open Backup Exec console.
Backup Exec Management Service start-up in EXCEPTION mode.
Problem:
After updating product Microsoft .NET Framework 4.5.2. Update Name: KB3195363, an attempt to open the BackupExec admin console fails with error and Backup Exec Management Service start-up in EXCEPTION mode.
All the Backup Exec services are running fine on the media server “FS2”
This issue is known to be caused by a corruption in the configuration of .NET framework on the server itself and is not specifically a Backup Exec issue.
Resolution:
--Will have to uninstall the Microsoft .Net Framework 4.5.
--Need to install Microsoft .Net Framework 2.0
--Need to install Microsoft .Net Framework 3.0 then reinstall .Net Framework 4.5 again.
--Multiple reboot require.
--If this issue is not resolve, you may need to contact Microsoft for more information on this case.
11-16-2016 03:22 PM
I fixed this issue by removing .NET 4.6.1 and rolling back to 4.5.2 following this guide.
http://www.expta.com/2016/02/how-to-uninstall-net-framework-461.html
All I did was uninstall KB3102467
Rebooted then ran the .NET repair on 4.5.2 just in case. https://support.microsoft.com/en-us/kb/2698555
After final reboot I was able to log into the console.
11-21-2016 11:11 AM
Thank you so much SDTek619! Had the same issue and rolling back to 4.5.2 fixed it. I used the powershell command below instead, but your post told me what I needed to do.
wusa.exe /uninstall /KB3102467
11-25-2016 01:34 AM
Removing this KB also fixed the issue for me. Thanks :)
11-29-2016 01:02 AM
I add the same problem on a fresh install BE 15 in replacement of Arcserve on a DC. BE did not start and i was unable to remove any KB.
By changing SQL configuration to Shared Memory disable and Named pipes and TCP/IP enabled, and restart SQL and all BE services, my BE console now start and I can planify my new backup job.
Hope this can help other.
Stéphane
12-11-2016 07:00 PM
Thank you so much Stephane. i had this exact issue with a new install of Backup Exec 16. tried everything even removing all updated of .net 1 by 1 starting with the one they recomended on the first page. nothing worked. i had a snapshot as BE is on a VM Guest just so i could go back and find out what worked specifically. nothing did. that is until i came over to the second page and saw your comment.
i disabled Shared Memory and enabled named pipes restarted the services and BAM everything is working. thank you so much for sharing
12-28-2016 06:40 AM - edited 12-28-2016 06:41 AM
Backup Exec 16 - Server 2012 R2
Yes, Thank you StephB! Just as dgelw437 stated, I tried everything to do with .Net, and was still unable to login. And it was strange that all services (BE and SQL) were starting fine with no errors.
Disabling Shared Memory, and enabling Named Pipes on the SQL server network configuration worked like charm and saved me hours of having to unisntall/reinstall/reconfigure BE + SQL instances.
12-30-2016 04:59 AM
I am new to BackupExec and have the same problem but I do not know where the shared memory and name pipes setting are. Can you give me a how to instruction to find these settings.
Thanks Kim
01-03-2017 12:45 AM
Please be aware that we have been continually updating the tech article that related to issues around recent Microsoft patchs apparently causing issues with access to the Backup Exec console.
As such for our latest advice on the condition please ensure you carefully review the information and suggested solutions in:
http://www.veritas.com/docs/000116721
01-03-2017 11:04 AM
Thanks for the updated info.
01-05-2017 04:37 AM - edited 06-12-2017 05:06 AM
System: Windows 2012 R2
Software: Backup Exec 2015
I had the same issue after a clean installation. I have tested all proposed solutions. None of these solutions succeeded. I had this Problem with 4 different Instances on different Locations.
I have installed the .Net Framework -- NDP462-KB3151800-x86-x64-AllOS-ENU.exe
https://www.microsoft.com/en-US/download/details.aspx?id=53344
@Colin_Weaver .Net Framework fixing has not solved all Instance/Problem, sorry for this failed Information
This Solution is working
---> Please use Solution from @CW2 it was working on my Instances
01-05-2017 04:47 AM
@ChristianWitzke I am not sure how often you have been checked our article as it has gone through numerous updates - the latest version does indicate that 4.6.1 is the recommended solution for Windows 2012 and Windows 2012 R2
http://www.veritas.com/docs/000116721
As such we would be interested to know if you ever tried 4.6.1 and it did not fix or whether you went straight to 4.6.2 from a lower version so do not know if 4.6.1 would have fixed it.
05-08-2017 03:48 PM - edited 05-08-2017 03:50 PM
StephB has hit the work around to the issue, FYI its still a problem in Version 16.
if you go into
SQL Configuration Manger | SQL Server Network Configuration | Protocols for BKUPEXEC
Change Shared Memory from Enabled to Disabled
Change Named Pipes from Disabled to Enabled
Restart all of the services or reboot, BackupExec now works.
This aritcal needs to be update with the above info in it.