After trying to connect to my Desktop at work last night and failing due to network issues, this morning when using Visual Code SSH, the files inside Visual Code are old files (I can tell because if I go to the same folder using terminal ssh, I see the files are different). IOW, it seems like Visual Code is showing me an older version of the files. I tried removing the VC server cache on the desktop but still seeing the same issue. Has anyone seen this?
My setup:
Client: Windows 10 pro running Visual Code with the remote SSH extension
Server: Ubuntu 16.04 (which also has Visual Code installed)
Please note, till Yesterday, the setup was working fine. I could edit files on the remote from the local VS and compile on the remote host. But Today, the files that I see on Visual Studio do not correspond to those in the same folder on the remote.
This turned out to be false alarm. The problem was that Visual Code was pointing to the wrong tree.
Related
I am running an assembly jar file in command prompt and getting the exception below. And resulting in termination.
Uncaught error from thread [ccp-akka.persistence.dispatchers.default-plugin-dispatcher-23] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[ccp]
There is nothing else running in my windows machine while this.
No code access is there except a jar file.
What might be the issue, i tried restarting the machine a couple of times.
Looks like the issue is only with my machine since it is running fine in all other machines. Even i cross checked all the environmental variables.
Attached the screenshot.
What it says that there is a missing binary dependency, leveldbjni, which interfaces with native/platform specific version of leveldb.
Adding leveldbjni-all to your dependencies as described in the docs (http://doc.akka.io/docs/akka/2.5.0/scala/persistence.html#id8) should solve that, if it doesn't then maybe the platform is unsupported (which seems weird, the leveldbjni homepage lists both win32 and win64 as supported - https://github.com/fusesource/leveldbjni)
Step1: Go To "C:\Users\asaini75" and Delete already existing folder ".datastax_studio"
Step2: Go To "C:\Users\asaini75\Downloads\datastax-studio-6.0.0\bin" and click on "server" windows batch file and Wait until you see the below message on your command prompt.
Step3: Go To browser and hit the URL "http://localhost:9091". You will below the home page.
Step4: Add connection and Notebook. it will work perfectly fine.
I installed the Microsoft Visual C++ 2010 Redistributable for my windows machine, that solved my issue. Reference.
The Microsoft Visual C++ 2010 Redistributable Package installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2010 installed.
Download link here (x64).
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 have a project on my studies to write kernel driver. First step of this project is to prepere working environment, so I installed WDK, installed and configured Windows 7 x64 on virtualbox machine and created hello world kernel driver solution from the internet. After that I could deploy and debug my driver in windows 7 client machine directly from visual studio. Everything worked fine. After few days there was an update to windows 10 (host) - november update 1511, I installed that and (sic!) removed ,,previous Windows installations" to get disk space. Unfortunatelly when I opened my project again - I couldn't deploy and debug my driver due to visual studio crash. I can't find workaround for 3 days which is really frustrating beacause I have to show it to my professor on monday.
What I have tried to do:
I completly reinstalled visual studio and WDK (in host and client machine) and it still happens.
After compile, when I click ,,Debugging tools for Windows - Kernel Debugger", visual studio is crashing
(screen)
I can't get previous installation back and now I have no time to reinstall entire system.
Can you help me, please? Is there a way to get it working again?
PS. Excuse me for my english
I solved that.
After I upgraded my OS, I had still installed WDK 10.0.10240, it was not updated to the newer version. Even if I reinstalled it with new wdksetup.exe downloaded from microsoft site, there was still this version. Microsoft did not update their download page. I searched in google "WDK 10.0.10586.11" and I found the direct link to the newest WDK 10.0.10586.0 on tweettunnel.com/vanhoivo.
The link is:
http://download.microsoft.com/download/C/E/1/CE19C726-6036-4443-845B-A652B0F48CD7/wdk/wdksetup.exe
After I installed this wdk version, the problem has solved, VisualStudio is not crashing now and I can deploy and debug my driver. However, I think that is a bug in VisualStudio - it should show an error that WDK version is not appropriate
Thanks
"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."
Searched for similar posts, but didn't found one. If duplicate just inform.
I am not trying to connect to any remote machine. Just testing on my local machine.
Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)
Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.
I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.
This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:
127.0.0.1 mydomain.com
This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
Ensure you have Local Machine selected in this drop-down menu:
Windows 7 x64, VS 2012, VB.NET
I fixed it like this:-
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK.
To start VS2012:-
Double-click the msvsmon shortcut icon (that you created above, to launch msvsmon). Wait for the "Visual Studio Remote Debugging Monitor (Administrator)" window to display before continuing ...
Double-click the "Visual Studio 2012 Professional" shortcut icon (that you created above, to launch VS2012)
In VS2012, ensure standard toolbar is visible.
In VS2012, ensure "Solution Platforms" dropdown (on standard toolbar) is visible and set to "x86".
and debug now works (for me anyway) ...
However after 15 minutes or so, debug may stop working and you may get the msvsmon error again. If that happens, simply close VS2012 and msvsmon and then start again (from "To start VS2012:-" above) ...
Myself and several other developers have been trying to look for a solution for this problem for about 3/4 hours as Visual Studio crashed then this error would occur (twice in 2 days). I then suddenly (after a lot of debugging and trying other suggestions and headbanging) I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project, once I changed it to my project's one it then worked.
Hope this helps and saves people from hours of pain!
I also got this error, I usually run sites under a named user (which is also a database user) and forgot to set the Application Pool. (parliament's answer also helped me)
For me this worked in VS2013:
Save your work, close Visual Studio then reopen your project
I encountered this error as well.
The cause of mine was that I had accidentally emptied out the following property
Properties->Debugging->WorkingDirectory
Changing it to:
inherit from parent or project defaults
Solved the issue.
If you are using Microsoft's Azure, try attaching manually the debugger:
I have outlined the steps in the following answer:
https://stackoverflow.com/a/35738995/1057052
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.