This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
The layout page “{path}” could not be found
I published the site to local IIS server using "Filesystem Profile". After hitting through local url from IIS, web site does not find master page e.g. "~/Views/Shared/_Layout.cshtml"
The same website runs perfectly from the vs-2010 on same machine.
Thanks buddies for reply.
Actually I was trying to setup on Win-2008-R2 with IIS 7.5.
There was an issue with permissions. The site is configured with app pool .NET 4.0 which runs under NetworkService account. Giving acccess right to "NetworkService" for website resolved the issue.
Another question addressing the same issue:
The layout page "{path}" could not be found
Another link for configuration:
http://learn.iis.net/page.aspx/624/application-pool-identities/
Related
For the last year we've been working from home, and using VPN to connect to the office network for program updates.
Lately we've decided to try to find away to remove the need for that connection, and I would like to remove the need for any kind of file share, as replacing the VPN with a different VPN seems silly.
I know that VS can make a deployment web page and upload it to FTP, which solves half the problem, but I also don't want just anyone who finds the webpage being able to download and install the app.
We have a web server running IIS, and we also have a sharepoint site on office.com
If I install it to IIS, is there a way to secure it to our employees with azure active directory?
Is there a way to put it on the sharepoint site, which is already secured?
I just haven't found good resources to solve either problem.
For the question of is there a way to secure it to our employees with azure active directory.
If you want to do it in IIS level, I don't think it can be implemented. But we can do it in application level. You can refer to this document about how to develop your application with Azure AD.
This question already has answers here:
How to enable external request in IIS Express?
(27 answers)
Closed 1 year ago.
I want to access the site from another machine, like 192.168.1.11:10369
I found a solution for it, that is: http://bendetat.com/access-iis-express-from-another-machine.html
It's working well if I run the project in Web Matrix
But doesn't work from Visual Studio and showing Error Bad Request.. http://prntscr.com/ifz2jq (But it is working fine as http://localhost:10369/)
What should I do.. so that it can work from VS through IP address, as it is working good in web matrix and localhost/
Try like this:
iisexpress-proxy 8080 to 3000
source: stackoverflow.com/a/29971694/11600278
I've recently had a name change to my PC and rebooted. Before this change, I could run my MVC3 project from VS2010 using IIS 7. After the name change I getting:
Http Error 403 Forbidden Version Information: ASP.NET Development Server 10.0.0.0
I realise this could be a number of things so I'll try, in detail, to describe what's going on.
IIS
My IIS reverted back to v6 so I loaded 7 and set my DefaultAppPool to use .NET v4.0.
Security has all permissions for my account.
Request Filtering has 'Allow unlisted file name extensions checked (another answer on SO)
I'm using FireFox 24.0
VS2010 hasn't changed as far as I'm aware.
I'm not very familiar with IIS which, seems to me, is my problem so please bear this in mind if you decide to help. I'll gladly provide more information if needed.
thanks,
Paul
Do you actually have IIS7 installed or are you using IIS Express or Cassini?
I'm pretty sure that you'll be able to get things going again if you use the aspnet_regiis command.
Navigate to your .Net folder and run the following command aspnet_regiis -i
This isn't the answer but rather a different question. The problem wasn't IIS, the problem is with FireFox. I changed the default browser to Chrome and my app runs as it should.
Simple answer - I changed windows authentication password which wasn't updated in firefox. I changed the password to be in sync and it solved the issue.
I'm working on the following tutorial in the Windows Azure website:
https://www.windowsazure.com/en-us/develop/net/tutorials/web-app-with-sql-azure/
(also: go to windowsazure.com, click on the "Develop" heading, click on ".Net" under languages, under "Create Your First Application" -- click on ASP.NET MVC Web Application with SQL Azure)
I can run the application in the Windows Azure emulation environment on my development machine. If I change the connection strings to the production database, the app works in the local development environment.
However, when I deploy the application to Azure, I get an error message: "Sorry, an error occurred while processing your request." This appears within a rendered page, so I think the request is getting to ASP.NET.
I believe the problem I'm having is with allowing the production app on Azure to connect to the SQL Azure database.
I believe it is a firewall issue, but haven't been able to determine what the IP range needs to be. (I previously thought the problem would be with me running VS 2010 in a 32 bit environment, with Windows Azure as a 64 bit environment, but we deployed the sample app from a 64 bit environment and had the same issue). For additional details, here's my previous posting on MSDN to a previous inquiry on the same issue: http://social.msdn.microsoft.com/Forums/en-US/windowsazuretroubleshooting/thread/23afb5e3-e2ee-4444-aabb-7001ae6c6e6a/#af5284c0-ef4b-4193-b912-d4b7adfb5d21
Thanks for any assistance you can provide. I really want this sample app to work!
Update: Got the tutorial to work on a different computer and fresh 64 bit configuration, pointing to a different data center.
I got my hands on a new laptop with 64bit Windows 7 Home Premium , and installed Visual Web Developer 2010 Express, all of the most recent Azure and MVC SDKs. Seems like what I thought was a firewall issue, could have possibly been issues with database connectivity at the North Central data center. (I'm speculating, and will still need to test my original configuration against the South Central data center to see if this is actually the case. But, the North Central data center was not an available choice for hosting a SQL Azure database (3 month subscription), and here's a link to a discussion of this on another thread:
http://social.msdn.microsoft.com/Forums/da-DK/ssdsgetstarted/thread/7b181eef-ccd1-4090-80d1-0853059d166f
As mentioned above, the checkbox "Allow other Windows Azure services to access this server" needs to be checked, and both the service and the database need to be located in the same Windows Azure data center.
As #veblock suggest, you may try switching off the custom errors to see the actual error.
Meanwhile, the "IP range" that you seek for enabling firewall rule for your role is just a checkbox away:
You just need to check that "Allow other Windows Azure services to access this server" checkbox. The entry "Microsoft Services" with IP range of "0.0.0.0 - 0.0.0.0" will be automatically added. This is an internal entry and Microsoft keeps track of their own IP ranges, so that any Windows Azure data center will be able to access this SQL Azure Server.
But, yes, you can also check the real error message, by either Remote Desktopping to the instance, or by disabling the custom errors. There is a small chance that the ASP.NET MVC is also not fully installed in the Azure Instance. The easiest way to eliminate this problem would be by right clicking on the web application project and select "Add deployable dependencies", then chose ASP.NET MVC.
Thank you for your help. I have also hit this issues and spent several hours to debug what was going on since everything worked as expected in the Emulator, but won't work in production. After I have moved my hosted service and the database server to be in the same region, the problem went away.
In the original sample, it was also noted that it was important to ensure both are in the same region, but it mentioned due to performance reasons only, but for me it won't work at all.
"
IMPORTANT: Pick the same region that you choose earlier when deploying your application. This will give you the best performance.
"
I have a asp.net 3.5 web application which is deployed on server 2003 and IIS 6. After running fine for a few weeks it goes "Down" and by down I mean that when I try and access it the browser looks like it's loading but never actually serves the page. After an IIS reset it loads quickly again.
My question is what are the steps and tools I should use in tracking the root cause?
First point of interest would be the event viewer, second the iis logs. If you still do not find the error then performance counters could help you out there.