We recently migrated from TFS 2008 to Tfs 2015, The code and the build and WorkItems window was showing only blank window .
how do we fix this
Team web access is allowed for all
Licenses are set up to allow web access all features
Quite Strange and very difficult to figure out.
I tried all possible options.
IE Browser gave an error that some of the features are not configured.
But I was able to access that in VS 2012 , Vs 2015 client IDE's
so I wasn't convinces by the browser Tip.
**
Finally I used F12 in IE to find that the Options verb settings was denied in IIS 8 in Win 2012, where our TFS 2015 App Tier server was hosted
**
**In IIS 8, Go to “Request Filtering” under the IIS website and check the default setting was set to deny any verb that’s not listed explicitly to be allowed.
Issue was resolved on allowing the verb “OPTIONS” explicitly in that tab.
see the Picture attached for reference
Looks Like TFS web access needs that verb and we would see blank page of 404 error in new installations of TFS 2015
**
Related
So, we have a web app we've migrated to .net core, and while it runs fine in Visual Studio 2017, because Visual Studio uses its "launchSettings.json" file to configure how IIS Express will work/launch - I, for the life of me, cannot figure out how to get VS Code to run the project. The problem is, we use HTTPS only and have always just let IIS Express used the self-signed locahost cert to allow this, so when debugging the site locally, we'd always use https://localhost:44300. As stated, this worked fine when entering this url in the launchSerttings.json file for Visual Studio, but VS Code does not use this, and the only answers I can find on this always refer to having to use the Kestrel Server's .Listen() method and used a self-signed cert and password to allow the use of an HTTPS port. 1) this seems just silly that I'd have to add this "test" code to run it locally, because I don't need it when we deploy to Azure, as Azure manages the certs and url for us. 2) Visual Studio 2017 does not need any specification on Kestrel to make this all work. So, I have hard time believing there isn't some extension, or process to achieve the same thing in Visual Studio Code that Visual Studio is doing under the hood to allow IIS Express to communicate with the .Net Core Kestrel Server.
Combing through the all the documentation suggests that the ASPNetCoreModule is what handles this communication for IIS and Kestrel, so, I would hope/guess there has to be some way to configure the web.config file's tag to include something that would make this work.
I've previously used and tried other IIS execution extensions in VS Code, but those focus on elements in the project's web.config to boot IIS which are no longer present in the web.config due to it being a .Net Core app. I had been successfully running the web app with the IIS Express Executor extension before migrating to .Net Core when the web app was a .NET Framework 4.5.2 app
So, the end goal is that I need to be able to go to https://localhost:44300 in the browser, and have our site work, but I don't want to have to add any sort of test-cert into the Kestrel config in the Program.cs or Startup.cs files. If there's no way to do this, then that will be really disappointing considering Visual Studio makes this seem like it should be very simple.
Thanks for the help.
Was able to get this to work using the following steps.
1) Install IIS Express executer in VS Code or any other similiar extension that wraps around dotnet commands
2) Download Process Explorer from https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
3) Launch Visual Studio IIS Express as you would normally
4) Open Process Explorer (may need to launch as Admin) and locate iisexpress.exe -> VSIISExeLauncher.exe
5) Right click VSIISExeLauncher.exe and click properties then locate the "Environment" tab. Inside the environment tab you will see 2 variables: LAUNCHER_PATH and LAUNCHER_ARGS. Copy both of these variables and values.
6) Next locate the configuration file for the extension you installed in VS code (mine is launch.json inside the .vscode folder in your project root directory). It will likely have an "environment" or "env" section for adding environment variables to the launch arguments. Add the two arguments copied from step 5. These vary from person to person so the value of the arguments will be unique to your machine.
7) Launch IIS-Express from vs code. My particular command for this is "IIS-EE: Start IIS Express Server" but will vary based on the extension you installed. You can hit F1 to launch commands.
Visual Studio itself uses too many tricks under the hood to make you believe it is simple. However, it is not.
I documented all necessary details in a blog post,
https://blog.lextudio.com/how-visual-studio-launches-iis-express-to-debug-asp-net-core-apps-d7fd3677e3c3
And if you follow the steps manually, you should be able to launch IIS Express the same way VS does, and then use that in Visual Studio Code. I know there is some VSCode extensions trying to integrate with IIS and IIS Express, but I do hope those authors spend more time learning such integration and improve their extensions to fully support the scenarios.
I have installed SQL Server 2012 on my Windows 10 computer. When I try to access Reporting Services via the Browser such as Chrome or Firefox, It prompts me for username/password (In which I do enter) but then it gives me an error
(Reporting Services Error: The permissions granted to user
'ComputerName\User' are insufficient for performing this operation.
(rsAccessDenied)).
I have tried many solutions such as Internet Options and SQL server management studio. I have spent most of my time trying to figure this out but have given up hope.
Assuming you are trying to access Report Manager application (and not the Report Server) try this:
Run Internet Explorer as Administrator
Browse to Report Manager URL e.g. http://localhost/reports
You should see the Report Manager "home" page
Go to the Security settings for the home page and explicitly add your user account with the "Content Manager" role
You should now be able to browse to the home page with IE or Firefox. Note that Chrome is not a supported browser for SSRS 2012.
I struggled doing this with IE now officially unsupported (with chromium edge installed). Everytime I opened IE it would close immediately. To get around this, create a Windows Shortcut (lnk) file with this command:
"C:\Program Files\Internet Explorer\iexplore.exe" -extoff http://localhost/Reports
NOTE: The shortcut must be opened as Administrator.
I need to add a web reference in Visual Studio 2012 (because service reference generates a blank reference CS and I have given up after hours of googling).
When I go to add the web reference (add service reference → advanced → add web reference) and enter the WSDL URL I get the IE Notification Bar in the dialog with the message:
To help protect your security, your web browser has blocked this site from downloading files to your computer. The option to "Download file" does not work.
I've changed IE security settings to minimum and added the domain to the list of trusted sites but did not have any effect. I also uninstalled IE10 completely and still get the notification bar. I am using Windows 8.
Anyone shed any light on this or had any success adding a web reference in VS 2012?
If you can download the WSDL with your browser, download it and save it to a file. You can then reference it from Visual Studio by pointing it to that file. Or you can use svcutil.exe or wsdl.exe to generate a proxy from the commandline.
I'm stumped. There are several threads out there that reference a similar problem, but not the same one. I'm trying to get a simple WCF service up and running in Azure, but my problem is happening before I even deploy. I'm following this article:
https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-create-deploy/
Which says to create your project, build the "Hello World" service interface and class, and then start your project locally. I get a 403 error when I try to start my project.
The only step I'm not following exactly is that I don't have a "Start Without Debugging" option (I'm using Visual Studio Express Web Developer), so I just push "Start Debugging."
Why would I get a 403 error on my own machine? I am running Visual Studio as Administrator.
On the WebRole project right click on your .svc (Service1.svc) and choose "Set As Start Page" And then run the project. Make sure to do this on the WebRole project not the Azure Cloude Project.
Is the Azure project the default project or is the WCF Web Role? If it's the role itself, that may be your issue - it's trying to access the root of virtual directory containing the web service versus running the cloud app in the local emulator. If you browse to http://127.0.0.1:81/Service1.svc in a new browser window do you still get the 403?
It seems VS has lost the its project settings. Bring up "Properties" page on the web service in VS. Go to the "Debug" tab. Under Servers/Virtual Path: my configuration was set to just "/". Put the name of your server back in there "/Service1.svc" and it should work from the debugger now. This fixed the problem for me.
The problem went away when I upgraded to VS 2010 Pro. I never fixed it on Express, but after upgrading the problem was gone ... I had the "Start without Debugging" option in the Pro edition, so I suspect that the problem may have been specific to Express.
I've just got to the bottom of this, and couldn't find the problem documented anywhere, so thought I would post the question (and answer) for future reference:
I've just installed CruiseControl.NET on a (virtual) Windows Server 2003 and I can't access the Dashboard. CruiseControl (ccnet.exe) runs fine, and IIS6 is up and running, and the the CruiseControl installation installed the Dashboard app under Default Web Sites as "ccnet". It's pointing to the dashboard folder, and the dashboard files are visible in IIIS Manager, but when I try to access http://localhost/ccnet I get a 404: Page Not Found error. I get this whether I use IE or Chrome, or try to Browse the site from IIS Manager.
What's wrong?
ASP.NET was Prohibited, and needed to be Allowed - in IIS Manager, click on Web Service Extensions under the server, select ASP.NET and click Allow.