locked
ERROR: TF55030: Rename Data Tier failed while attempting to rename the server on a single server deployment of TFS.

    Question

  • I followed all the steps that are detailed in "How to: Rename a Data-Tier Server" (http://msdn.microsoft.com/en-us/library/ms253106.aspx) to try and change the name of the machine running our TFS server. (the documentation states that these are the same steps that one needs to take to rename a TFS single server installation).

    After I get to the step "Update the Application-Tier Server to Work with the Renamed Server" and I run TfsAdminUtil RenameDT, I get the TF55030 error.

    I then ran Set TfsDetailedErrors=1 and reran TfsAdminUtil RenameDT. This time I got some more information and found that the error is being caused because the "the remote name could not be resolved" and the remote name it was looking for was the old server name. (Obviously it wont find it because it has been renamed to a new server name). Is this a bug? What is my work around?

    I tried running the steps documented in "How to: Rename a Data-Tier Server" on the Virtual PC image of TFS 2008 (downloaded from Microsoft) and I get the same error.

    The exact steps I undertook can be found on my blog post: Unable to rename machine running TFS 2008 (single server deployment).

    The error message I get is : ERROR: TF55030: Rename Data Tier failed. Please verify that the supplied Data Tier name is a valid Team Foundation Data Tier name,that the Data Tier can be accessed on the network and that you have administrative rights.

    Further investigation shows that the error is being thrown because of "System.Net.WebException: The remote name could not be resolved ", where the name it is trying to resolve is the old server name (which no longer exists because it has been Renamed!)
    Thursday, April 16, 2009 7:40 PM

Answers

  • Hi rocky

    I just replied you in your blog post. :)


    Time and tide wait for no man.
    • Marked as answer by rockyMtnRajah Monday, April 20, 2009 1:38 PM
    Monday, April 20, 2009 7:54 AM
  • Hello Bill,

    You and Robert were correct about how to get around the TF55030 error in my case. (unfortunately, I an now running into an issue with ActivateAT command!).

    But here are the steps that I took to make sure that RenameDT works, reproduced for the benefit of others....

    After having update the Reporting Services database setup and windows identity....

    On the server
    1. Open folder "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services"
    2. Open the web.config file and change the connection string's server name to the new server name. Save and keep file open.
    3. Open a command prompt and go to folder "c:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools" and run
        TfsAdminUtil ConfigureConnections /view
        Reports Uri and ReportServer Uri should show up as pointing to the old server name.... we need to update it.
    4. update the reporting uris
         TfsAdminUtil ConfigureConnections /ReportsUri:http://<NewServerName>/Reports /ReportServerUri:http://<newServerName>/Reports/ReportService.asmx
        Should run successfully
    5. Change the server name in the web.config file that you edited in (2) back to the old server name (required for TfsAdminUtil RenameDT to work!).
    6. Start the Report Server and Microsoft Team Foundation Server Application Pool
    7. Make sure that the default web site is running
    8. Run TFSAdminUtil RenameDT <newServerName>
       should run successfully.

    http://blog.aggregatedIntelligence.com/
    • Marked as answer by rockyMtnRajah Monday, April 20, 2009 1:38 PM
    Monday, April 20, 2009 1:38 PM

