that is a protection issue inside of the SQL database itself. Can generally be fixed by giving administrator and system dbadmin privs in the database. i.e., connect using admin command box and do something like this: sqlcmd -S .\instancename
EXEC sp_addsrvrolemember 'NT Authority\SYSTEM', 'sysadmin';
GO
EXEC sp_addsrvrolemember 'computer\administrator', 'sysadmin';
GO