0

"You specified a SharePoint Web application that has not been configured to grant access to Team Foundation Server. In order to add this Web application, you must either have Farm Administrator permissions, or a farm administrator must have granted access to this deployment of Team Foundation Server."

Can anyone help me with a starting point to diagnose what the issue is here? The wizard is installing WSS 3.0 and configuring it for me. How can I set Farm Administrator permissions if WSS 3.0 doesn't exist?

The wizard only prompts me for one peice of information; a non-system account that will be used as both the TFS report reader account and the WSS 3.0 service account.

I am entering the details of a domain account that has been added to the local admnistrators group.

I have been struggling with this for hours now, trying all ways I can think of, but I still get this error every single time.

J M
  • 1,877
  • 2
  • 20
  • 32

1 Answers1

2

Make sure the account running the service is granted the rights to logon as batch job in the local security policy. That was causing me the exact same problem when installing a couple of days ago.

I_DRIVE_TOYOTA
  • 68
  • 4
  • Hmm, my server is in a domain so I'm going to have to wait for IT to do this for me it seems (as the "Add User or Group" button is inactive in local policy). I will update when I can. – J M Mar 12 '11 at 18:44
  • Actually, that's not going to be until late this evening so I'll accept your answer and re-raise if necessary later. Thanks again :). – J M Mar 12 '11 at 20:56
  • UPDATE: That was it! I owe you a drink :). Hours upon hours of pain. Thank you very much. – J M Mar 13 '11 at 11:59
  • Happy to be able to help out :D – I_DRIVE_TOYOTA Mar 13 '11 at 13:26
  • I would be very interested to hear how you worked it out? I thought I had literally scoured the installation documentation. – J M Mar 13 '11 at 14:12
  • I noticed that when trying to go to the Sharepoint Central Admin I would allways get a Error 503 Service Not Available response. I also noticed that after the Sharepoint Central Admin app pool was not running in IIS. After starting the app pool it would stop again when trying to go to central admin again. So I started to look at the IIS event logs and there it was in plain text that the account need to be able to log on as a batch job. – I_DRIVE_TOYOTA Mar 13 '11 at 15:12
  • Heh, I followed that exact same path apart from the all-important last step. I will remember to check the IIS logs the next time I see HTTP errors. Seems so obvious now. Thank you for sharing :). – J M Mar 13 '11 at 16:44