I restored all the databases using msdn document 252516 found here

http://msdn2.microsoft.com/en-us/library/ms252516.aspx

However I run into issues when I get following section of the document:

To Restore the connection strings on the Report Server

1. On the Team Foundation application-tier server, open Internet Explorer and in the address bar, type http://applicationTierServerName/reports.

I get page not found error.

When I get to the last step of the document which updates client cache for work items and requires one to goto following link:

2. In the address bar, type the following address to connect to the ClientService Web service.

http:// applicationTierServerName :8080/WorkItemTracking/v1.0/ClientService.asmx

I get "Service Unavailable" message in the browser.

Not sure whats wrong. Any idea? Any logs that I can check for issues?

Thanks

Shahab

So, you're keeping the same app tier and just moving the data tier.

Because of that, it's very confusing as to why you're getting "page not found" when you try to go to the Reports page, since your app tier's Reporting Services was presumably working fine before. Were you able to successfully create team projects before attempting this move?

Normally when you go to http://server/Reports you'll get the SQL Server Reporting Services "Home" page which will include a list of the team projects (as folders inside the Reporting services). Any chance you mistyped it? Make sure to not include the :8080 part. Also, you could check in inetmgr under the Default Web Site to see if there's a Reports subdir listed there.

For the ClientService.asmx giving "Service Unavailable", there should be an entry in the event log from when that page failed to load - fire up eventvwr and see what it says and please reply with the contents of that error.

I am in the process of rebuilding this box and will give it another shot.

I only backedup and restored the databases on the destination server. msdn doc doesnt mention moving anything else from the source server except databases. if you think otherwise please let me know.

i will let you refresh my post with the latest once I try it again.

thanks

That's correct - the conceptual level action is first moving the databases then modifying the application tier to point at the new database locations.

When you say you're rebuilding "this box" do you mean the application tier or the data tier? Are you using a dual-server setup (separate app tier and data tier) or a single server (both on the same machine)? Given that you're moving the data tier, I would assume it's a dual-server setup, but I wanted to make sure what you meant by "rebuilding this box".

In that case, you're using the wrong document. The one you're referencing is specifically for the case where:

1. you have an existing dual-server setup (separate app tier and data tier machine) that's running fine, AND
2. you want to move the data tier from the machine it's currently on to a new machine, but leave the app tier where it is.

That document is not for single-server. For single server, you have a couple of options:

1. (preferred) if the server dies (let's say it's currently called "foo"), then create a new machine also called foo, install Team Foundation there (still single server setup), then restore the databases. This is the most seamless, as the clients can connect to it by the same URL, the internal names still match, etc.
2. server "foo" died, but you want to recover onto a machine called "bar". This is effectively "restore-based move" (the fact that you're in a disaster recovery instead of a voluntary move doesn't affect the mechanics) and you can follow the regular restore-based move docs @ http://msdn2.microsoft.com/en-us/library/ms404869.aspx

Reading through these pages, I would agree that it's unclear which pages are for which type of situation, and I'll see if we can get this clarified in the docs.

Thanks!

I've contacted our docs lead and we're at least going to modify that page to make it clear that it applies to dual-server and not single server. We're still discussing the best ways to say "here are the pages that describe single server and here are the pages that describe dual server" since there's some overlap (and things may get more complicated in the future), but we appreciate the feedback that the docs as-is certainly aren't clear about which setups they apply to.

Thanks!