Changing server hostname
Hi all
I'm wondering if anyone has been successful at changing the hostname of a server after Geocortex has been installed, post install completed, and a few test sites put up? I found a thread here:
that seems to have been successful, but even after these changes (and a reboot), when I open the REST Manager, it still gets directed to a URL that contains the old hostname. If I swap the old hostname for new in the URL, then I get a "Service unavailable: HTTP Error 503. The service is unavailable."
I'm hoping not to have to get IT to change the name back so would greatly appreciate any guidance on this topic...
Thanks, Gavin
-
You should be able to update your web config files in the following locations.
<essentials install location>\<instance name>\REST Elements\Manager\web.config
<essentials install location>\<instance name>\REST Elements\REST\web.config
You probably will notice some of the following attributes in your web.config file need to be updated.
<add key="ServiceBaseUrl" value="net.pipe://<yourdomain>/ApplicationServices/" />
<add key="EssentialsUrl" value="http://<yourdomain>/Geocortex/Essentials/<instance name>/REST/sites" />
0 -
You should check also to make sure the application services are started.
0 -
Thanks Nick
Unfortunately (for me) I had already edited those web.config files per the link in my original post and that did not fix the problem. I've searched all the xml files I could find for the old hostname as well as the registry and am not seeing anything obvious. I just can't figure how the REST Manager is still directing me to the old URL, let alone why I get the error when I plug in the new hostname in the URL.
The only service I found is the 'Geocortex Agent' and that is started. As I mentioned, I had restarted the server and still no luck. Thanks for the suggestions though.
cheers, Gavin
0 -
Sure you checked this but are all of the app pools up and running. i had a routing process crash and my app pool shutdown on its own and I was getting 503 errors acrooss all sites until I restarted the app pool. Is Anything showing up in your logs for windows or the essentials log files.
0 -
Well, I'll preface this with the fact that we just installed Geocortex a few weeks ago and are still trying to find our way around. Also, I am blindly groping my way through the web stuff coming from an old school GIS background.
That said, I looked at the app pools under IIS and all are started but one, which is called 'EssentialsAdministrationAppPool4' (there is one running called 'EssentialsAppPool4'). As a test, I started the one called 'EssentialsAdministrationAppPool4'. It starts fine, but as soon as I try to access the REST Manager (with the error), the pool shuts down (no error).
I checked the IIS logs and nothing obvious. I'm not yet familiar with the Essentials logs, but browsing around and checking the logs I found in the essentials folders did not reveal anything obvious (then again I may be missing it since i'm not familiar with what I should be seeing).
Anyway, I'll keep reviewing the logs, but i wanted to make sure there wasn't something obvious I was missing and that it was actually possible to change the hostname without having to reinstall. Thanks for the advice.
cheers, G
0 -
There was someone else having this issue recently that posted on the fourms. Your app pool should not be shutting the app pool not running would explain the 503 error.
0 -
Thanks- I think I am getting closer. I found the thread I'm guessing you were referring to, which seems to be the same issue:
https://support.geocortex.com/SupportForums/Thread.aspx?pageid=0&mid=2&ItemID=2&thread=47464
The identity on both of the app pool entries included the old hostname <old_hostname>\EssentialsAdmin. I was able to change the identities to the defaults as suggested in the article, but am unable to change it to the new one, being <new_hostname>\EssentialsAdmin (or just EssentialsAdmin) due to getting an error that i am using the wrong password or that the account doesn't exist. Then looking at user accounts, it seems that the 'EssentialsAdmin' acct has been checked for 'Account is locked out', which would explain why I am getting the error that the acct doesn't exist. Not sure why it's locked though. For the other app pool entry (the one that is still running, the Essentials acct is not locked, but when I try to change the identity back, I get an error that the passwd is invalid (however, there is only 1 account on the server which is the admin acct and I am using that passwd). I'm now wondering if I need to use our domain admin acct...
Anyway, thanks for all the help and glad it's Friday. Looks like resolution will wait until Monday. Worst case I will spin up a fresh VM and re-install since we don't have that much time invested yet. Just seemed like the change should have been straightforward...
Thanks, Gavin
0
Please sign in to leave a comment.
Comments
7 comments