How to fix the “TF30045: The instance information does not match” error in Team Foundation Server 2010 (TFS2010).


Ok.  I’ll admit.  This error almost *never* comes up.  Nevertheless, I ran into it last week while I was doing a Team Foundation Server 2010 (TFS2010) upgrade and hardware migration for a customer. 

It starts out with an error message when you try to connect to TFS that says “TF31001: Cannot connect to Team Foundation Server at server_name. The server returned the following error: Server was unable to process request. —> Team Foundation services are not available from the server.


When you go look at the Event Log on the TFS machine, you’ll find an error message that says something like “TF30046: The instance information does not match. Team Foundation expected 34fa79c8-a6d7-4eb7-a99a-91ca0e5a4105 but found 34a2a94f-8da8-40c0-b8e7-e03a1c3595df.

The Solution: The simplest answer is to change the application id that TFS2010 is expecting. 

Step 1: Go to the “C:Program FilesMicrosoft Team Foundation Server 2010Application TierWeb Services” folder on your TFS application tier machine

Step 2: Make a backup copy of the current web.config file

Step 3: Open Web.config in notepad


Step 4: Locate the appSettings applicationId key in web.config


Step 5: Replace the “value” with the “actual” guid from the event log error message

Step 6: Restart IIS

Step 7: Rejoice.



Want some help setting up and using Team Foundation Server 2010?  Drop us a line at

9 Responses to "How to fix the “TF30045: The instance information does not match” error in Team Foundation Server 2010 (TFS2010)."
  1. You saved my day (well, my night actually…, it’s already 23:57 🙂

    But how did you find that this Guid was actually configured in this web.config!? You are great!

  2. I have restored a backup from another instance of TFS2012 Update 3 to a Hyper-V windows 2012 server but I also get this error message, I checked the web.config and my instance id was exactly the same as error message! any solutions plz?!

  3. Won’t work on TFS 2012. The real instance ID is not in the message anymore. I had to run TFSConfig ChangeServerID and look at the log file to get the actual GUID as Target InstanceID. Then I put it in web.config and the web services started working. You can test by connecting to the http://servername:8080/tfs endpoint in a browser. You will get the error message in the browser if it is not fixed.

  4. Works great for TFS 2013. Where I had to get the applicationid from was a file called web.config.sav. I copied the applicationid from that file and put it in the web.config, restarted IIS and everything worked again. Thank you! My TFS Server had been down for 3 weeks! Now I’m back in business!!! Thanks!!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: