Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
We have just started to use Windows Server 2008 R2 and IIS7.5 and I'm trying to move some existing sites across from our Windows 2003 box. I can get the sites running ok but am getting 401 errors for all the CSS / Images in the sites. Granting Everyone read access will solve this - but I'm not very happy doing this.
I've read that IIS7.5 makes use of a magical new 'account' and each Application Pool has its own account.
So far I have
Created a new folder in wwwroot for my website (kbank)
Copied the files in from another machine
In IIS7 created a new website (not virtual directory), this created a new Application Pool with the same name as my website. This is an Integrated Pipeline pool
In Process Model / Identity this is using ApplicationPoolIdentity and Load User Profile is set to True
Granted IIS AppPool\kbank read access to the root of the folder
Can anyone tell me how best to set up my websites.
2008 R2 IIS 7.5
Just as an FYI. After rebuilding servers and spending endless hours troubleshooting a 401.3 error after changing the AppPool identity to a domain account, we came to find out that a GPO was killing IIS. Make sure you test with a server in the "Computer" container and that no GPO's are changing restricted groups outside of Administrators.
In our case, NT Authority\Authenticated Users was removed from the local USERS group and it broke IIS complete.
Maybe you are just missing a small step. When you granted the account read access, did you check that it replaced settings in all subdirectories. Also it may require an IIS reset after changing the access rights.
I would check what is the exact status code of the 401 error IIS 7 Status Code
Once you know the exact error code, it will be easy for to troubleshoot the exact issue is.
I would also run Process Monitor and see if there are any "ACCESS DENIED" using the Filter.
Regards,
Vivek.
Related
We use IIS 7.
We have log enabled to be daily for all our sites. For new sites, I can see logs are created properly, but for old sites, the logs are just not there. From IIS manager, I can see the log is enabled, but for some reason, the logging stopped like one month ago.
We installed debugdiag on this server, will this software somehow hide or redirect iis log? Is there any register key I can check (other than what I can see from IIS manager)?
Many Thanks
Sounds like an NTFS permissions issue with the target logs folder.
When restarting IIS, you will see entries in Event Viewer stating it could not create the log file.
See this question and check your folder permissions.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
Hi All,
Actually I have a web application build using classic asp and vb script, along with MS-Access 2003 hosted on IIS 6.0. It is running fine.
Now I have shifted it to on IIS 7.0 and database MS-Access 2003 to 2010.
The Login Page is running fine, and also it's easily get login when I try to login. But after login when I try to access some others pages through click a button, it shows error 500 Internal Server Error.
I have given security this application to the everyone level but still it is showing error.
I am using database through DSN. I can not say that there is any DSN configuration error or mistake I did, because login page is working fine which gets user id and password from my database.
What type of issue might be there?
solved. Now I have given my Intepub\mailroot\pickup forder to appropriate permission.
I recently installed webmatrix on a windows 2008 machine.
I installed dotnetnuke using webmatrix, I visited the site using a browser on the server, finished installing the site, and everything works just fine.
I than created a site in IIS, and pointed it at the folder where I installed dotnetnuke.
When I visit the site using my domain name and on port 80 with a browser on my server, it takes me to the install page. When I visit the site using a remote computer, it says "This site is currently Unavailable Please check back later". Yet, when I visit it on iis express, it works perfectly!.
What is wrong?
thanks!
There are a number of things that could be going on at this point.
Incorrect permissions - Ensure that the ASP.NET Worker Process has full permissions to the DotNetNuke directory. (With IIS Express, you are using your user account IIRC)
Incorrect database access - Ensure that the connection information is correct for the database. As with the above, if the connection for example has a "Integrated Security=true" option defined, you will need to either change this to a SQL account or add the ASP.NET worker Process user to have permissions
It could be a missing Portal Alias, but the current versions of DNN don't have the same issue as you use to.
ALso make sure that the UsePortNumber option in the web.config is set to false.
We have an old ASP.NET application hosted in IIS6/Win2k3. It's a document generation application that uploads the documents to SharePoint 2003. The application uses an application pool under the user sharepointservice, which is the administrator of the SharePoint site. The web application, which has been recently migrated to .net 2.0 from 1.1, uses NTLM authentication to identify our intranet users.
As the IT administrators are on holidays, I, the developer, has been given local admin rights to the Win2k3 box. The issue is, whenever I deploy the website, though the documents are uploaded appropriately to the SharePoint site via the application, the users are not able to download them. The error is
HTTP Error 403 - Forbidden: Access is denied
I know the IT guys use a service account, not their domain user accounts.
I have already tried to modify the permissions in IIS for that website. I even put Everyone and <Domain>\Users to have read access to all of those folders, to no avail. I've scoured the net, there are no definitive answers. Am I missing something else?
I hate answering my own question, but this did it for me:
The application pools for the SharePoint site were modified from the default. So I reset them, including the AppPools for _layouts, _vti_bin, and _wpresources. Their AppPools are now the default, and are the same.
This link gave me the lead.
You are probably being prompted by permissions for the file system. Check the directories where IO is happening and make sure the user sharepointservice is using in the app pool has read/write permissions.
I just had this problem and solved it after following these instructions:
http://support.microsoft.com/kb/2543306
It seems the webapplication took so long that it hadn't created everything correctly when the IIS timed out. So I was receiving strange errors like yours.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 14 years ago.
Improve this question
I have an .asmx in a folder in my application and I keep getting a 401 trying to access it.
I have double and triple checked the setting including the directory security settings. It allows anonymous. I turned off Windows Authentication.
If I delete the application and the folder its in, then redeploy it under the same application name it magically reapplies the old settings.
If I deploy the exact same application to a different folder on the server and create another application under a new name and set up the directory security setting again it works!!!
How do I get IIS to forget the setting under the original application name?
After deleting the first application in IIS and its associated files on the disk, try restarting IIS (or your server if possible). Then come back and recreate the whole setup.
Eventually I got it working again. By deploying to a different folder and recreating the virtual folder / application to it.
I am not sure how that makes a difference but at least things are working again.
I ran into a similar situation with asp.net pages. I had Anonymous on and Integrated off for a virtual directory, but one page was the opposite. Everything worked fine until I went to the one special page, then my post backs stopped working and I couldn't log out of the site until I deployed to a new virtual directory.
My eventual solution was to enable anonymous and integrated for the entire site and just turn off anonymous on that one page.