Hi all,

I've now worked with the source control part for quite a while in the Beta 3 refresh version of TFS. Now we're upgrading to a released version and want to restore our work on new HW. Both the Beta installation and the new released version are single-server installations that belongs to the same domain.

I've followed the instructions 'How to: Move Your TFS from one HW configuration to another'. Here's the link:

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

1. The first problem I get into is when I move the service accounts using command:

tfsadminutil ChangeAccount domain\tfsservice domain\tfsservice

I'll get messages that changes were made to application pools 'TFS AppPool', 'TFSWSS' and 'TFSWSSADMIN', but after that a message 'ERROR: Could not access database' appears. I use the same domain acounts as in the Beta installation.

2. The next problem occurres when I perform the 'Process' method on 'dbo._WarehouseConfig' database. Following errors appears:

- Errors in the high-level relational engine. The data source view does not contain a definition for the '__ID' column in the 'Load_x0020_Test_x0020_Transaction_x0020_Dimension' table or view.
- Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Load Test Transaction Dimension', Name of 'Load Test Transaction Dimension' was being processed.
- Errors in the OLAP storage engine: An error occurred while the 'Load Test Transaction Dimension' attribute of the 'Load Test Transaction Dimension' dimension from the 'TFSWarehouse' database was being processed.

3. The third problem I get is when trying to access the 'ClientService.asmx' using:

http://localhost:8080/workitemtracking/v1.0/clientservice.asmx

It returns the error:

------
The XML page cannot be displayed

Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.

Invalid at the top level of the document. Error processing resource 'http://localhost:8080/workitemtracking/v1.0/clientserv...

TF10216: Team Foundation services are currently unavailable. Try again later. If the problem persists, contact your Team Fou...
----

I would really appreciate if anyone could give any input regarding these problems!

/Hansi

It's unclear to me - are you trying to upgrade and move hardware at the same time? I don't believe we support a combination upgrade+move.The best approach is:

1. Make full backups (of course!) of your Beta3Refresh server
2. Upgrade from B3R from RTM on the same server - the upgrade guide is located at http://go.microsoft.com/fwlink/?LinkID=60341
3. Verify the upgrade, kick the tires, make sure things seem ok
4. Make separate backups of this post-upgrade server
5. Use the "restore-based move" (as you already linked to)

If you follow these steps, we should be able to at least differentiate whether you're having an upgrade problem or a move problem.

Thanks for your answer. The fact is that I realized my mistake about an hour after I posted my question. As you stated I was trying to do both an upgrade and move at the same time.

Now when I'm upgrading the B3R installation I still get into some trouble when I use the TFSUpgradeRTM tool. I get an unexpected error that tells me that a 'domain\account' does not exist in the database. The utility report it as a fatal error and quits.

The utiltity did not report any problem when used with the /verify switch. Any ideas about this problem?

/Hansi

Can you include the full error, and ideally the few lines of the log/output before it? Hopefully that'll give enough context to figure out what's breaking here.

Thanks!

Here's the log file content from the TFSUpgradeRTM run that failed:

I've just replaced some specifics from our environment. The server and domain names are replaced with xxx and yyy respectively.

--- logfile content ---

Beginning upgrade from Beta3 to RTM
DB ServerName : xxx.yyy.se
Log File : TFSUpgradeRTM-632960034170683073.txt

Connecting to SQL Server xxx.yyy.se
Success
Verify if core team foundation databases exist
Success
Fetching Server location for WorkItemAttachments
Found - XXX
Fetching Server location for Warehouse
Found - XXX
Verifying connection to WIT Attachment server - XXX
Success
Verifying connection to Warehouse server
Success
Verifying connection to OLAP Server
Success
Verifying if WI Attachments DB exist on XXX
Success
Fetching Report Server location
Found - http://XXX/ReportServer/ReportService.asmx
Verifying if TFSIntegration DB is RC or greater
Verifying if TFSIntegration DB is Beta3
Success
Verifying if TFSWorkItemTracking DB is Beta3
Success
Verifying if TFSWorkItemTrackingAttachments DB is Beta3
Success
Verifying if TFSBuild DB is Beta3
Success
Verifying if TFSVersionControl DB is Beta3
Success
Verify WIT DB for reference name incompatibility
Success
Verify for CMMI Field name clash
Success
Checking pending branches and merges.
Success
Verification of DB's complete
Attempting to delete reports from report server
Creating reporting proxy
Success
Fetching projects to delete
Deleting : /Project1...
Success
Deleting : /Project2...
Success
Deleting : /Project3...
Success
Deleting : /Project4...
Success
Reports Deleted successfully
Reports deleted successfully
Upgrading database TFSWorkItemTracking
Removing TFSExecRole on TFSWorkItemTracking
UPGRADE FAILED
Unexpected Error: User or role 'YYY\tfshidrawserv' does not exist in this database.

--- end of logfile content ---

Interesting - what can you tell me about the 'YYY\tfshidrawserv' user/account? Is it the service account you're actively using for the TFS app tier services? Is it one you used to use, but no longer? Is the account now deleted out of active directory?

The step that's failing is (obviously) our attempt at removing the TFSExecRole from the database 'TFSWorkItemTracking' (we do the same thing on each of the databases, so you may need to do these steps for each of the TFS* databases). We do this during upgrade to ensure that there's no active users of the database as we're upgrading.

Removing this role involves 2 steps: removing all the users that currently have the role, then dropping the role. Based on the error message, it looks like we're failing during an attempt to remove 'YYY\tfshidrawserv' from this role.

If you can login to the data tier and run SQL Server Management Studio, then connect to the TfsWorkItemTracking database, could you:

1. run this to see which users still have the role: exec sp_helpuser 'TFSExecRole'
2. --> most likely, there will be just one row, and it may be the 'tfshidrawserv' account if that's still your active service account
3. for each of the users listed (result column should be "Users_in_group"), try to have them drop the role with this: exec sp_droprolemember 'tfsexecrole', 'domain\user'

I'm guessing this will actually fail, but hopefully with a more useful error message.

I sorry to say, but before I got your (James) answer I decided to go another way. Here's what I did:

- Uninstalled TFS, STS and SQL Server
- Deleted all but the default application pool in IIS
- Re-installed everything in the same way as I did for my original B3R environment
- Restored a backup according to this document. I skipped updating the SIDs since I didn't re-install Windows

Everything worked nicely and VS 2005 on a client connected to the server and source control were OK, but I had no access to the reports. I tried the http://localhost/reports on the server and got following result:

The report server installation is not initialized. (rsReportServerNotActivated) (rsRPCError)

A quick look in the application log shows that services cannot connect to the reports server:

You should try the debugging steps that Dan and Bo mentioned in this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255848&SiteID=1

Was http://localhost/Reports working after you installed SQL Server but restored the backups? In a "cannot connect to database" situation, you're usually verifying 1) the databases exist and 2) the account running reporting services (should be Network Service) can connect.