I have a problem which I cannot solve after some days. Simply, we have a web application which should run as a domain user (domain\user). We can do this in IIS (ver 8.5) manager in one server (statging) through application pool settings but when we do the same on another server (production) it is not working.
By not working I mean : If you browse that website and come back to the application pools tab, you see that it is stopped! and you receive HTTP Error 503. The service is unavailable. in the browser.
I have tried many things and solutions on SO but no success so far.
but when we do the same on another server (production) it is not working:
1.) Check Website Browsing Directory if enabled.
2.) Check Framework in application pools.
3.) Is your IIS set up correctly?
Hope it helps
Related
Every time I try to publish a website, it runs fine but when the website opens up it gives me a,
"HTTP Error 503. The service is unavailable."
Everywhere I look on the internet talks about it being my application pool but that seems to be running fine. I think it may be my web.config file but I'm not entirely sure.
PLEASE can someone help me.
"PICTURE OF ERROR BELOW"
Make absolute sure the App Pool is running
Goto WinKey+R (Start > Run) type in InetMgr, press enter.
Left side, Connections, expand your computer or the server in question.
Select Application pools.
Start all pools that have their "Status" as Stopped.
Make sure the site is set to the correct pool
Not all sites are assigned to the default application pool, in this case, in the left side expand sites, find your site, expand it. In the right column, click Basic configurations.
Edit the application pool there, go back to the first block and make sure your newly assigned Application Pool is running.
Test it
Select your site again, In the right side, there is a Browse site group, click on Browse *:80 (or something like that, this should do it).
Check permissions on site's folder.
Go to your site folder and give full permission to NETWORK SERVICE.
Make sure Application Pool service is not disabled in windows services.
If everything else fails, go to Services.msc and set the service related to your app pool to Automatic (maybe you or someone disabled it for some reason, who knows).
Reinstall IIS
Go to Control panel > Programs and resources > Install Windows Resources, find everything related to .NET, ASP.NET and install. Check all leftover boxes from IIS and subselects.
If this fails, uninstall it completely then install it again.
Let us know if any of these work.
This is most times caused by Application pool which has been disabled or because the application pool identity is invalid.
Go too IIS > hostname > Application Pools (Observe the Application is stopped)
Right click and go to Advance Settings
On Identity Select an Identity Pool from the drop-down list (possibly change the identity already selected by default)
Restart the Application pool
To set up an Identity Pool to select from follow this link
I am getting a "Server Unavailable" error message when I try to access a web application externally, but I can access it fine internally. It's got a message for administrators telling me to check the event log, but there's nothing there. Another thing, this is a work server, so I'm not exactly sure if they're using another firewall, but the Windows Firewall is disabled and the McAfee security installation does not have a firewall. Any thoughts on what could be causing this. If you need to see any code or need more information, let me know.The server is running Windows 2003 server OS.
I would be willing to bet the correct ports are not forwarded.
What kind of web app is it? You have to find out which port that app uses and forward it on the router.
Server Application Unavailable in IIS for ASP.NET application
Problem :Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
Solution 1:
Open the command promt and direct to the folder C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
and run the command to install ASP.NET in your IIS
aspnet_regiis.exe -i
Solution 2:
To work around this problem, verify that the ASPNET account has the correct user rights as follows:
a) %windir%\Microsoft.NET\Framework\Version\Temporary ASP.NET Files: Full Control
%windir%\Temp: Full Control
b) Application folder: Read
c) %installroot% hierarchy (for example, %windir%\Microsoft.Net\Framework\Version): Read
d) %windir%\Assembly: Read
e) Web site root (for example, %root%\Inetpub\Wwwroot) or the path that the default Web site points to: Read
f) %windir%\System32: Read(Typically, the ASPNET account has already been granted user rights as a member of the Users group.)
Now Close all the applications and reset IIS in command promt 'iisreset'
problem solved :) cheers
A group of us wrote a .NET web application for our University class and in order to let our prof test with it I am setting it up on my webserver at home. Here is what I have done so far:
I created a new account on my domain, I then granted that account Read, write access to the folder where the app is stored. I have setup an application pool that uses this new account as its identity and created a new site that uses the new application pool.
I initially was receiving the Service unavailable error message, so I realized I had to add my account to the IIS_WPG account. So now I am stuck at the "page cannot be found". The website is pointing to the correct folder (I can see the aspx page list from within the IIS browser) but when browsing the site either in IIS, on a browser on the server or on a browser within my network I keep getting Page cannot be found. The home directory is pointing to default.aspx which is what our app uses.
The app of course works just fine when running from within the IDE, but now that I am trying to get it to work it doesn't want to.
Any thoughts?
Thanks.
you should give error details first.
for now, I suggest you check the 'network service' account's permission.this is the ASP.NET's account.
then publish your site to *.aspx file and *.dll file. to see if there is any errors.
So I found the issue. What I didn't know is that by default, IIS 6 does not turn on support of active server pages and .NET pages in Web Service Extensions. Once I had turned this on the site began to work just fine.
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.
My host is having issues getting my MVC3 app to work on their server, so I though I'd check it out myself. Until now I've been too busy developing under the built in server to worry about IIS, but today I tried my first deployment to the host with no joy. Then I tried one to my local IIS, with no joy. Then I tried telling VS to use IIS for debugging, to maybe resolve some local issues, with no joy.
What steps and configuration are required to use local IIS 7.5 to debug an MVC3 application?
EDIT: Going through a browser, after clearing up a permission problem for my Windows user on Temp ASP.NET Files, I now site with a I get a HTTP Error 403 (Forbidden), but the occassional basic auth login dialogue. Here I have tried a Forms auth user, my normal Windows user, and my Windows admin user, all to no avail.
When I try and debug under VS, I get a 500, internal error.
THE PLOT THICKENS: When I enable directory browsing on the site, I get a proper directory listing for the site root url. This suggests the the MVC3 routing is not working, but why not?
If you're getting a directory listing that means there's not a default file set (for IIS6). It usually means the request wasn't routed to IIS to deal with. thing are slightly different with II7 & it's integrated pipeline.
Simon