I get the error below when trying to run my asp.net mvc solution:
This error is located in my WCF service.
My question is: how can I see the trace logs of the IIS server?
Below is the configuration of my Visual Studio project:
Thank you for your help.
You need to set up Logging in IIS from IIS not Visual Studio.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/d29207e8-5274-4f4b-9a00-9433b73252d6.mspx?mfr=true
Related
I have an asp.net mvc5 application that I created about a year ago and it was working. I did it in Visual Studio 2015 and then published it to a production server. I just did an update to the application and republished it. I now get an error when the application tries to save I think. The error, " Error. An error occurred while processing your request." does not tell much. I turned off Customerrors in hopes of getting more information but I still get the same message. Not sure how to find out why it is no longer able to save. I have checked all the account permissions based on other site suggestions. Is it possible some recent updates to Server 2012 or Sql Server 2014 require additional changes? Any help on how to find the actual error message would help a lot.
Thanks.
After a lot of work on the Visual Studio I realized the VS2015 was very out of date. I tried to run updates on it but it would not succeed. That is why my apps would not update. Visual Studio was the problem all along. I finally moved to Visual Studio 2019 and then upgraded my applications from ASP.net mvc5 to ASP.net MVC Core. I realize now it is important to update the Visual Studio on a frequent basis. If you wait too long it may not allow for an update.
I have an Azure Cloud Service solution in Visual Studio 2017 which I debug with Emulator Express.
I'd like "migrate" from Visual Studio to Visual Studio Code. I mean that I'd like to be able to run/debug my cloud service(web role project) in VSCode without the use of Visual Studio at all.
My solution has two project:
Service project - contains .csdef, .ccproj and multiple .cscfg.
Role project - contains the .csproj file and the rest of the sample web role project.
I've tried:
I'm building both of the projects with msbuild, the same way it's been built in visual studio. The problem is running the site locally.
Run a local site with IIS Express VSCode extension and configure the web role project root as site root. It didn't work, I tried to browse the site but I got a notification that the folder of the site can't be viewed as a directory. When I think of it this option is missing all the configuration that is defined in the Service project so how is it suppose to work? Does IIS Express can run an Azure cloud service app locally? Maybe I configure a wrong path?
I've tried running csrun.exe command multiple times with different arguments. Something like this:
"C:\Program Files\Microsoft SDKs\Azure\Emulator\csrun.exe"
/run:./csx/Debug/roles/WebRoleProject/approot;./ServiceConfiguration.myconfig.cscfg /launchBrowser
/launchDebugger:%systemroot%/System32/vsjitdebugger.exe
It gave me the following error:
The compute emulator had a error: Can't locate service descriptions..
I also saw here that compute emulator(csrun.exe) needs visual studio opened as administrator, so maybe it's not possible to run it without it..
I’ve verified this question with the Azure Cloud Compute team and this is not supported in VSCode, they only built an extension for Visual Studio.
I'd been working on this for many hours.
My problem is this -- I can view our web application on both debug and release using IIS Express in Visual Studio 2013.
But when I try to publish it using Web Deploy then load the web app in browser (Chrome) -- it loads but it cannot find the CSS, JS, Fonts and some images.
What may cause this problem? While using Visual Studio 2013 debug or release mode in IIS Express all works smoothly.
Thank you.
After publish your web application, you must have to change the path of css,images etc.
Hope it will help you.
I copied my project over to another computer to open it and in visual studio and got this error:
http://localhost:51278 : error : Error opening web http://localhost:51278. The Web site 'http://localhost:51278' could not be found.
I have looked on the link here stated in other answers: http://support.microsoft.com/kb/326497
But I fail since I cant find a (Projectname.vbproj.webinfo) File, all I have is a .SLN File.
I set up IIS and dragged the project into the root at (C:\inetpub\wwwroot). Upon opening the file in visual studio I know get this error. Any ideas?
EDIT:
I ran visual studio as ADMIN and got this error:
http://localhost:51278 : error : Error opening web http://localhost:51278. The Web Site 'http://localhost:51278' is configured to use IIS Express as the web server but the URL is currently configured on the local IIS web server. To open this Web Site, you must use IIS Manager to remove the bindings using this URL from the local IIS web server.
This might be a stupid question, but I have a problem with Visual Studio 2013 and IIS (not Express), that the Visual Studio debugger by default uses IIS Express (iisexpress.exe) to debug code. But I do not want that, but I want to use IIS installed on my computer (w3wp.exe).
I succeeded in debugging with IIS by using Attach to Process... and then selecting All Users and then picking w3wp.exe as a process. But I need to do this every time I start debugging. Is there a way to use IIS by default? In Visual Studio 2012, everything worked well, but in VS 2013 I cannot find an option to use IIS (w3wp.exe) by default.
I am debugging a Web Site ASP.NET 4.0.
Thanks for any help!
If your website project was opened via IIS, it should debug the IIS process automatically. If your site exists in IIS currently, you should be able to find it via File -> Open -> Web Site.
If you opened an IIS Express based website project (or via the file system, which uses IIS Express by default), then run the site through IIS, VS doesn't know that the site is running in IIS.
In order to get this working on my setup (VS2013, IIS7, Win7) I needed to go into IIS Management Console and manually enable Windows Authentication.