All replies

  • Hi rocky

    I just replied you in your blog post. :)


    Time and tide wait for no man.
    • Marked as answer by rockyMtnRajah Monday, April 20, 2009 1:38 PM
    Monday, April 20, 2009 7:54 AM
  • Hello Bill,

    You and Robert were correct about how to get around the TF55030 error in my case. (unfortunately, I an now running into an issue with ActivateAT command!).

    But here are the steps that I took to make sure that RenameDT works, reproduced for the benefit of others....

    After having update the Reporting Services database setup and windows identity....

    On the server
    1. Open folder "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services"
    2. Open the web.config file and change the connection string's server name to the new server name. Save and keep file open.
    3. Open a command prompt and go to folder "c:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools" and run
        TfsAdminUtil ConfigureConnections /view
        Reports Uri and ReportServer Uri should show up as pointing to the old server name.... we need to update it.
    4. update the reporting uris
         TfsAdminUtil ConfigureConnections /ReportsUri:http://<NewServerName>/Reports /ReportServerUri:http://<newServerName>/Reports/ReportService.asmx
        Should run successfully
    5. Change the server name in the web.config file that you edited in (2) back to the old server name (required for TfsAdminUtil RenameDT to work!).
    6. Start the Report Server and Microsoft Team Foundation Server Application Pool
    7. Make sure that the default web site is running
    8. Run TFSAdminUtil RenameDT <newServerName>
       should run successfully.

    http://blog.aggregatedIntelligence.com/
    • Marked as answer by rockyMtnRajah Monday, April 20, 2009 1:38 PM
    Monday, April 20, 2009 1:38 PM
  • Hello rockyMtnRaja, Bill and Robert,

    How did you get around the TF55030 error? I can't access the blog (blocked by corporate firewall). Can you please post the solution in this forum?

    Thanks,

    Vik

    Friday, April 24, 2009 7:34 PM
  • Hello Bill,

    You and Robert were correct about how to get around the TF55030 error in my case. (unfortunately, I an now running into an issue with ActivateAT command!).

    But here are the steps that I took to make sure that RenameDT works, reproduced for the benefit of others....

    After having update the Reporting Services database setup and windows identity....

    On the server
    1. Open folder "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services"
    2. Open the web.config file and change the connection string's server name to the new server name. Save and keep file open.
    3. Open a command prompt and go to folder "c:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools" and run
        TfsAdminUtil ConfigureConnections /view
        Reports Uri and ReportServer Uri should show up as pointing to the old server name.... we need to update it.
    4. update the reporting uris
         TfsAdminUtil ConfigureConnections /ReportsUri:http://<NewServerName>/Reports /ReportServerUri:http://<newServerName>/Reports/ReportService.asmx
        Should run successfully
    5. Change the server name in the web.config file that you edited in (2) back to the old server name (required for TfsAdminUtil RenameDT to work!).
    6. Start the Report Server and Microsoft Team Foundation Server Application Pool
    7. Make sure that the default web site is running
    8. Run TFSAdminUtil RenameDT <newServerName>
       should run successfully.

    http://blog.aggregatedIntelligence.com/

    I am specifically looking for these steps:
    "After having update the Reporting Services database setup and windows identity...."

    How did you do this..??

    VIk
    Friday, April 24, 2009 7:38 PM
  • Hello Vik,

    They are steps 2 and 3 on the page "How to: Redirect Reporting Services to Connect to a Different Data-Tier Server ." (http://msdn.microsoft.com/en-us/library/cc668756.aspx).

    I was able to get RenameDT to work after I first redirected reporting services and then followed the steps that I posted here on April 20, 2009 1:38.

    Unfortunately, after that I got stuck with the ActivateDT step with a 404 error. As of now I have given up trying to rename the old server. I am now going to try and stand up a new server with the new name and migrate TFS from the old server to the new one. I will post here once I start working on that.

    Let me know if it works out for you and if you had to use any other steps.

    Best of luck.

    Raj



    http://blog.aggregatedIntelligence.com/
    Friday, April 24, 2009 10:32 PM
  • Vik, one more thing....

    When you get to ActivateAT,

    try the following steps if it (ActivateAT) doesnt work for you....

    1) Use SQL Management Studio to login to the database where all of your TFS databases are kept
    2) Find the Database "TFSIntegration"
    3) Open the table "tbl_service_interface"
    4) Update all the enteries that were pointing to the old machine name.
    5). Ran ActivateAT. Succeeds
    6). Renamed all the enteries back to old machine name

    Unfortunately, I encountered another error right after that... and still havent managed to successfully get TFS to run on a renamed server.

    Also, what Robert had suggested was that we use the "How to: Move Your Team Foundation Server from One Hardware Configuration to Another" (http://msdn.microsoft.com/en-us/library/ms404869.aspx) to rename the single server deployment of TFS. (link )

    At this point I am unable to "Rebuild the Team System Cube"!

    Raj
    http://blog.aggregatedIntelligence.com/
    Friday, April 24, 2009 10:43 PM