I started a migration source code from TFS (not work items) to Visual Studio Online and it has been running for more than 24 hours but the status still shows "Reading and Analysis". CPU usage for the application is showing 0.
Should I keep waiting or is there a way to find out if an exception is thrown? I am not too familiar with debugging procedure for Java applications.
Which version you are using?
There is performance issue with label which is fixed in version 1.0.1.005.
Can you try current version?
Error : TF14045: The identity 19b7a3e0-b25b-4c48-90a8-813202d6d1b4 is not a recognized identity.
above error comes while connecting to tfs server that's why utility continuously displaying reading and analysis because everytime utility connects to source TFS for fetching total number of change sets and lables it encounters same error.
As per microsoft blogs, people are encountering this type of issue after upgradation/db restore for collection. After this process when user tries to connect tfs, it always throws the same error which you have encountered. Have you done any of the above process for the collection you are trying to migrate? You can refer following thread which contains resolution for same error.
http://social.msdn.microsoft.com/Forums/vstudio/en-US/b67ad1d6-d763-4602-bf14-489a3389a30d/getting-tf14045-the-identity-guid-is-not-a-recognized-identity-after-db-restored?forum=tfsadmin
Let us know in case you won't be able to resolve this with the above information and also in case you have not done any upgradation/db restore procedure. In that case we would like to know your source tfs version and older upgrade history of this instance (If any).
Related
I have been working with SF for a while now. Recently, I began having a problem when I do a Start to debug. The service shows in error and I get the infamous Partition is below target replica or instance count.. The strange thing is that I can deploy to local or remote SF provision and attach debug with no problem
I thought that something was wrong with my code, but it turns out that when I create a brand new test project, without any custom code, the same thing happens.
Note, this does not happen if I create a .net core service, only the ole .net service..
This is very strange, and I speculate that it possibly caused by the environment or VS.
I am running the latest updates on VS2017, latest SF on Windwoes 10 with latest updates..
PS: I also get the a 64-bit debugging operation is taking longer than expected when I exit the debugger
I am trying to migrate from TFS 2013 Update 4 to Visual Studio Online. I have had real difficulties using OpsHub Migration Utility, so I have come now seeking advice on how I may go forward.
I have 65 Team Projects to migrate, some with source code, others fairly empty with just a few work items so they differ in size a fair bit. I want to maintain branches we currently have which are cross Team Projects so I initially tried selecting all 65 projects for migration. This took 11hours at the creating configuration stage of the utility, then on getting to the end the tool complained it could not communicate with the service OpsHub Visual Studio Online Migration Utility. So back to square one.
Next approach was to batch the projects into sets of 10 projects. The validation and creating configuration stage was done in 10mins for each set which was a big leap forward, and the migration actually started. This has currently been running for about 17hours. It has done 29,000 work item revisions out of 480,000 across all Team Projects, so I think this may well take a couple of weeks to clear. It hasn't started on the Version Control data yet, which I'm hopeful it does at a later stage but this says not running at the moment.
This is running on a fast i7 box, with 16GB RAM, SSDs the business. 100Mbps internet connection.
I have emailed OpsHub to find out if the commercial version will perform better. But any suggestions what I could do better welcome, including any alternatives to the migration tool.
For Configuration creation taking high time, the assumed reason seems
to be due to issue in communicating with the service OpsHub Visual
Studio Online and waiting till the TimeOut.
The Work Item migration sync time seems to be near to the expectation, migration of Version Control data will be started once the work item migration is completed.
Also as the data is in big amount, its taking time but the migration would keep on running in background, you can use your source TFS instance(if required) without stopping the migration.
For more details on Profession Services you can drop an email to support#opshub.com
There is another tool named TFS Integration Platform that developed by MS for TFS Migration. You can try with it to see if it can migrate the data faster.
We are trying to migrate from our on-premises TFS 2010 to Visual Studio Online (VSO). We did it a first time just to test it out. The OpsHub application stopped a couple of times, but we finally succeeded. We did our testing and deleted the project from VSO.
The second time dident go so well. It gives the following error after migrating a lot but not all of our change sets:
com.opshub.eai.config.exception.ConfigServiceException:
OH-CONFIG-0101: Exception while calling service, underlying cause :
could not execute query.
We can press OK and navigate into another view in the application but the same error occurs on every view. We have restarted the application, the service and even the server. We always get the same error. We decided to uninstall the application and reinstall it. That solved the problem, but it appears again after we have migrated about 60% of our source code (a day or so).
So, after 3 re installations we are about to give up. It doesn't crash on the same change set every time.
Does anyone know a way around this? Is there any way we can see the real cause of the problem and fix it?
We are using version V1.3.000B000 (latest version).
Not sure if this is the proper place to post the question, but OpsHub is referring to stack overflow for support.
How can I fix this error so that the migration completes please?
OH-SCM-009: Error occurred while sync. GetAndDownloadFile :The server returned content type text/html; charset=UTF-8, which is not supported.
Retrys all seem to fail at same changeset ID 371
Thank you
depending on your on-premises TFS version, the issue could be in your TFS Data Cache (on the machine where TFS is deployed) or configuration of Visual Studio or even corruption of data.
This (https://social.msdn.microsoft.com/Forums/vstudio/en-US/b3c9ab89-17b0-45b1-bf70-4c338ae6b523/the-server-returned-content-type-texthtml-charsetutf8-which-is-not-supported?forum=tfsgeneral) thread might be referred to, for a possible solution. Which suggests the user to clear his cache.
In any case, it might be a good idea to contact Microsoft Support or try posting on Social MSDN.
I have installed AppFabric onto Server2012. I checked the prerequisites were installed first and have installed accumulative update 3. I have an instance of SQL Server 2012 installed to SP1 and the OS indicates that all updates have been installed.
When viewing the dashboard I am receiving the error:
Unable to cast object to type
'System.Management.Automation.PSCustomObject' to type
'Microsoft.ApplicationServer.Management.Data.Group...'
I've found minimal information during my google searches, none of which are providing a solution to the problem.
Can anyone help with this?
I had the same issue and found that applying Windows Update KB2932678 (Cumulative update package 5 for Microsoft AppFabric 1.1 for Windows Server) stopped the error from coming up.
EDIT : KB3092423 (Cumulative Update 7) is the latest one I could find, so if you are going to apply an update you might as well apply the latest one.
I've had the same issue. I read somewhere (don't have the link) that it appears because there are no records in the AppFabric Monitoring DB's table that contains the instances (of the service).
Once you have at least one record there, the error will disappear and the Dashboard will show the WF instances correctly.
This worked in my case.
UPDATE:
To be precise, the table which is relevant for the AppFabric Dashboard to stop showing the aforementioned error is: AppFabric Persistence DB's table [System.Activities.DurableInstancing].[InstancesTable] . This table should contain at least one record that is related to the WF Service(s) that the current AppFabric Dashboard is shown for.