Unfortunately I have deleted the 401 page at application level in IIS..
I have created a new one there back.. type of that page is local instead of inherited..
How should I get it to inherited at app level..
Tried resett but no luck
Unless someone has changed the delegation configuration for your Error Pages, the changes made to your Application Error Pages will be made to the Application's Web.Config file.
Click your Application on the Left Side of IIS Manager.
Next Click Explore in the Top Right corner to open Windows Explorer to the Physical Path of the Application.
Open the Web.config in NotePad.
Locate the tag for < httpErrors>.
I imagine you'll only have two entries one for Remove and one for add. If this is the case, delete everything between < ttpErrors and the closing < / httpErrors>. (Feel free to make a backup of the web.config if you're nervous).
If you have something other than that in the web.config or you don't find it, post back with what you find.
Related
I think I must have changed something to IIS default website settings. Now I cannot even browse IIS default website. Even if I create new website, when I browse, it always go to http://localhost/webpages/home.aspx which became the default page for all website I added to IIS. where can I change that setting not to call that http://localhost/webpages/home.aspx by default.
any pointer would be appreciated.
if I understand your question correctly.
These steps should help you to produce the result(s) you require:
1 Create your project in VS.
2 Right click Project name.
3 Select Properties.
4 Select Web.
5 Under Server there is a dropdownbox. Here the default is IIS.
dropdownbox
The usual choice as far as I know is between IIS and localhost.
6 Click the Create Virtual Directory button located to the right.
A message box should pop up saying Virtual Directory successfully created!
Here is a link that may be more helpful. https://www.youtube.com/watch?v=k5RKfOEpOGk&index=9&list=PL6n9fhu94yhXQS_p1i-HLIftB9Y7Vnxlo
I have an existing application under the "Default Web Site" that is functioning but want to move it as its own "Site". What is the best approach to this as the functioning site has a lot of configuration to it.
I've tried creating a new site and copy/pasting the folder contents(c:/inetpub/wwwroot/application) over but that does not work.
In theory, if I could simply drag the application out of the "Default Web Site" and drop it to the "Sites" folder, that would be nice...
Any help with this would be greatly appreciated! Thank you!
All you have to do in IIS.
Right Click on Sites --> Add web Site (Make up a name for it)
Just set the physical path to the location of the application (You don't even have to move the application)
If you have an old website you want to move to a different folder (like on a different hard drive w/ more memory), you can:
copy the folder to the website to the new location (making sure to reset all the file permissions b/c they are often not automatically copied),
open the site in IIS,
click "Basic settings" in the "Actions" panel on the right hand side of the screen,
change the "Physical path"
click ok
Do an app pool recycle afterwards to ensure everything takes effect
Using asp .net MVC 4.0 , razor , VS2010 , IIS5.2 , windows Server 2003
I have built an application which i want to publish in IIS. what i did is listed below:
Cleaned then built the solution.
right click on project file and clicked PUBLISH.
publish method : File System
Target Location : C:\Inetpub\wwwroot\testing
then publish.
Then i went to IIS and got my site in Default web sites. happy :). Then i did:
right clicked on testing(my app) and open properties.
In the tabdirectory everything goes fine.
in asp.nettab, i set asp .net version 4.0.30319
here is a little confusion, I set home/index as my default content page in documentstab
then I right click testing and clicked browse. And it shows :
Most likely causes:
This website requires you to log in.
This error(HTTP 403 Forbidden) means that this program was able to connect to
the website, but it does not have permission to view the webpage.
a short summury what i got as error message. This is my fist mvc application and first hosting. What is my fault here? what should i do now?
I had the similar issue. Please try the following:
A. Suggestion below from Microsoft Technet helped me:
The solution is to ensure that the Authenticated Users or \Users group (which usually contains DOMAIN\Users group) has Read & Execute, List Folder Contents and Read permissions on the /BIN folder below C:\inetpub\wwwroot\wss\VirtualDirectories{Sitename80}. Follow the steps listed below to grant the required permissions:
Open Windows Explorer and navigate to the /bin directory of
your web application
Right-click on the folder and click on Properties
Go to Security tab and click on Edit
Click on Add and add the local server group Authenticated
Users or < SERVER NAME >\Users (this usually contains
DOMAIN\Users group).
Select the Read & Execute, List Folder Contents and Read
permissions (if you are planning to add Everyone to the /bin folder,
grant Read permissions only)
Click OK to apply the new settings
NOTE: you may need to to it after every Publish, as permissions somehow may get reset.
B. In VS - set the default page for your website, or try navigating to specific page as opposed to simply opening the website with only the site name.
I know it sounds dumb, but that also was the problem for me
after publishing your webiste to IIS, navigate to http://myServer/mySite/somePage instead of http://myServer/MySite
A developer just send me a running website files from IIS directory. I want to know if I can run the website on my PC. The file contain "Default.aspx" file, which I assume is of some importance.
I want to know if it is possible to run the website on my PC, I have installed IIS and I placed the file in the wwwroot folder, but unfortunately I dont know how to proceed from here.
Can someone please point me to the right way to continue with this task.
Thanks in advance
First time use of IIS
Now that IIS is running on your system, it should have defaulted to running on port 80. You can test this out by going to http://localhost/
The file you have placed in the wwwroot directory Default.aspx is an ASP.NET application. You need to go to IIS and convert the directory it is stored into a web application.
Now when creating web applications, it is better to create them in another folder other than your wwwroot folder, and in the case of this tutorial it is easier. Move your Default.aspx into a folder named 'webapp', or something of the like.
To convert it into an application, do the following:
In the Server Manager, expand the
'Roles' item in the tree
Expand the 'Web Server (IIS)' item
Click on 'Internet Information Services (IIS) Manager
In the window on the right hand side, you will need to open up your server. In my case, my server is called WIN2008R2. Your server name will be located inside the 'Connections' pane. Expand your server in the tree
Expand the 'Sites' item
Expand your newly created site. There should only be one there, and the item will have a globe next to it
Now right click on your 'webapp' item which will have a folder next to it, and click 'Convert to Application'. Then leave all the properties the same in the window that comes up and click OK.
You have now created a new web application. By going to http://localhost/webapp you should see it working.
You need to configure IIS to host an ASP.NET website.
You can find information about configuring IIS here: http://msdn.microsoft.com/en-us/library/ms178477.aspx
Another option is using the Cassini web server (instead of IIS). You may find it easier to configure: http://ultidev.com/products/cassini/
I'm making some changes to a legacy classic ASP application. I've made the changes locally, and now I want to copy the changed files to the server. At the same time, I need to download the Access database, add some fields to some tables, and upload it again. For this reason, I need to be able to stop visitors from modifying the database while this is happening.
My main question is, what is the best way to setup a quick "Down for Maintenance" page that will be shown immediately and no matter which page the visitor requests. The application is already established, so I'd rather an answer that didn't require me to rework the application's architecture.
My second question (maybe this should be a separate question):
Is there a better way to add fields to a db table than to copy it down, modify, and stick it up again? Please forgive if that's a dumb question - I'm new to ASP - new to Windows too.
I only have FTP access to the remote server.
Thanks.
two ways:
1
if you do a server-side include in every asp page you can do a response.redirect in that include to /upgrading.html
2
in global.asa you can do a response.redirect in the session on start event. THis is probably the best way. Will only work for .asp pages, not if the client comes to a .html page.
Do you have any control panel access to the site at all?
When I used to run a number of ASP Classic sites I often turned them off for the five minutes required to do what I needed.
Rude to do to your visitors I know.
As others have said you could redirect to a page, but that won't stop people visiting static content in html pages, but then that probably won't matter, at least it stops them making changes to the mdb whilst you download it.
It's a pity that ASP.net's app_offline.htm doesn't work for ASP classic.
Another option I used to use was to create a default.htm file that had the offline message, and the way IIS was setup default.htm overrode default.asp, so simply uploading default.htm changed the homepage. This of course doesn't stop anyone using any of the other .asp pages.
So no real answer! Sorry.
If you have just FTP access to the server (and no control over the IIS) just insert a response.redirect to the "down for maintenace" page in top of all the asp pages, and remove it when the update is completed.
The changes to the database can be performed with the ALTER TABLE statement.
With regards to the "Down Maintanance" page issue you can and taking mapache's idea a step further if there is an included file (for a header) in each of the pages you can put the Response.Redirect in that one file and upload that in place. This will avoid making changes to all pages.
Another option is to upload a temp html file which will be found first by IIS. In IIS you can set which page name.ext are looked for in a domain/folder. For example when you browse to www.example.com you don't specify the page you are looking for so it could load index.html or index.htm for example depending on setup. It will depend on your hosts configuration setup, but a bit of trial and error I'm sure you can find out which one they use. Common ones for IIS are default.htm, default.html, index.html and index.htm. You can then put it in each of the folders in the website (not ideal I know) and then carry out your maintenance.
When updating databases you can run a migration script, written in sql, to update the schema and data of the db. As you only have FTP access this will require some sort of page you can paste the sql into and run. This however opens security issues so downloading the db, making the changes and then uploading again is probably easier. In addition to doing it this way you can also save the file and you'll have a backup :-)
Hope this helps.
Better than an include file, just use the Global.asa.
In the Global.asa's Application_onStart, add
Application("Offline")= True
at the top of all of your ASP files, add
If VarType(Application("Offline")) = vbBoolean Then If Application("Offline") Then Response.Redirect "App_Offline.htm"
(The double-if gets around the lack of VBScript's short-circuit operators, and therefore any data type errors.)
You could even set the Global.asa code to
Set fso= Server.CreateObject("Scripting.FileSystemObject")
Application("Offline")= fso.FileExists(Server.MapPath("App_Offline.htm"))
Set fso= Nothing
Which would enable the offline page if it exists, like ASP.NET. However, the application start code is only reparsed when the server is reset (using iisreset), or when the Global.asa file is modified, merely adding the App_Offline.htm will not be enough.
Add below code in web.config
<?xml version="1.0"?>
<configuration>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
</system.webServer>
</configuration>
And place app_offline under root folder. This will work.