• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1273
  • Last Modified:

Failure installing backup exec on domain controller

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,

2 Solutions
Rodney BarnhardtServer AdministratorCommented:
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.
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,...so 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.
maureen99Author Commented:
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 http://msdn.microsoft.com/en-us/library/ms143504(SQL.90).aspx


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 Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Rodney BarnhardtServer AdministratorCommented:
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.
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.
maureen99Author Commented:
The backups have been running fine for a while now, thanks for your assistance.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now