I'm trying to publish a DB project in Visual Studio 2013 Professional and the "Publish" button do nothing.
In project properties I checked "Create script (.sql file)". I right click the project name in solution explorer > Publish... > Load Profile (a profile that works for my colleagues) > Publish
Nothing Happens, not an error, warning or anything (same with "Generate Scripts" button).
Visual studio error logs say nothing and I tried to restart the PC, Visual studio and SQL server.
Thank you!
If you have an Azure Cloud Explorer window open in Visual Studio (could be table, blob or queue), that leads to the Publish of an SSDT project hanging.
Close the window and start a new Publish operation. It may take a little longer than usual but eventually that will progress and you'll be able to close Visual Studio as normal.
Thanks to Noel Abrahams for his comment that led to this answer.
EDIT: putting it here as an answer so that it can be more easily found but credit goes to Noel.
Found a fix on the MS Connect site.
In my publish profile I had set the connection string as so:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=SSPI;</TargetConnectionString>
According to the comments on Connect, it doesn't like Integrated Security=SSPI. Instead you should use Integrated Security=True;:
<TargetConnectionString>Data Source=.\sql2008r2;Integrated Security=True;</TargetConnectionString>
Then it all works fine.
I cloned the solution from VCS to a new directory and only this helped.
Other symptoms that I had with this issue:
While editing a table .sql script, Design pane didn't work.
Integrated Security=True; was set in my publishing profile. So Rhumborl's answer is not about my case.
If the solution folder is copied to another machine the issue is reproduced there too.
I tried to Clean Solution before re-cloning, but it didn't work.
For me publishing the database project to a new sql server database with a different name allowed the publish to proceed. Once I'd done that I was then able to publish to the original database again.
I found that having an Azure Queue or Blob Storage opened in Visual Studio Professional 2015 meant that clicking Publish did nothing and I couldn't close the application. After closing those windows which I had launched from the Cloud Explorer, I had to click Publish once again to kick it off. A strange bug.
Related
I got an issue with the tfs.
Firstly after my tfs server database got full.
So in order to solve it i cleared the table of logs from tfs server.
Now at time of clearing data one of my workspace had checkout of one file. As soon i finished my clearing data, it is giving me this error TF30063: You are not authorized to access Microsoft-IIS/8.5. at every time i try to get latest version.
Thats how i am unable to take latest.
Any help would be appritiable.
Right-click solution
Get Latest Version
Try commit again
Issue started for me when I upgraded to VS2017
For me it helps if i just click the Refresh button at the top of the Team Explorer.
After that, the message disappears and i can normally check in.
For me, it helped just to restart Visual Studio.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
Clean the Cache folder on Server machine. The folder path is: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data
After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
I just reconnected to the team project in the Team Explorer and my commit went through, didn't have to restart anything.
I had the same issue. When I closed an open Source Control Explorer window and all the files in Visual Studio, I was able to check in.
I think i got solution, exactly got that how to do.
Do checkout that file and check in an old version of that file
and
than do take latest.
It will not generate this error again.
If you can get a copy of the file that is on TFS you can add it as a new file to TFS, and then do get latest version of the file, and then select keep local when you get the conflict error, and then you can check in the file. After that you can then get latest with no errors.
For me, Run as Administrator from Visual, It will never make this error again.
1 : Open TFS window.
2 : Click on Refresh(F5).
3: Try again to Check-in.
CLick here see Solution (Image):
I have faced same issue while check-in on TFS : You are not authorized to access Microsoft-IIS/10.0.
Using Visual Studio 2017 Enterprise with the latest update installed v15.2 (26430.4) on Windows 10 64-bit. The issue has been happening for awhile, it is not new with the latest VS update. We're using a TFS repository hosted on Visual Studio Online, i.e. our TFS repository is at COMPANY.visualstudio.com.
Frequently, when checking in, or attempting to shelve changes from the Team Explorer window in VS, I'll get an error message indicating I'm not authorized to access Microsoft-IIS/10.0. I've had reports of other developers experiencing this as well.
We've discovered the following workarounds.
Clicking the refresh button on the top of the Team Explorer window and then trying the operation again
If you have multiple workspaces, changing to a different one, then back to the original, then trying the operation again
It appears something is "stale" perhaps with the TFS connection and that refreshing it prevents the error message.
Hitting the refresh button over the Team explorer, resolved the issue.
I had a locked item. When I excluded/undo the locked item it went through.
Refresh TFS not worked for me
In my case the error disappear restarting Visual Studio
or me, it helped just to restart Visual Studio.
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 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.
"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 have visual web developer 2010 express and mysql/connector 6.4.3
When I press on the database explorer tab -> connect to database, I need to choose data source but I dont see mysql data source as I shold.
I've tried to reinstall it..
I have both visual studio 2008 and visual web developer 2010 express.
Btw, during the mysql/connector I only saw that he configured vs2008..
How can I fix that?
p.s.
I saw here that its not supported, is it true??
Thanks.
This is an old, but to answer your question I was having the same issue until I tried it on the ultimate version. It picks it right up. You just need to re-install the connector.
So short answer, yes. :(