Failure installing backup exec on domain controller

Posted on 2010-08-18
Last Modified: 2013-12-05
I am trying to install backup exec 2010 on a windows 2003 sp2 domain controller.  The first time I installed it on a domain controller with the same os, it worked without a hitch.  The installation of backup exec fails with error 1603 and the symantec article directed me to install sql manually from the backup exec cd.  I am trying to to that but I am getting the following error:

Failure creating local group SQLServer2005MSSQLServerADHelperUser$<servername>

I understand that the domain controller does not have local groups and this may be the problem and after reading the following:

I have created the groups listed in AD and added the account i want to use as the service account to the groups.  I am still getting the same failure.

Can anyone please tell me how to get around this?  It really did install the first time on a machine that was a domain controller!

Thanks for any help at all,

Question by:maureen99
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 32

Accepted Solution

Rodney Barnhardt earned 250 total points
ID: 33467942
What account are you using to perform the installations? 1603 generally refers to a permissions problem. Also, where did you obtain the installation? If you downloaded it, try to download it again. I have seen issues where the download may be corrupt or incomplete.
LVL 29

Assisted Solution

pwindell earned 250 total points
ID: 33468061
You probably need to do a forced manual removal of SQL2005.  Once it is installed once it does not remove properly or cleanly and gets in the way of subsequent installations.

Check out the comments at the bottom of this article!  Never install anything on a Domain Controller that includes any version of MS SQL Server unless you enjoy reinstalling your DCs from scratch.  On DCs I add DHCP, WINS, and DNS,...that is all,...nothing else,...ever.

How to: Uninstall an Existing Instance of SQL Server (Setup)

However I have always been able to remove SQL2005 and older manually without  problems.  Use Add Remove Program first,..then do the manual method to clean up what is left behind.
I used this method below.  I used Add Remove Programs first (if it is listed there) then I used the Remove Files and Folder and the Cleanup the registry portions of the article below,..I never have had to use MSIZAP.EXE thing but it wouldn't hurt to look into that.  The article is for SQL2000 (MSDE) but it works for 2005 as well

How to manually remove a Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) instance

Backup Exec.....
Obviously I recommend installing Backup Exec on a different machine (along with the physical Tape Drive if you are using tapes).  Then just install the Agent on the DC's to be able to back them up remotely.  However I had a bunch of trouble with the Agent causing services to fail to start-up  during machine start-up on the DCs, I ditched Backup Exec completely.  I'm not saying you have to do that or that is will be that bad for you,...I'm just expressing what happened to me.

Author Comment

ID: 33469845
Well I went through the install of sql 2005 again and this time I used the domain account I added to the security groups i created instead of the local system account and the install worked.  I still haven't set up any jobs yet but it did not fail on the sql install this time.

What I did was create the following security groups in active directory based on


and then add the domain admin account and the admin account I was installing under to each group.  Then in the sql install i choose to use the admin account i put in the groups instead of the local service account and it worked fine, I hope this won't cause any problems with the backups.

thanks for your assistance,

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 33474895
This should not be a problem as long as the account that the BE services are running under is included in the SQL permission. Let us know how it goes.

Expert Comment

ID: 33480846
The simple solution to this is.

1. Run SFC /ScanNow command on the DC.
2. Update DC to latest by windows update.
3. Install SQL 2008 R2 Express edition. (Take care of all Required Prerequisites)
4. Install BE and choose to use existing SQL instance.
5. Update BE to latest.

You have not mentioned BE version but i would suggest you to go for Backup Exec 2010 R2.

Author Comment

ID: 33622303
The backups have been running fine for a while now, thanks for your assistance.

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

VM backups can be lost due to a number of reasons: accidental backup deletion, backup file corruption, disk failure, lost or stolen hardware, malicious attack, or due to some other undesired and unpredicted event. Thus, having more than one copy of …
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question