TFS Backup fails on granting account permissions to folder

Question

Hi, I'm using the Sept 2010 TFS PowerTools and setting up the backup wizard. It fails at the "Grant Backup Plan Permissions" step. The log says that it failed to grant permissions to account XYZ on the backup path network location I gave.

This is the first error that occurs in the log:

[Info   @12:22:48.343] Adding machine account MYDOMAIN\TFS$ for SQL services on server tfs1
[Info   @12:22:48.347] Granting account MYDOMAIN\TFS1$ permission on folder \\SERVER\TFSBackup\TFSBackups
[Info   @12:22:48.349] System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
...
[Error  @12:22:48.352] MSSQL Server service account MYDOMAIN\TFS1$, MYDOMAIN\myuserlogin does not have the required permissions to create backups on the backup path \\SERVER\TFSBackup\TFSBackups

SQL server is configured to run under the default NetworkService account. Is this an issue as it appears to be attempting to grant the machine name permissions to the network location.

Thanks.

Answer 1

Hi,

In the account page, which account did you choose?  NetworkService ?

You can try to use a domain account.

---

Best regards,
Ruiz
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com

Answer 2

Hi,

How is this issue now?

---

Best regards,
Ruiz
MSDN Subscriber Support in Forum
If you have any feedback on our support, please contact msdnmg @ microsoft.com
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 3

Hi,

Though its running under user account only, i'm getting same error.

- Suthir

Answer 4

Hi

I did resolve the problem I had. I can't quite remember the exact details, but I did note down the following:

• I configured the backup to run under a dedicated user account (DOMAIN\TfsBackup)
• Grant access to the backup location network share to the TFS computer (i.e. DOMAIN\SERVER_NAME$) and the account that is used for the TFS backup.
• When configuring the backup job (i.e. running the wizard), I started the TFS Admin Console using an admin account rather than my usual network login.
• Don't backup SharePoint - there are known issues with the September drop of PowerTolos.

With all this, the backup worked correctly for me.

Answer 5

I have exactly the same issue.

 

Error

[ Grant Backup Plan Permissions ] Account Quad\Massimo failed to create backups using path \\Quad\m\Team Foundation Server Backup

 

The path M is shared with  full control to Everyone so I should not have issues.

I tried both with the service account and my user account.

 

Answer 6

I had the same issue too - I fixed it by changing the share name so it didn't contain spaces.

Answer 7

I had the same issue too - I fixed it by changing the share name so it didn't contain spaces.

This solved the issue for me too.

Answer 8

Ditto

Answer 9

I have the same issue. And i have some exceptions in wizard log:

 

[Info   @15:28:24.757] Granting account corp\spadmin permission on folder \\mskfs71\backup\TFS

[Info   @15:28:24.759] System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

"Grant Permissions" privilege for user who start wizard is requaried

 

---

Don't forget to vote for useful replies and/or mark answers for your questions - that helps other guys to find the answer faster.

Answer 10

I had the same issue too - I fixed it by changing the share name so it didn't contain spaces.

removing spaces from the share name solved it for me too.

Answer 11

Is this something that the Power tools team can fix?  On a side note is the source open at all so I might fix it?

Answer 12

Same here - i've been faffing around with permissions for about 1 hr thinking i was going mad and it turned out to be that the folder name cannot contain any spaces. D'oh!!!!

Answer 13

Same problem here, solved with removing spaces from the share path. Also, surrounding the path with double quotes does not help, you must remove the spaces.

Answer 14

Ok, this solves my problem, also.

Answer 15

I had the same issue too - I fixed it by changing the share name so it didn't contain spaces.

You da man!