Access is Denied writing bak file to another disk

FRR wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.
First off, don't use a drive mapping (i.e. F, that just adds
complexity - backup straight to the UNC path \\servername\LNCENTER...
Second, SQL running under a local account won't have access to network
resources. Create a domain account for it to run under, and give that
domain account access to the network share.SQL Services should run under domain account and use UNC instead of drive
letters. The domain account that SQL runs under must have permissions to th
e
destination folder including a share if one is used.
"FRR" wrote:

> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.|||We have been writing a nightly bak file to our backup server without a
problem. We are now getting Error = 5 Access is denied.
BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
STATS = 10, NOFORMAT
It has been working fine until both servers were added to a domain. Using
either a local admin account or domain account does not correct the problem.
SQL is running under the local account. Production server is running SQL200
0
and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would b
e
greatly appreciated. Thank you.|||FRR wrote:
> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.
First off, don't use a drive mapping (i.e. F, that just adds
complexity - backup straight to the UNC path \\servername\LNCENTER...
Second, SQL running under a local account won't have access to network
resources. Create a domain account for it to run under, and give that
domain account access to the network share.|||SQL Services should run under domain account and use UNC instead of drive
letters. The domain account that SQL runs under must have permissions to th
e
destination folder including a share if one is used.
"FRR" wrote:

> We have been writing a nightly bak file to our backup server without a
> problem. We are now getting Error = 5 Access is denied.
> BACKUP DATABASE [ABCDE] TO DISK = N'F:\LNCENTER\C$\AURIOBAK Backup
> files\MP100BACK.BAK' WITH NOINIT , NOUNLOAD , NAME = N'MP100', SKIP ,
> STATS = 10, NOFORMAT
> It has been working fine until both servers were added to a domain. Using
> either a local admin account or domain account does not correct the proble
m.
> SQL is running under the local account. Production server is running SQL2
000
> and Win2000. Backup server running SQL2000 and Win 2003. Any ideas would
be
> greatly appreciated. Thank you.|||Thanks for the info.
"Jeff Ericson" wrote:
[vbcol=seagreen]
> SQL Services should run under domain account and use UNC instead of drive
> letters. The domain account that SQL runs under must have permissions to
the
> destination folder including a share if one is used.
> "FRR" wrote:
>|||SQL starts up fine with the domain account, however I am now getting error
17052 'you do not have sufficient operating system permission to open the SQ
L
ServerAgent status event.' I have a tape backup scheduled, which is runnin
g
but I can't see that from within EM - SQL Server Agent. I changed the MSSQL
Server service to run under the domain account. Is there something else I
need to do? The doomain account has local admin rights. Thank you for any
help.
"FRR" wrote:
[vbcol=seagreen]
> Thanks for the info.
> "Jeff Ericson" wrote:
>|||FRR wrote:
> SQL starts up fine with the domain account, however I am now getting error
> 17052 'you do not have sufficient operating system permission to open the
SQL
> ServerAgent status event.' I have a tape backup scheduled, which is runn
ing
> but I can't see that from within EM - SQL Server Agent. I changed the MSS
QL
> Server service to run under the domain account. Is there something else I
> need to do? The doomain account has local admin rights. Thank you for an
y
> help.
Did you also change the SQLSERVERAGENT service account? Look up
"Setting up Windows Services Accounts" in Books Online. There are
specific permissions that the domain account requires on the local
machine in order to run the services.
Tracy McKibben
MCDBA
http://www.realsqlguy.com