503 Service Unavailable
Hi,
I'm getting a 503 Service Unavailable error message when I try to access the Geocortex Essentials Manager.
Things I've tried to fix this problem:
- Restarted application pools
- Deleted and recreated Essentials and EssentialsAdmin accounts
- Removed essentials completely, removed stray directories and site info, removed registry entries, removed accounts, and then reinstalled.
And still the problem persists. IIS 7.5 on Windows 2008 R2 is working fine. Running Essentials 3.10.1. Any help appreciated.
Regards,
Dion.
-
Update:
The exact error message is:
Service Unavailable
--------------------------------------------------------------------------------
HTTP Error 503. The service is unavailable.
0 -
Hi Dion,
A 503 Service Unavailable messsage means something upstream of Geocortex Essentials or REST Manager is not running or not able to process our request. None of our services will return a 503 code - we always try to return 200 (OK) or 404 (not found) only, and even then you should see the Essentials logo somewhere on the returned page.
Usually with ASP.NET applications, this means that the application pool is stopped. You said that you restarted the app pools - were they stopped? Do they stop when you try to launch the site? If so, the Windows Application and System Event logs should indicate why those application pools are stopping (they aren't supposed to). Often they will stop if you have configured a custom identity for the application pool and that identity is no longer valid - for example, a domain user that is now locked out or has had its password changed.
Otherwise, it is likely an IIS configuration issue where the IIS configuration limits the type of services we may run. Sometimes this is an issue where our extensionless URL handler is not allowed to run, so that we are able to use the ASP.NET handler only for pages that have an extension. So, "Default.aspx" works but "RestManager/login" does not.
Regards,
-Malcolm
0 -
Thanks for your reply Malcom.
Yes indeed the problem did appear to be related to the EssentialsAdministrationAppPool4. It was a strange issue as removing Essentials from the server, along with the application pools and user accounts, and directory and registry entries, did not fix the problem after a reinstall.
So what I did today to fix the problem was to change the identity for both the EssentialsAppPool4 and EssentialsAdministrationAppPool4 to the default 'ApplicationPoolIdentity'. I then stopped and restarted both application pools. And then I set the identity for EssentialsAppPool4 to Essentials, and EssentialsAdministrationAppPool4 to EssentialsAdmin. After doing this, and stopping and starting both application pools once again, the issue is gone and everything is back to normal.
0 -
In case anyone is still seeing this thread, what are the password(s) for the Essentials and EssentialsAdmin user accounts? In trying to change the identity for the app pools back to these users is prompting me for a password, and it doesn't seem to like the admin password, which is the only account on the server.
Thanks, Gavin
0 -
Hi Gavin,
Can you take a look at the Users on the server (in Users and Groups) - there should now be at least three local users: your Administrator account, the Essentials account, and the EssentialsAdmin account.
These accounts are assigned random passwords when they are created, so you cannot look them up. However, you can reset the password for the user AND for the identity of the application pool and then you should be fine.
0 -
Thanks Malcolm
The *random* password and it being Ok to reset it was the key I was missing. I actually ended up uninstalling and reinstalling instead as we did not yet have much time invested, so figured I would cut my losses on troubleshooting. I just deleted the app pools and the users before reinstalling and it seems to have resolved our issues.
The one other item (this arose from changing the hostname on the server) was that the REST manager shortcut was still pointing to the old hostname in the URL and I could not figure out where that setting was located. The reinstall fixed that too.
The only symptom left is that the SL viewer won't fire up, but I'm guessing I need to reinstall that as well and all should be fine.
Thanks, Gavin
0 -
I realize this thread is ancient...
I have a client who's Essentials user profile appears to be corrupted. I tried fixing this per this (http://www.bauer-power.net/2010/03/temporary-profile-loaded-on-windows.html#.VUocJflVhBc) article . After doing this hitting the desktop.json.js file returned a 503 error and caused the app pool to crash.
I followed Dion's suggestion and using ApplicationPoolIdentity has things working again. Are there any known drawbacks to doing this?
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare