Home Dashboard Directory Help
Search

TFS 2012 error while installing update 2 CTP 4 : Invalid Uri by niccasse


Status: 

Closed
 as Fixed Help for as Fixed


9
0
Sign in
to vote
Type: Bug
ID: 780985
Opened: 3/8/2013 1:44:28 AM
Access Restriction: Public
1
Workaround(s)
view
7
User(s) can reproduce this bug

Description

After installation of the update, the upgrade wizard launches, but on the screen asking for the name of the database to update i have an error : "Invalid Uri : The hostname could not be parsed".

I tried upgrading from update 1, or uninstalling tfs before and choosing "Application only", same error.

Everything works fine with Update 1.


Here is the log :
Message d'exception : URI non valide : Impossible d'analyser le nom d'hôte. (type UriFormatException)
Trace de la pile d'exception :    à System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
à System.UriBuilder.get_Uri()
à Microsoft.TeamFoundation.Admin.Console.Models.PageApplicationTierSettingsViewModel.SetExistingSettings(TfsConfigurationDatabase configurationDatabase)
à Microsoft.TeamFoundation.Admin.Console.Models.PageApplicationTierSettingsViewModel.OnRegisteredPropertyChanged(Object sender, NavigationPropertyChangedEventArgs args)
à Microsoft.TeamFoundation.Controls.WPF.PageNavigator.OnRegisteredPropertyChanged(Object sender, NavigationPropertyChangedEventArgs e)
à System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e)
à Microsoft.TeamFoundation.MVVM.NotifyPropertyChangedDispatcherObject.RaisePropertyChanged(String propertyName)
à Microsoft.TeamFoundation.MVVM.ViewModelBase.RaisePropertyChanged(String propertyName)
à System.ComponentModel.PropertyChangedEventHandler.Invoke(Object sender, PropertyChangedEventArgs e)
à Microsoft.TeamFoundation.MVVM.NotifyPropertyChangedDispatcherObject.RaisePropertyChanged(String propertyName)
à Microsoft.TeamFoundation.MVVM.ViewModelBase.RaisePropertyChanged(String propertyName)
à Microsoft.TeamFoundation.MVVM.NotifyPropertyChangedDispatcherObject.SetAndRaisePropertyChanged[T](T& propertyDataField, T value, String propertyName)
à Microsoft.TeamFoundation.Admin.Console.Models.DbPickerControlViewModel.set_SelectedDatabase(TfsDatabase value)
à Microsoft.TeamFoundation.Admin.Console.Models.DbPickerControlViewModel.<>c__DisplayClass8.<GetDatabases>b__4()
à System.Windows.Threading.DispatcherOperation.InvokeDelegateCore()
à System.Windows.Threading.DispatcherOperation.InvokeImpl()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
à System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout)
à System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
à System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
à System.Windows.Threading.Dispatcher.Invoke(Action callback)
à Microsoft.TeamFoundation.Admin.Console.Models.DbPickerControlViewModel.GetDatabases()
Details
Sign in to post a comment.
Posted by LeonM on 5/14/2013 at 4:24 PM
Sorry for net getting back to you earlier. I had the 'Invalid Uri' issue with update 2 but can confirm it has been fixed in the Update 3 RC. Thanks.
Posted by Microsoft on 4/9/2013 at 7:40 AM
For those of you who have hit this issue, could you please send your logs to us (TFCare at Microsoft dot com)? Please zip the contents of the following locations: 1)%programdata%\Microsoft\Team Foundation\Configuration\SavedSettings 2)%programdata%\microsoft\team foundation\server configuration\logs 3)%programdata%\microsoft\team foundation\Configuration. Thank you.
Posted by Microsoft on 4/9/2013 at 7:34 AM
@Steven - the workaround is relevant to both Update 2 CTP4 and Update 2 RTM. Could you try it and let me know how it goes?
Posted by AndreyVeselov on 4/5/2013 at 5:21 PM
Wrkaround works.
Posted by Steve Squires on 4/5/2013 at 1:49 PM
Actually, I have this issue with update 2 RTM.

Could it be something to do with the service account not being known?
Posted by Microsoft on 4/5/2013 at 1:19 PM
Hi Everyone,

Thanks for the feedback, and we apologize for the inconvenience. We have gotten to the root cause of the problem for one customer (Aaron), but would like to collect setup and configuration logs from everyone else to ensure there aren't any other cases that could be causing a problem. Please zip the contents of the following locations and email them to tfcare at microsoft dot com with reference to this connect issue:
%programdata%\microsoft\team foundation\server configuration\logs
%programdata%\microsoft\team foundation\Configuration

We will work to have a fix to this problem in Update 3. In the meantime, we have a workaround which was successfully used by Aaron that you can try. The workaround is to rename the following folder: %programdata%\Microsoft\Team Foundation\Configuration\SavedSettings. This should unblock your upgrade, but without this folder we will not be able to automatically persist as many of your TFS customizations during the upgrade (the will have to be fixed up manually, as was the case in RTM and Update 1).

Hope this helps.

Posted by LeonM on 4/5/2013 at 6:21 AM
After spending a few hours I gave up with Update 2, can't pass the Invalid URI error. The next page shows 'Invalid account'. What I said earlier about IIS websites, I think it was 'normal' that IIS was empty because TFS was the only website.

I uninstalled TFS 2012.2 and reinstalled 2012.1 (the slipstreamed version on MSDN), now TFS is back online.
Posted by AndreyVeselov on 4/5/2013 at 3:51 AM
same issue with version Update 2 RTM
Posted by LeonM on 4/4/2013 at 3:05 PM
After the installation, but before the upgrade, I noticed alll my IIS websites are now missing. To be sure IIS is healthy, I reinstalled the web role.
Posted by LeonM on 4/4/2013 at 3:04 PM
I'm having the same issue on my production server, with version Update 2 RTM. Same stacktrace, Windows Server 2008 R2 English
Posted by Microsoft on 3/12/2013 at 12:09 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below. http://go.microsoft.com/?LinkId=8967043
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:
http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 3/8/2013 at 10:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by LeonM on 5/14/2013 at 5:00 PM
Instead of Update 2, install Update 3 RC or later.
File Name Submitted By Submitted On File Size  
vslogs.cab (restricted) 3/13/2013 -
Logs.zip (restricted) 4/5/2013 -