I've created a asp.net mvc 5 app project (no app so far) when I go to http://localhost:12345/ it shows the asp.net default index page:
But if I go to http://development_machine_ip:12345/ from a remote machine it shows the unstyled page:
Note I am using Windows Authentication on an Intranet app. I am using the same credentials in both machines.
This issue is present in Firefox, Chrome an IE. The site is not being displayed in intranet compatibilitymode as suggested here
I've also set project folder permission to read and execute for all domain users and added the <meta http-equiv="X-UA-Compatible" content="IE=10.0" /> tag without success.
I am using IIS Express and Visual Studio 2013.
Thanks for considering my question.
SOLUTION:
the clue is to give the appropriate permissions to IIS_IUSRS. But until that it's easier to launch VS 2010 with administrator privilages.
Check this link provided in this question comments by #barry
Related
I am working on an ASP.NET website. I am trying to deploy the website on Windows 2003 server, IIS 6. The website works fine when I run using Visual studio 2010. but I am not able to deploy on IIS 6 and access the website login page.
I published the website and created a new Virtual directory in IIS 6 pointing to the precompiled website folder under c:\Inetpub\wwwroot\App-name folder.
I get the below error message when i try to access the website login page.
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
A name was started with an invalid character. Error processing resource
'http://myappservr.com/app-name/Login.aspx'. Line 1, Po...
<%# page language="C#" autoeventwireup="true" inherits="Login, App_Web_rmgltjnq" %>
-^
In IIS, under ASP.NET tab, I selected the ASP.NET version as v2.0. In IIS, under Web service extensions folder ASP.NET 2.0 is allowed.
Why the does the browser show the message is The XML page cannot be displayed Cannot view XML input using XSL style sheet when I access the aspx page from the IIS?
Please let me know how to fix this issue when access the website from IIS 6.0
Thanks
Ashok
The error you are receiving means that IIS is not processing the asp.net pages at all. It is simply displaying the HTML directly to the browser. The error you are getting is the same one you would receive if you opened the .aspx page directly in the browser from the file system.
Steps to make sure
the .net framework is actually installed on the server.
if it is, make sure it is enabled to be served. MS disabled many application development features by default to avoid servers becoming a potential viral attack vector.
Go to the Server Manager on the server
Select the Web Server (IIS) Role to show the details under the Role Services list ensure that the Web Server | Application Development | ASP.Net and .Net Extensibility nodes are Installed.
If not, select the Add Role Services options to add those and any other Application Development eatures you need.
If correct, you may need to run aspnet_regiis to update the mappings. Usually the -i or -ir options are most commonly selected.
I have website in VS2008. Created the Virtual directory in IIS 5.1. When I try and run the site to debug from Visual Studio I keep on getting:
Your Web service is now running.
You do not currently have a default Web page established for your users. Any users attempting to connect to your Web site from another machine are currently receiving an Under Construction page. Your Web server lists the following files as possible default Web pages: default.htm,default.asp,index.htm,iisstart.asp. Currently, only iisstart.asp exists.
To add documents to your default Web site, save files in c:\inetpub\wwwroot.
I have no idea why this is happening.
Can anyone help me?
If I understand correctly, it may be as simple as this:
In Solution Explorer, right-click on the page you want to be the default page and click "Set as Start Page".
O/S: Windows 7 ,Home Premium
I have just installed IIS manager Express from Web platform installer and Turned on the IIS7 feature from the Program Feature in control panel.
Q) I was playing with IIS Manager (inetmgr) I was able to view the Welcome page on typing localhost but after adding some sites and deleting them I'm unable to see any site hosted on IIS and even can't see Welcome page of IIS
Note: I was assuming IIS switched off ,but its running
Services.msc from start menu > run
Progress:
After trying Update2 from "Andrei Drynov" here is the sanpshot
Is there page iistart.html in C:\inetpub\wwwroot?
Is the default web site there and running?
UPDATE:
You can you can uninstall and then install again IIS components like Default document, if you really want that welcome page:
UPDATE 2:
I was able to reproduce your issue by creating another web site with site1.com as a host name in Site Binding and removing the default web site. Remove the host name there and you will be able to open the welcome page again:
Is the default IIS website running? that means in the IIS can be on, but the website can still be stopped...try restarting the website...and then try --- right click on website>Manage Website>Browse...
I'm evaluating Telerik's Sitefinity CMS. On my dev box (Win7 x64/IIS7), everything works great.
However, when I deploy the site to our Win2k3/IIS6 server, the backend system doesn't work correctly. According to fiddler, anytime the browser makes an AJAX request to a WCF (.svc) service within the application, the home page is being returned.
Any suggestions?
I've tried:
re-registering ASP.net
Re-registering WCF with
\windows\microsoft.net\framework\v3.*\wcf\servicemodelreg -i
Made sure that the .svc extension is allowed
Deleted and recreated the site in IIS
Argh. Suggestions?
You can find installation information and other tips on getting Sitefinity up and running by visiting the documentation.
This turned out to be related to the IIS6 application pool identity, permissions on the web folder, and having multiple authentication methods checked in site properties. By playing with those things I was able to get it to work.
As a test, I ran the site through the Sitefinity project manager app (using its integrated Cassini server), and everything worked correctly.
I have an asp.net website that has been running well in IIS 6.0. I very well remember the sites ASP.NET version was set to version 2.0 in IIS but i just checked and found the version set to nothing. If i click the site asp.net version dropdownlist in IIS, i can see two options(1.1.4322 and 2.0.50727).
The problem is i set it back to 2.0 and now the site can nolonger be accessed both remotely and locally.
And i cant set it back to "nothing" since the version dropdownlist only has two options( 2.0.50727 and 1.1.4322).
Any ideas what could be going wrong.
Below is what i get in the browser
The page cannot be found The page you
are looking for might have been
removed, had its name changed, or is
temporarily unavailable.
Please try the following:
•Make surethat the Web site address displayed in
the address bar of your browser is
spelled and formatted correctly.
• If
you reached this page by clicking a
link, contact the Web site
administrator to alert them that the
link is incorrectly formatted.
•Click the Back button to try another
link. HTTP Error 404 - File or
directory not found. Internet
Information Services (IIS)
Technical Information (for support
personnel) •
Go to Microsoft Product
Support Services and perform a title
search for the words HTTP and 404.
• Open IIS Help, which is accessible
in IIS Manager (inetmgr), and search
for topics titled Web Site Setup,
Common Administrative Tasks, and About
Custom Error Messages.
This is the culprit
http://blogs.msdn.com/b/webtopics/archive/2010/06/14/iis-6-applications-may-stop-responding-after-you-install-microsoft-update-kb-982666.aspx
It sounds like .NET isn't properly installed on your IIS website.
Try to open a command prompt, step into %windir%\Microsoft.NET\Framework\v2.0.50727\ and run aspnet_regiis.exe (use the directive -? for help). If you only run one IIS website on your server you can run aspnet_regiis.exe -i
Hope this may help you.
.net 1.1 and .net 2.0 don't get along well on IIS 6.0. You must run one of the frameworks in a different app pool - so, for every 1.1 website, for example, run it in a new app pool (other than the default).