I get the following error: Unable to attach to machine 'machine name' when running my project in debug mode with visual studio 2003.
I have not find this error/solution anywhere on google or stackoverflow, this is why I am asking here. I'm not even sure what is causing it, I haven't made any changes to the project's Property or any code.
Additional Info:
Debug mode worked fine before.
No issue with release mode.
Any hints will be helpful.
This issue was somehow related to ClearCase version Control. Making a new view in ClearCase solved the problem.
Related
I have recently installed Microsoft Visual Studio 2015 Community Edition on my laptop.
Since the time of installation I have been facing a few issues.
I was not able to even access the New Project option itself.
Some of the times I will be able to access it however, sometimes it does not even allow me to access a single file of my solution in the startup itself it gives me an error.
I have attached a set of five screenshots in this query. There is some blank space after users path, I removed an extra folder name(username) from the path so dont get confused with that.
The detail of all the screenshots are as follows:
1) This is the image I get when I launch the Visual Studio on my laptop.
2) Once I click 'NO' option on the first dialog box I get a new one stating an error with the source code.
3) Once that is done, I move onto Solution Explorer to access the solution and I get this log.
4) When I try to access the tools tab to check for options I get this error message.
5) I had even tried to create a new project and the following error provided in this screenshot would appear.
I am not able to understand where I could have gone wrong or what happened that has corrupted the application to this extent. Is it an installation issue or are there some bugs in this version of Visual Studio, if there are any I would be more than happy to move to previous versions as I was a lot happier with them than this one.
If someone would help on this concern I would be really thankful.
Regards,
Harrisson
First, I went ahead and uninstalled the current version of Microsoft Visual Studio 2015 from my system. Then, I searched and removed the data from the temporary files related to MS VS 2015 from the following paths:
C:\Users\Username\AppData\Local\Microsoft\VisualStudio
C:\Users\Username\AppData\Roaming\Microsoft\VisualStudio
Once this had been done, I went ahead and installed Visual Studio 2015. After installation, I installed the additional support directories for Visual C++. You can do the same for the platform you wish to work on.
Then I installed updates from the following link:
https://www.visualstudio.com/en-us/news/releasenotes/vs2015-update3-vs
Once I started the solution it worked perfectly fine after that with no errors.
I'm using Visual Studio 2015. I'm trying to use Diagnostic Tools and somehow that window is always blank. There is nothing displayed in that window. There is no error too. I tried the same with empty IDE, loading a project, and debugging the project but in all scenarios it is completely blank, just the window heading and nothing else.
I've seen other issues with Diagnostic tools such as this, and this but I can't find anybody facing issue like this.
I tried reinstalling VS and also checked by installing VS 2015 Update 2, nothing helped.
It would be great help for me if anybody got any idea why it is happening or what can I do to find the issue or fix it?
Product version: Visual Studio Enterprise Edition 2015 with Update2
OS: Windows 7 Enterprise Service pack 1
I have experienced this same issue with VS 2017. For me, the problem is that my laptop has a 4K display, but I'm also connected to exernal monitors that are not 4K. VS seems to have trouble rendering the diagnostics tool panel when I move the VS window around or connect/disconnect the external displays. If I restart VS and open it on the desired monitor, it starts displaying again.
Please try to enable logs for the diagnostics tools based on instructions here. Probably, log contents can provide some hint for the reason of the issue.
Starting VS2015 as Administrator worked for me as a workaround.
The only error that I found in logs (enabled as in Andrey's answer) was this one:
Error --- datawarehouse.cpp --- Path should be secure at this point: 'C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CLIENTDIAGNOSTICS\APPRESPONSIVENESS\..\MemoryProfiler\DataModel'
Otherwise logs looked fine, with entries of Debug and Info importance only and nothing suspicious.
I had the same problem, when I blocked with SRP executable file of Microsoft Edge WebView2:
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\110.0.1587.50\msedgewebview2.exe"
So, I you wish Diagnostic Tools working, you need to have Microsoft Edge WebView2 installed, or allowed it for execution.
To install it, run the file with arguments:
MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /install
Situation.
I have Web developer Express Studio 2008 installed on my system.
Until recent windows update it worked fine, but about 2 weeks ago it start giving me an error every time I attempt to create any new project. Screen shot of an error below:
Express 2008 error
I did try to do windows restore to point before update and it did not worked.
As a next step I installed Visual Studio 2010(same result) and VS 2015 same result but a bit more descriptive error. Screen show below.
VS 2015 error
But there is no clear information on Microsoft MSDN forums about this error or how to fix it.
I did try to do reset(devenv.exe\resetsettings) but so far no luck.
Any idea what is going on and how to fix this?
Right now I can not create ANY new project and some of older projects are not opening as well. There is no system of or any kind of similarity between projects which opens or not.
This is a fairly vague error as the dll in question isn't listed here and 0x8007045a is just the error code for this dll initialization error. As a next step in troubleshooting to find the issue (outside of a windows repair) I'd go ahead and run Process Monitor and watch the file system activity for Visual Studio (once you see devenv.exe show up, right click on it and include just that process.
There's a blog post with some troubleshooting steps here but really though, you need to find which library is the culprit to track down what you'll need to reinstall (likely from a system or shared library side).
I'm getting the following error message
Cannot access a disposed object. Object name: 'MarshalingWindowFrame'.
This message came when I tried to load a SLN file into VS2013.
What is the reason?
I am using VS2013 Ultimate with Update 4 on Windows8.1 pro x64 bit OS (8GB RAM, 500GB HDD)
If you get that when opening a solution, either an addon is bugging out or (worse, but less likely) you found a bug in VS itself. Try safe mode and see if that helps.
If however you get the error when opening a form rather than the solution itself (remember opening a solution loads the various forms), there's a bug in an user control that's trying to access a disposed object. Remember that user controls run as binaries when hosted in VS, so make sure you put actual code inside guards that require you not to be in design mode.
Was that project created in the earlier versions or in the Visual Studio 2013 Preview? Because, if you update this project from Visual Studio 2013 Preview, you have to check the update procedure (http://blogs.msdn.com/b/lightswitch/archive/2013/08/12/upgrading-your-lightswitch-projects-raghuveer-gopalakrishnan.aspx) first, perhaps it can give some hints why this happens.
I had previously installed the VS11 beta, and had some issues with my Visual Studio 2010 instance, which you can see here how they were resolved: Excel AddIn Click Once deployment issue.
Now I have a code base which compiles/builds a vsto, which installs fine and runs fine in Excel 2010. However, when I remove the installed version from Excel, and try to run it directly through Visual Studio 2010, the AddIn does not get loaded into Excel when running in debug configuration mode, in release configuration mode it works fine. Any ideas on why this might be occurring? I've tried re-enabling it through Com AddIns, and a few other things with no luck.
I've found the issue which was not letting me run my project in 'Debug' configuration mode, though it worked in 'Release' mode. At some point, the AddIn, got hard-disabled (not sure if that's the term to use). At that point, trying to re-enable from within Excel doesn't do anything. Within the registry, there is a folder where disabled AddIns are flagged. I deleted all of the keys from this folder except for "(Default)" and now my AddIn works when launching from Visual Studio 2010 in 'Debug' mode.
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Excel\Resiliency\DisabledItems
When you run through Visual Studio 2010 does it hits the breakpoint in the addin_startup event.
If not try to debug this way
Hope this helps you
You can reenable a hard-disabled Add-In with Excel
http://msdn.microsoft.com/en-us/library/ms268871(v=vs.80).aspx
I had the same problem with a Word VSTO, but there was no Resiliency\DisabledItems folder in my registry, so I think it was never hard disabled (as in #mservidio's solution). What worked for me was to edit the Manifest path in HKEY_USERS\<user key>\Software\Microsoft\Office\Word\Addins\<Add-In name> to reflect the 'Debug' path rather than the 'Release' path.
To find the right folder it might be easiest just searching for the Add-In name and checking that any Manifest keys refer to the Debug path.
I had the same problem in Excel.
The following worked for me:
Go to the following key....
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\AddInLoadTimes
see if your plug-in is listed. if so, delete it.
now run your app from Visual studio again.
This worked for me, hope it can help someone else.
I also had the same problem, what I didn't understand was :
Why I re-install Office 2016, I don't change my code neither VS setting but I get a cant load error message ?
After many many hours, repairing Office and VS and getting the same error message, I observed that the Addin was starting well in Release config, I started checking the difference between the both config in my code.
I found that debug config was targeting to x86 proc bug release to any cpu
So Office x64 didn't load x86 dlls (in my case)