Return Code = 5 always ends up to be something to do with permissions. If you cannot figure it out, please place a call with IBM Support.
Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 12/18/2008 02:17:38 PM: > [image removed] > > Re: SQL Database Agent error > > Hizny, Michael > > to: > > ADSM-L > > 12/18/2008 02:18 PM > > Sent by: > > "ADSM: Dist Stor Manager" <[email protected]> > > Please respond to "ADSM: Dist Stor Manager" > > Del, > > We are using mixed authentication. My id has the sysadmin role on > the database. I also tried using integrated security with the sa > userid and had the same result. > > Thanks, > Mike > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On > Behalf Of Del Hoobler > Sent: Thursday, December 18, 2008 11:08 AM > To: [email protected] > Subject: Re: [ADSM-L] SQL Database Agent error > > Are you using SQL Server Windows mixed authentication or SQL Server > authentication? > Has your userid been granted "sysadmin" role to the SQL Server? > In the User's Guide, the "security" is documented like this: > > ------------------- > Security > Data Protection for SQL requires certain settings in order to perform > operations in a secure environment. > > Windows administrator authority is required for installation. Data > Protection for SQL must be registered to the Tivoli Storage Manager server > and the appropriate node name and password must be used when connecting to > the Tivoli Storage Manager server. In addition, standard Tivoli Storage > Manager security requirements apply to Data Protection for SQL. > > > Three options are provided when specifying SQL Server logon information: > > Accept the default sa account and blank password. > Use SQL user ID security and specify both the SQL user name and password. > With SQL user ID security, the SQL Server administrator provides the logon > ID and the password that provides access to the SQL Server. > Use a trusted connection and let Windows authenticate the logon. > > Note: The SQL logon user or Windows user name must be added to the SQL > Server SYSADMIN fixed server role before it can be used by Data Protection > for SQL. > ------------------ > > > Thanks, > > Del > > ---------------------------------------------------- > > "ADSM: Dist Stor Manager" <[email protected]> wrote on 12/18/2008 > 09:44:15 AM: > > > [image removed] > > > > SQL Database Agent error > > > > Hizny, Michael > > > > to: > > > > ADSM-L > > > > 12/18/2008 09:47 AM > > > > Sent by: > > > > "ADSM: Dist Stor Manager" <[email protected]> > > > > Please respond to "ADSM: Dist Stor Manager" > > > > Hi, > > > > > > > > We just installed Data Protection for SQL on a windows 2008 server > > running SQL 2005. We are getting the following error when we try a > > backup. Has anyone seen this before? > > > > Thanks, > > > > Mike > > > > > > > > Backup Failed. ACO5402E . The virtual device set could not be created. > > > > > > > > In the Event logs we get: > > > > > > > > SQLVDI:Loc=CVDS::CreateEx,Desc=Create Memory, Error Code=(5)Access is > denied. > > > > > > > > > > > > We believe that it is a permissions error, but we can’t figure out > > what permission needs to change. We are running the backup from an > > administrative account on the server and the scheduled backups run > > as a system level account. > > > > > > > > > > >
