I am using TFS2010 and have added 3 projects in default collection.
But now I want to add one more project.
So, When I create new project , I am getting error as below :
TF30170: The plugin Microsoft.ProjectCreationWizard.WorkItemTracking
failed during task WITs from group WorkItemTracking.
Explanation Plugin error text: “TF237162: There is insufficient
system memory on the Team Foundation Server SQL Server to run this
query.”
User Action Contact your Team Foundation Server administrator.
I am admin user of machine.
I have also new collection and tried to create new team project , I am getting same error.
Can anyone help ??
I see the issue is in the database of the TFS, it seems that the disk space of the server hosting the database is too low or empty.
If you are the administrator of the server, try to free the disk space, you can also shrink the logs to increase the available space.
Also the issue may be related to the reporting services, open the TFS admin console, disable the reporting services then create your team project again then enable it at the end.
Hope this helps
Related
I have ADF Linked Services to File Server(on-prem) It is accessing X drive.
Linked Service is using Self-hosted integration Runtime (VM) to access File Server.
I have pipeline which copy files from Azure Blob storage to File Server.
This has been working fine for more than years.
However this connection got broke after Integration Runtime got software update last week.
Operation on target ForEach1 failed: Activity failed because an inner activity failed; Inner
activity name: Copy data, Error: ErrorCode= DnsResolutionFailure,
'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException, Message=x could not be
resolved., Source=Microsoft.DataTransfer.Common,'
What could be issue?
As per my analysis below are findings:
Root cause:
As of version 5.22.8297.1, to improve security, the File System Connector will no longer support connecting to local disk, for example, the C: drive, as well as \localhost.
Action Required:
For long term solution, ADF product team recommends, customers should serve files over a remote network share instead of from the local disk of the same machine SHIR is running on.
Temporary workaround:
Downgrade to a previous version of SHIR, until you've made the required change listed above (Long Term solution). Ensure to disable auto-update until the action is taken.
The latest version that supports the above scenario is 5.22.8285.1:
https://download.microsoft.com/download/E/4/7/E4771905-1079-445B-8BF9-8A1A075D8A10/IntegrationRuntime_5.22.8285.1.msi.
Once the action is completed, please re-enable auto-update, or manually update to the latest version as soon as possible.
Here is a GitHub issue where ADF product team is actively engaging with users in regard to this issue. Feel free to add your comments/feedbacks if you have any: Integration Runtime Upgrade Breaks Sink Connections
I have inherited an non working AzureDev Ops 2019 server.
I have been tasked to fix it.
The only thing I seem to be able to access is the Administration console.
The site collections (which I am guessing the should look like websites) just show a web structure.
It is like it is missing the default page.
When I try to modify the "group membership" or "administer security" I get "Http 500 internal server error. Please contact your administrator. There was an error contacting the server".
I have tried repairing Azure DepOps but to no wail.
Can anyone please point to information on how to fix or trouble shoot issues on a DevOps 2019?
I have looked at application logs and IIS logs but there is nothing useful there.
thank you for your help in advance
A project was recently deleted from the Draft and Published databases by mistake. Sever versions are still listed in the Archive database. How can I restore that project to the published database and make it available in PWA?
I tried restoring the project via Administrative Restore. I got a message saying the restore job would be queued. I checked the queue and the job finished successfully - but the project does not appear in Project Center. I'm wondering if Administrative Restore is only meant for restoring specific versions of projects that are still "live".
Thanks for any help and please ask if more information might help.
Have you checked to see if the project is accessible through Project Professional? Also, have you checked the simple things that are easy to forget, such as making sure that "sub projects" is selected in the ribbon, or that when you restored, it wasn't marked as closed, and then being excluded from the views? When I have restored a project previously, sometimes key pieces of Project Details are either missing or incorrect and the project does not appear as expected in the views. Once the project is opened, the details can be reapplied and the project appears in PWA as expected.
You could also attempt to use "ProjTool." It would be worth trying to see if that program recognizes it is as available and publish from there.
I Try to deploy a application using Microsoft Release Management for Visual Studio or better known as "InRelease". But i face unexpected Problems using the MSI-Deployer.
The deployment fails with the flowing error:
Setup.msi XXX139W8 10/1/2014 11:19:18 AM 00:00:00 Package location '\\Server\drop\Application\Build_20140930.5\Setup.msi' does not exist or Deployer user does not have access. Failed
First suggestion(incorrect Path) is not the case, i double checked that.
So why does my Deployer user not have access to my server? And how to fix that?
I tried out running the DeploymentAgent as Administrator, as Local Service adding XXX139W8$ permissions to the drop folder, running as domain user with admin rights on the drop folder.
Sadly the deployment agent is totally unreachable or the error mentioned above shows up.
Here are some system specs:
TFS and RM Server run on a Windows Server 2012 R2 with SQL Server Express 2012 Installed.
The client i am Working on uses the Release Management Client for Microsoft Visual Studio 2013
The Target Machine is a Windows 8.1.
The deployer user is defined in the MS Deployment Service, ensure that this account has access to your Drop folder. I give the domain\EVERYONE account read access to the drop folder so that anyone can read the data
I resolved this Problem.
The cause was that i specified a File as Package (quite confusing if you try to deploy a single msi file) but the Component should only specify a Folder "Package".
The deployment agent fails to access the Folder (Setup.msi) and fails with the error i showed above.
Then i wasted hours in trying to fix my access problem, because if i enter the "Package location" everything worked fine._.
I have installed OpsHub and trying to migrate the source code from VSTF2013 to VSO. After selecting the TFS Endpoint and VSO Endpoint, clicking on Next. When trying to load the projects to be migrated I am getting this error, "TF50608: Unable to retrieve information for security object $PROJECT:vstfs:///Classification/TeamProject/faedd6e7-e2bc-4f91-917f-3823c951e71b, it does not exist."
When I select some other TPCs in the same VSTF server, I am able to load the projects in VSTF. Could not understand this error code if this is related to security configuration at TPC level or OpsHub is trying to load some project which is does not exist?
I have done some search on this error code TF50608, looks like this issue can occur if any Team Project is deleted and created with the same name. I am able to connect to TPC and load the projects using TFS Administration Tool (http://tfsadmin.codeplex.com/) but OpsHub fails to load the projects.
Is there any work around to skip this error and continue with the selection of the Team Project?
We have verified it is a defect. It will be resolved in the next build coming out soon.
use VERSION 1.0.1.005, in which this issue is resolved