Trying to install any type of TFS 2012 instance returns this error:
TF255356: The following error occurred when configuring the Team Foundation databases: TF400771: A step performer with name 'Administration' has already been registered.. For more information, see the configuration log.
Looked through the log and cant really understand what is actually going wrong. There was a problem with the config database from an upgrade done last year, so I decided to do a clean install and attach the existing collection to sort it out, however, cant seem to install TFS in the first place now.
Tried on a different server of the same setup and worked ok.
Related
Everything was fine until yesterday. This must be due to Windows update. No one touched the server. I have tired couple of similar solutions posted in Stack Overflow(all are old questions),none of them worked for me. What I have, Server Windows server 2019, APP netcore 3.1 ,IIS version 10. .net core runtime and SDK both are installed. This was working before. No one touched anything, just stopped working
In the browser appearing
HTTP Error 500.31 - ANCM Failed to Find Native Dependencies
When I executed on the command line
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in
When I checked event log. Something like below appeared. But let me tell you in the build
directory we don't have a file like app.runtimeconfig.json
What I have tried
Repair .netcoe runtime and SDK
Restore old DB backup
Reinstall .netcore versions
No pending Windows updates
Restart IIS APP pool also the server
Check file permission
None of them worked for me. If anyone can help, really appreciate.
For this issue, we can't find out that the environment of windows server caused by windows update is abnormal. As you said, it worked fine before.
So please allow me summarize below suggestions as answer.
Suggestions
Copy the publish file named original_file . And paste it in our dev pc or other server which have IIS Management. And test it, this publish file should be works. This step just confirm the publish file is normal.
Create a new website and a new application pool. Create a new asp.net core3.1 application and deploy it. Then check if it works properly under this new site.
The site should be fine in the second steps, and replace it with the original_file. And the application also should be works fine.
The site can't work in the second steps, it means the environment in you server has some problem. It could be registry issue or ApplicationHost.config issue in IIS and so on. If it's very important for you, you can rasie a support ticket and let official engineer help you to figure out what happend in this windows Update
After the third step, if the new site can run the original_file file well. We can compare ApplicationHost.config between the new site and the original one to see if any settings have been changed.
I am facing the below errors when trying to install any type of MS SQL Server on Windows 10 operating system. There seem to be a common problem/error in all of the cases (i.e. An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32") for which I could not find any workable solution in earlier related posts or other sites (quora, microsoft support etc). This is similar to iTunes installation error but the workaround for that particular solution did not solve my problem. Screenshots provided in the following arrangement:
MS SQL Server Management Studio 2016
MS Visual Studio 2015
Somehow, I have been able to solve the issue. THANKS 3N1GM4!! You did point me to the right direction! Fiddling a bit here and there solved the issue. Listing down the steps as reference to other users facing the same:
Quoting 3N1GM4: "Go to C:\Windows\Installer and search for *.msi, then add the Comments column to the Explorer window and find the file for Microsoft Visual C++ 2005 Redistributable"
Right click and uninstall
Download vcredist_x86.exe
Extract content of vcredist_x86.exe using command prompt, which will result to the VCREDI~3.EXE being extracted. Ref: (http://www.itninja.com/software/microsoft/visual-c-2005-redistributable/8-1662)
Once again, extract VCREDI~3.EXE following the steps in above link, which will result to i) vcredis1.cab and ii) vcredist.msi being extracted.
Now, run and install vcredist.msi
Note: Not sure if steps 5 & 6 were redundant but I went through with them anyway. Installing vcredist_x86 directly after step 3 may also solve the problem.
Once again, I would like to thank 3N1GM4 for this ingenuity!
Just recently my project has been going Offline and I'm unable to connect to TFS 2010 from my instance of Visual Studio (2012). When I try to connect via the VS Team Explorer window I get:
TF31002: Unable to connect to this Team Foundation Server
In the Output window of Visual Studio it looks like it repeatedly tries to connect:
....
This solution is offline. [Team Foundation Server: http://mycollection:80/tfs/defaultcollection]
The solution was offline during its previous session and will remain offline.
This solution is offline. [Team Foundation Server: http://mycollection:80/tfs/defaultcollection]
The solution was offline during its previous session and will remain offline.
This solution is offline. [Team Foundation Server: http://mycollection:80/tfs/defaultcollection]
The solution was offline during its previous session and will remain offline.
HTTP code 404: Not Found
This only seems to be impacting me, and not others in my team. I've changed my password on the off chance it had expired, and I've also restarted my machine. A few tips have been to run a TFS tool (which I don't have as it's not a local install of TFS) or are VS2013 specific.
Does anybody have any tips I could try locally to try and connect to the server?
I managed to find a solution to my particular problem, it seemed to be caused by the Cache file for TFS.
To resolve it I went to
C:\Users\[User]\AppData\Local\Microsoft\Team Foundation\[Version]\Cache
I then cleared this directory of all files and restarted Visual Studio.
It has been a while since I've published my app to Azure. During that time frame, I've upgraded my system from 32-bit to 64-bit meaning a fresh install of Windows and Visual Studio. And Visual Studio Update 3 came out and was applied. When I went to publish an update today, I received the following:
The following exception was thrown trying to publish: Root element is missing.
My web.config file looks fine so I don't think it's this issue.
The app works fine in debug mode so I don't think it's any of the .lsml files as is mentioned here.
And I tried this procedure to hand edit the .ls3proj file but it didn't seem to help.
I previously had an issue trying to publish when I upgraded from the standalone LightSwitch 2011 to Visual Studio 2012. I was able to overcome that issue using the method described in this thread.
Attempting to use this same method resulted in my new project has a full screen error saying "There are critical errors in the application definition metadata..." and 210 individual errors (max errors reached).
The first error, "Cannot create unknown type '{http://schemas.microsoft.com/LightSwitch/2010/xaml/model}GlobalAttributeGroup'." Doesn't make sense because that line in the .lsml is identical from the old project to the new project.
The second error, "Could not find any application definition in the project." Which I do not understand at all.
I am able to publish a simple "Hello, world" style app to my Azure account.
What could be causing this? How can I get more information about exactly which element is causing the issue? The log produced by running devenv /log was not helpful.
Matt Thalman was able to solve my problem over in the Microsoft Forums. The ServiceConfiguration.cscfg and ServiceDefinition.csdef were missing from the project when checked out of version control. Copying those over from a new project restored my ability to publish.
I am trying to setup a new connection to TFS with VS2012. Early on I was able to add my TFS server and, using the Microsoft Git Provider, clone a copy of the remote repository from within Visual Studio. Later, as I was fiddling with things in Team Explorer trying to find the branch I wanted to use, something broke. My local repository remains, but my connection to the remote repository was somehow corrupted, as evidenced with this error:
TF31004: Unexpected error encountered while connecting to Team Foundation Server at http: //my.server.com:8080/tfs. Wait a few minutes and try again. If the problem persists, contact the server administrator ok help
Things I have tried to resolve this:
Wait and try again (as the error message suggested).
Restart Visual Studio.
Reboot my machine.
Reboot TFS server.
Use system restore to revert back before I installed msysgit and Microsoft Git Provider, or had attempted to connect to the TFS server.
Review the MSDN help for the error (see below).
Search Stack Overflow (found one other related issue but did not seem to apply).
Tried devenv /ResetSkipPkgs
Tried devenv /setup
Re-install Team Explorer for VS2012.
Clear IE cookies (per this post).
Clear TFS caches (per this post).
The help page offers these tidbits, but none of them seem likely given that I had, as I said, the connection working at one point:
The version of Team Foundation running on the local computer does not match the version running on the Team Foundation Server server {name}.
The server returned HTML content instead of XML content.
The required Web service on the server could not be found.
Any ideas would be appreciated!
I have had an exactly the same problem.
My solution was to clear all the credentials in the Windows Vault (Credential Manager residing in the Control Panel).
I have no idea why the credentials did get messed up.