The problem is mostly likely caused by SQL Server 2005. By default, members of the administrators group are no longer automatically granted administrative privileges on instances of SQL Server 2005. To grant a user administrative privileges against an instance of SQL Server 2005, you have to use the "SQL Server 2005 User Provisioning Tool for Vista" (SQLProv.exe) utility. (I know the utility says "Vista", but you have to do this even if you're running Windows Server 2003; not sure about Windows 2000 Server, as my company no longer uses the OS).
By default, SQLProv.exe is found in the folder
C:\Program Files\Microsoft SQL Server\90\Shared.
Log into the system with administrative privileges. Launch SQLProv.exe w/o any command line switches to use the GUI interface. IMPORTANT: in the upper right hand corner of the dialog, specify the username to provision in domain\username format (if you're not running on a domain, or using local machine accounts to run the Backup Exec services, then the format is machinename\username). The username specified should the username running the Backup Exec Services. If different usernames are used for different services then specify the username running the Backup Exec Device & Media Service. In the "Available privileges" list (left hand side), select the instance of SQL Server for Backup Exec and click the ">" button to move the entry into the "Privileges that will be granted to..." list (right hand side). Click OK to grant the SysAdmin privilege to the user. Afterwards, you should be able to start the Backup Exec Device & Media Service.
BTW, you'll have to do this again if you ever change the user running the Backup Exec services.
Hope this helps.
Jim St. John
CTO, BRS Computing
P.S. I did this on a server running both BE 11d and SCS 3.1. They co-exist nicely, so I don't understand why Symantec would say don't run BE and SAV on the same box.
Message Edited by jimsj on
09-27-2007 01:09 PM
