If possible, try backing up that instance with the SQL Enterprise manager to local disk. I have had cases where the TDP could not back up a data base, but Entprise Manager failed as well, due to some sort of lock on the DB.
> Thanks Del, > > I have checked that now, and the userid does in fact have SYSADMIN > authority. > > Sean > >>>> Del Hoobler <[EMAIL PROTECTED]> 9/13/2007 1:07 PM >>> > Sean, > > This is most likely a SQL Server permissions issue. > Make sure you have give SYSADMIN authority to the userid running > the SQL Server backup for the default instance. > > Thanks, > > Del > > ---------------------------------------------------- > > "ADSM: Dist Stor Manager" <[email protected]> wrote on 09/13/2007 > 02:45:17 PM: > >> I have a Win2k3 server with 2 instances of SQL 2005. I am unable to >> backup the default instance, but I can backup the named instance >> without error. >> >> When I attempt to backup the default, I get the error ACO5402E - >> Virtual Device Set could not be created. >> >> There is no entry in the vdi.log file on the server. And the fact >> that the named instance works, leads me to believe it is not the >> sqlvdi.dll as mentioned in some other posts regarding the Virtual >> Device Set error. >> >> Any suggestions would be greatly appreciated. >> >> > > >
