http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=2895
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3244
I didn't have a problem with the reports or report server. Instead I was having a problem with tfsadaminst.exe returning a value of 1. The verbose error was:
Visual Studio 2005 Team Foundation App-Data Tier Beta 2 (English): [2] WARNING:Warning 32000. The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin\tfsadaminst.exe" /uninstall ROBZ2003 2420 TFGSS' returned non-zero value: 1.
I uninstalled ADAM and rebooted the machine. Hopefully Rob Caron will include that ADAM should be uninstalled as well before installing Team Foundation on the application Server.
Remove Encrypted Data From the Report Server Database
When I started the install once again, I get another error. I followed some directions here: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=2895.
Try the following from a command line whilst you have the error dialog up
rskeymgmt -d
Say yes to "delete all encrypted data from the report server database" question
Any other errors I received I clicked on retry.
BisSubscribe.exe Error
Now I am unable to connect to BIS Service. If I open a browser window I am able to connect just fine.
"%ProgramFiles%\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin\BisSubscribe.exe" /eventType ArtifactChangedEvent /userid RD\TFSService /Address http://ROBZ2003:8080/Currituck/BisService.asmx
The error was: Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\sdk\bin\BisSubscribe.exe" /eventType ArtifactChangedEvent /userid RD\TFSService /deliveryType Soap /Address http://ROBZ2003:8080/Currituck/BisService.asmx' returned non-zero value: 1.
Enable NTLM on W3Svc Path for ADAM to Work
I have moved on to do this as well: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3244
I remember why we do this from long time ago. This stems from our need to enable NTLM on the w3svc path for ADAM to work.
You can try to do this via adsutil script.
1> In a cmd prompt, navigate to %SystemDrive%:\InetPub\AdminScripts
2> Run "cscript adsutil.vbs get w3svc/NTAuthenticationProviders". This should return something like 'NTAuthenticationProviders : (STRING) "Negotiate,NTLM"'.
3> Set the value by doing 'cscript adsutil.vbs set w3svc/NTAuthenticationProviders “NTLM”'
(NOTE: this turns off Kerberos which may be needed by other apps. see (http://support.microsoft.com/?id=215383))
My guess is that this probably will work. At that point the setup *MAY* skip step this if it checks before running (but I don't know the exact coding behind this).
BIS Service Error (from above)
Back to the BIS Service error. As it stands the error said unable to connect when clearly I could connect from a web browser. This lead me to believe it may be an error with authentication through command line. I removed the Internet Explorer Enhanced Security Configuration for Windows 2003. For some reason after some time later it finished. We will see if I can connect using the TFS client now.
Update: The internet explorer enhanced security configuration did not correct the error. It was pretty much a shot in the dark.