I'm trying to update my installation of VS 2022 to 17.4.5. The installation cannot complete because for some reason it cannot download two files:
Microsoft.VisualStudio.KeychainCredentialHelper.vsix
Microsoft.VisualStudio.RazorExtension.vsix
I've asked the infrastructure team at our company to investigate. But the problem now is that I can't work on anything in VS because there's an active setup. There's an option to pause the setup, but I can't find a way to cancel the setup so that I can continue working. I can't run tools like SQL Management Studio either.
Anyone know of a workaround to this issue?
EDIT: It appears the reasons these files are blocked is because they match the signature of a Virus/Win32.WGeneric.dxsfnc.
Related
My team has several Selenium Unit Tests that we run locally. Selenium opens a browser and runs through our application. This works fine locally. Now, management wants to run the tests, on demand, via TFS. Should be easy, right? WRONG!
I am having trouble setting up our TFS 2015 server to run these Selenium UI tests.
Everything I read tells me to run the "Test Agent for Visual Studio 2015" tool. Problem is, the tool does not exist on my machine and I cannot understand why. I have tried many things, like installing the MS Visual Studio "Agents", with no luck.
When I try to open the freshly installed "Agents" I get a message saying: "Test Agent for Visual Studio 2015 has no configuration tool".
So the VS.NET "Agents" panel never opens. Seems bizarre to me that I installed something that needs further configuration, with no way to perform that configuration.
From further reading, I think I need to provision a group machine in the TFS web administration page, but am totally unsure if that's required for my situation, as I cannot even get past the basics here.
I see other people have had this problem, with very little response or help from Microsoft. I am a little baffled at why this seems so very difficult to do on a TFS server? It runs locally just fine, like a breeze. But TFS? It's like a giant puzzle.
Once this is working, I need to configure the test agent to run in "interactive mode" so it can run the browser but I cannot even begin to figure that out yet. Where do you set it to "run interactive" because I dont see any of those options. Am I missing TFS installation components? Do I have the wrong Visual Studio? Do I need the Ultimate edition of Visual Studio to be able to perform UI tests with the browser? We have the Professional edition.
Here is someone with the same problem:
https://connect.microsoft.com/VisualStudio/feedback/details/1712725/test-agent-for-visual-studio-2015-has-no-configuration-tool
Does anyone have any ideas or instructions on how to setup the "Test Agent" I need to run my team's existing Selenium UI tests in TFS2015? Seems very difficult when it should not be.
In the link you provided, Allen has explained that "There is no configuration UI with the test agent anymore. This is because we have simplified the existing remote testing scenario by doing the install and configuration for you when running via the build pipeline."
TFS 2015 Update2 now have a "Run Functional Test" task that you can use to run tests (included Coded UI Tests) against machine groups. So, first you have to upgrade your TFS 2015 to TFS 2015 Update2 if you haven't.
The tasks you need for test scenarios using Visual Studio 2015 and Visual Studio Team Services (VSTS) or Team Foundation Server (TFS) 2015:
Create environments from physical or virtual machines that you've already set up.
Set up your build to run your app and tests in the environments that you created.
After your build finishes, review your test results to start resolving problems that you found.
So, your build process template should look like the screenshot below. You need to specify every task to meet the requirement of your project. All TFS tasks can be found at this website, you can get more information for each task from it. Coded UI or Selenium tests that are running on full fidelity browsers would need Interactive Process checked.:
I have been using Visual Studio 2010 Pro for my vb.net desktop application development. I publish the apps via clickonce to a web server with ftp. My settings look like this:
Publishing folder location: ftp://www.webaddress.com/folder/
Installation folder : http://webaddress.com/folder/
This works perfect in VS2010.
I am now trying to upgrade to Visual Studio 2015 community edition. When I try to publish my app, I get the error "The components for communicating with FTP servers are not installed". I am getting this error on both computers I have installed VS2015 on.
Strangely enough, there isn't much info on this error. The only solution I've seen is to repair the installation. I did this but still a no go.. Another cause I read about is having Xamarin installed, but I have never had that installed.
Has anybody run into this and know what the fix is??
EDIT:
It appears to not actually have anything to do with installed components. After I posted this question, I realized the publish via FTP had worked earlier on a little sample Hello World project i made (brain fart). It was only once I loaded my existing project that this error started showing up.
I closed the solution, created another simple project, and still got the error. I closed visual studio, reopened the sample project, and ftp worked! I then opened my existing project and ftp worked there too?! So I don't know what the trigger is, and I haven't had it fail again yet, but maybe this info will help figure out what is causing the failure.
EDIT (3/30/2017)
Just an update - I am still having this issue. This issue happens on visual studio 2013, 2015, and 2017. I have tried reinstalling the c++ redistributable, still nothing. It seems others are having this issue with a web project but mine is a desktop app publishing with clickonce via FTP. It must be something to do with solution I am working on that was originally created in 2010, as the issue is not present in any other project.
I had the same issue with Visual Studio 2017. What fixed it for me was to start the Visual Studio Installer and install the ".NET Core cross-platform development" workload.
I had the same issue in Visual Studio 2015 / Update 3. It was resolved after installing the 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013 (https://www.microsoft.com/en-us/download/details.aspx?id=40784)
See also https://github.com/aspnet/Tooling/issues/748
I had the same problem with Visual Studio 2015. And Publish used to work fine so I went going crazy looking for and trying different solutions. Then I read on another thread of doing a Setup-> Repair (submitted by Erikest). I did a Setup->Repair and the publish process now works! I think it's also possible that the Repair not only did the trick on the FTP components but also replaced the C++ redistributable (often mentioned as a solution to this problem),
This is a total work around, but I've noticed I get this error every time I open my app (that originated in VS2010) and try to publish without first opening a sample app. I created a new project and published it to my FTP server. When I receive this error, I close Visual studio, reopen and the open the sample project, publish that app, then open my real app. The publish then works.
This works every time, and seems to be a bug in Visual studio, and probably has something to do with the fact that my app was originally built in 2010.
Maybe this will help somebody else with the same issue. It's a big pain so hopefully MS gets a fix in for this.
I have been banging my head against this problem for many months, re-installed VS over and over and just did a clean install of Windows 10 in the hope it would work but to no avail. By chance I cleaned some old .accdb files from the App_Data folder that I no longer need since I converted to SQL Server database and FTP publishing now works.
So it seems VS does not like the .accdb files but was happy with .mdb files when publishing with FTP.
As soon as I put the file back in App_Data the problem returns. Hope this is some help.
I had the same issue here, I was using the Publish right click option on the project, which had been working fine. What fixed it for me was going back through the publish options and re-testing the connection. Publish seemed to work after that. Maybe it forgot a password or settings?
I also installed the x86 C++ Redistribution Package.
Hope this helps someone who is in the same boat.
After many successful website publishes with Visual Studio 2015 Community Edition, we experienced the "components for communicating with ftp servers are not installed" issue. :(
First attempt at resolution was uninstalling VS Community 2015, then installing VS Community 2017. Received the same error: "components for communicating with ftp servers are not installed" when attempting to publish our business website.
With some work, we found that by uninstalling Microsoft Web Deploy and re-installing, this seemed to fix the problem. We can now use Visual Studio > Publish function to our ftp without problems.
See this link for download of Microsoft Web Deploy components.
https://www.microsoft.com/en-us/download/details.aspx?id=43717
Dont know what broke this VS IDE functionality, but hope this fix helps some.
I encountered the same error with Visual Studio 2019
I fixed it by using the Visual Studio Installer to install the Web Deploy (inc .netcore 2.1) under individual components
I just did a simple "repair installation" in the installer. Worked for me.
I am using Microsoft Visual Studio Community 2019 and had this problem for a while.
The problem went away after I updated about 10 NuGet updates that were over due.
I had the same problem, I closed all the open windows I closed Visual Studio and then I opened again and published and then it worked!
I've been developing an application In VB.net for the past few months using Visual Studio 2013 Pro and Azure Cloud Services. Thursday when I went to run / debug the application I got an exception vshost32.exe has stopped working. After hours of research, trial and error I was unable to fix it. I uninstalled VS and re-installed it. No Luck :(
I was then frustrated to the point that I wiped my computer, Formatted the hard drives and Installed a clean version of Windows 7 Ultimate and VS Pro 2013. My application still does the same thing.. any idea what the heck is going on here? I have changed the debugger to x86 followed hundreds of solutions online with no luck.
I have now started another application but when I connect to my Azure Files then try to connect to the DB in SQL Server Explorer within VS it literally just crashes Visual Studio goes into debug mode then restarts. I have tried disabling my Firewall and Virus Protection. Can anyone point me in the right direction, I'm bummed right out as it seems I have an application which was nearing completion that is now unusable...
Thanks in advance to Everyone for your help and replies!
Do you encounter the problem when you debug it? I had the same problem when I was debugging it by pressing F11 key when the debugger point is at the sql statement. If you have the same problem, then try debugging it with F10 key.
I also have the problem to connect remote database a month ago. Each time I connect to the remote database, the application (VisualStudio/SSMS) crashed. After reserching, I found the solution for my case.
The source of my problem are:
Visual Studio 2013 or .NET Framework 4.5.1 installed
Some network anaylyzing / detecting tools installed
I don't know whether you are the same case. You can check the link for details.
I have Windows 7 Professional x64. I have Visual Studio 2010 Premium and Visual Studio 2012 Premium installed on my machine.
I installed TFS Power Tools Decemeber 2011. I restarted my computer after successful installation. I then checked out a folder from TFS 2010 but the TFS menu items in Windows Explorer context menu do not appear when i right click on the folder.
I even reinstalled it by uinstalling it, restarting the pc and installing it again then restarting it again but same issue.
I have followed the instructions outlined in here:
TFS Power Tools: Shell Extension : Context Menu Quirky and TFS Icons on Files/Folders missing
But same issue same issue occurs. Would anyone know what else i can do to get the TFS menu items to appear in the context menu please?
Thanks in advance,
I am not sure if this would help or you are willing to use a new version but I had the exact same environment and issue with you.
What I had done is that I uninstalled the old TFS Power Tools ( listed with a "Microsoft Team Foundation Server" prefix and/or "Microsoft Visual Studio Team Foundation Server" in Control-Panel/Programs-and-Features ) and install a newer version which is RTM. You can download them at http://www.microsoft.com/en-nz/download/details.aspx?id=35775 and install the following in the same order listed below
Team Foundation Server 2012 RTM Power Tools.msi
Visual Studio Team Foundation Server 2012 Update 1 Power Tools.msi
Visual Studio Team Foundation Server 2012 Update 2 Power Tools.msi
Close Visual Studio before you start then restart after installing, you should see your context menu afterwards together with the green arrow that indicates it is in TFS
Here is a screenshot of it
Also please take note that after installation this would not happen instantaneously as advised on this post: TFS Power Tools: Shell Extension : Context Menu Quirky and TFS Icons on Files/Folders missing
It sometimes takes a while for the TfsComProviderSvr.exe to check if
the local folder is a workspace and register the shell extension.
So this depends on many variables, your TFS server speed, your machine speed and your network speed. In my case I left it overnight to fully show everything.
Windows has a limit on home many overlay icons it can support. This started happening to me after i installed google drive, one drive, and dropbox and the TFSOverlay got pushed down to the bottom in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer \ShellIconOverlayIdentifiers
You can fix it by either
Uninstalling some of the overlay apps. (Eg: remove Google drive
or Dropbox)
Rename the TFS folders in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer \ShellIconOverlayIdentifiers to start with numbers so they take priority (Eg: "1TfsOverlayAdd" , "2TfsOverlayEdit" etc.).
Also there is usually a delay for the green icons to appear in the folder explorer, so be patient.
I was having the same problem and just I executed this file:
C:\Program Files (x86)\Microsoft Team Foundation Server 2012 Power
Tools\TfsComProviderSvr.exe
After a few minutes the menu appeared.
This problem also occurs when you are running Visual Studio under different credentials (i.e. an account with Administrator privileges) than the logged on user. Logging on as that same user displays the ShellExtension correctly. But that's just not an option here...
I have not yet found a solution. It would be a nice feature to be able to set some options for TfsComProviderSvr.exe, so that one can let it watch workspace folders for a different 'Team Member' than the logged on user...
I've tried running Explorer.exe with other credentials, but that does not spawn a new TfsComProviderSvr.exe. Starting it by hand with the different credentials also does not seem to work. An instance of TfsComProviderSvr.exe is always (re)spawned for the currently logged on user.
Forgive me for sharing the obvious, but I had a similar issue, and in my case it appears that the default selected installed features were different than I expected.
I reran the installer using "Modify" instead of "Repair" and confirmed that the Windows Shell Extension feature was selected for installation:
I'm running a similar environment (VS 2010 Shell with VS 2013 Professional). Perhaps that impacts the defaults.
Here is the Power Tools Installer that I used.
I had a similar issue, I ripped off old the version, gave me some issues as you have to stop the TFS process and the explorer process but you can always restart explorer again once the old version has been uninstalled.
Then I restated my machine.
Installed latest version: http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f ( version 11.0.60506.0 )
Restarted my pc again
Navigated to a source control folder and all TFS icons and shell extensions now started to appear.
Bottom line, the latest version worked for me, did not have to fiddle with reg'values at all.
Here's how I fixed mine. I had installed Visual Studio 2015 and installed TFS Power Tools for VS 2015. I also installed Visual Studio 2017. I generally use VS 2017 and had attached to TFS there. I hadn't attached VS 2015 to TFS and the power tools menu would not show up in explorer. I finally realized that when they say you have to have the same version of Visual Studio installed that you ALSO have to have that visual studio Team Explorer connected to TFS. You don't have to use it beyond that, but it must be connected using the dialog, like you see here.
I'm getting an error when trying to install sharepoint 2010 on the server (windows server 2008 R2 64bit). The prerequisites installed fine, any ideas what this means?
BEX64 event means a problem with DEP, Data Execution Prevention, or buffer overflow.
It's surely a problem in the downloaded software. You can try to turn off DEP temporary.
I was having the same issue. I tried the install on 5 different servers and got the same result so it wasn't a problem on the server - it seems to be a corrupt download file on the MS Volume Licensing site. When I ran the download using the download manager instead of the web browser download, it kept saying the file was corrupted after the download finished (tried this a few times with the same result). My solution was to download the software from the Trial download site, then use the key I had from the VL download.
The URL for the trial is here
I spent weeks trying to get this to work. And it turned out to be group policy not allowing me to install. So in case that helps anyone else with the same issue.
Attempt the install, then check the windows event viewer and look for any software warnings.
Start -> Search for "Event Viewer" -> Windows Logs -> Application,
Look for an error with a yellow Esclamation mark in a triangle that occored around the same time as the install. And see why it didn't let you install.
Mine said this:
Access to C:\Users\[username]\AppData\Local\Temp\ose00020.exe has been restricted
by your Administrator by location with policy rule {34ae1087-c2cc-409f-a442-e48e70e62efb}
placed on path C:\Users\[username]\AppData\Local\*\*.exe.
I faced the same problem while installing office on my PC.
After all possibility I found that there is existing Microsoft Office folder inside Program files (C:\Program Files (x86)\Microsoft Office) I simply deleted that folder and tried to installed again its work for me.