问题描述
尝试在TFS2013.3上将OpsHub迁移到VSO时，该实用程序将在显示任何数据之前在用户映射"屏幕上失败.屏幕的白色区域保持空白，并最终在约5分钟后出现，并通过警报框引发错误.
Trying an OpsHub migration on TFS2013.3 to VSO, the utility fails on the User Mapping screen before any data can be shown. The screen's white areas stay blank and eventually after about 5 minutes, and error is thrown via an alert box.
OpsHub版本:最新-于2015年1月23日下载并安装.
OpsHub Version: Latest - downloaded and installed today, 1/23/2015.
我的OSVMU.log文件的内容显示如下:
2015-01-23 14:00:41,442 [1]错误com.opshub.eai.metadata.MetadataException:OpsHub-014371:无法为用户列表实例化元数据实现| TFS源1422039041211 ALM TFS 1422039041213，由于;嵌套的异常是: java.net.SocketTimeoutException:读取超时System.ServiceModel.FaultException:com.opshub.eai.metadata.MetadataException:OpsHub-014371:无法为用户列表"实例化元数据实现. TFS源1422039041211 ALM TFS 1422039041213，由于;嵌套的异常是: java.net.SocketTimeoutException:读取超时
2015-01-23 14:00:41,442 [1] ERROR com.opshub.eai.metadata.MetadataException: OpsHub-014371: Could not instantiate metadata implementation for For User List | TFS Source 1422039041211 ALM TFS 1422039041213, due to ; nested exception is: java.net.SocketTimeoutException: Read timed outSystem.ServiceModel.FaultException: com.opshub.eai.metadata.MetadataException: OpsHub-014371: Could not instantiate metadata implementation for For User List | TFS Source 1422039041211 ALM TFS 1422039041213, due to ; nested exception is: java.net.SocketTimeoutException: Read timed out
服务器堆栈跟踪: 在System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime操作，ProxyRpc& rpc)处 在System.ServiceModel.Channels.ServiceChannel.Call处(字符串操作，布尔单向，ProxyOperationRuntime操作，Object [] ins，Object [] outs，TimeSpan超时) 在System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall，ProxyOperationRuntime操作) 在System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage消息)处
Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
异常重新抛出为[0]: 在TFSMigrationUI.ViewModel.UserMappingViewModel.worker_RunWorkerCompleted(Object sender，RunWorkerCompletedEventArgs e)处的e:\ OVSMUBranch \ TFSMigrationUI \ ViewModel \ UserMappingViewModel.cs:line 416 在System.Windows.Threading.ExceptionWrapper.InternalRealCall(委托回调，对象args，Int32 numArgs) 在MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(对象源，委托方法，对象args，Int32 numArgs，委托catchHandler)
Exception rethrown at [0]: at TFSMigrationUI.ViewModel.UserMappingViewModel.worker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e) in e:\OVSMUBranch\TFSMigrationUI\ViewModel\UserMappingViewModel.cs:line 416 at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
推荐答案
我不知道如何或为什么，但是我使用Visual Studio删除了VSO服务器注册，然后通过Visual Studio重新添加了它，这似乎纠正ObsHub实用程序，因为现在它可以正确提取所有用户/映射.
I don't know how or why, but I deleted the VSO server registration using Visual Studio, and re-added it back via Visual Studio, and this seemed to correct the ObsHub Utility, because now it correctly pulls in all the users / mappings.
这篇关于OpsHub-用户映射屏幕在长时间等待后引发错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！