Utilizing Web Adapter generates HTTP error 404

2978
2
Jump to solution
02-22-2013 06:59 AM
BrianKraus
New Contributor II
Hello everyone.

I saw that someone had a similar problem to mine, and posted a similar question that I will back last July (http://forums.arcgis.com/threads/62444-Web-Adaptor-Error-404-Not-Found).  I did not seem like it was ever resolved, so I am posting/asking again.

Some info first:

- server: MS Server 2012 Standard
- IIS 8.0
- ArcGIS server 10.1 (have not installed SP1 yet) on default port 6080
- web adapter installed successfully and matched with GIS server. (name: arcgiswa)
- everything is installed on one machine (i.e. both web server and arcgis server)
- the server is behind a university firewall, but does have port 80 opened to it (i.e. you can visit a default page at http://<ip_address> or http://<fqdn> just fine)

So once everything is completed, I follow the link presented to make sure the web adapter is routing traffic to the Services directory.  This url is of the form - http://<machine-name>//arcgiswa/rest/services  (<machine-name> has been tried with the following variables, which are all really the same machine:  "localhost", the actual windows machine name, the IP address of the machine, a FQDN).  All attempts of accessing the ArcGIS services page, and consequently, utilizing the ArcGIS Flex application that will be deployed on the server, lead to a "HTTP Error 404 - Not Found" message. Note, I am not trying to "administer" the ArcGIS server (that is only done via the 'Manager' page or direct connections to port 6080 via ArcCatalog).

So, whenever I try to access the ArcGIS server through the default port 80, which is the function of the web adapter, it acts like it is trying to load a page that isn't there.  Is there something I need to do with the "Default Document" settings under the 'arcgiswa' virtual site in IIS, or perhaps the 'web adapter' folder listed there too?  I see that under the 'web adapter' folder there are some files called "Config.aspx", "Error.aspx" and "Update.aspx", but I don't think those are files I need to worry about for the general function of the web adapter.

Thanks for any and all help and your time on this.  I would rather not have to expose the ArcGIS server directly to the outside world for use of our simulation application.  That also entails increased bureaucratic paperwork and time to get that port opened through the firewall.

Cheers!
Brian
0 Kudos
1 Solution

Accepted Solutions
BrianKraus
New Contributor II
Final update - PEBKAC was the answer.

I had set the IP address bindings to a different test site in IIS, and the web adapter did not install under that directory, it installed under the "Default Web Site" within the IIS hierarchy.  So I just needed to switch the binding of the IP address back to that site, and everything worked fine.

Hopefully others encountering this problem can see this and it might be their solution as well.

View solution in original post

0 Kudos
2 Replies
BrianKraus
New Contributor II
Some new information that might help illicit a help response:

- I just installed ArcGIS Server 10.1 SP1 and Web Adapter SP1:  still gives the same issue

- clarification: when I am on the server itself (either physically logged in, or through remote desktop), the problem does *not* manifest itself if I access the rest services directory in the following manner - http://localhost/arcgiswa/rest/services.  I can see the root services folder just fine that way.  However, if I am on the server, or on another machine, and try to access the page via - http://<ip_address_of_server>/arcgiswa/rest/services, then I still receive the 404 error.

- no informative logs show up in ArcGIS server logs.  In IIS, I just see the 404 error in the log.

Thanks again!
0 Kudos
BrianKraus
New Contributor II
Final update - PEBKAC was the answer.

I had set the IP address bindings to a different test site in IIS, and the web adapter did not install under that directory, it installed under the "Default Web Site" within the IIS hierarchy.  So I just needed to switch the binding of the IP address back to that site, and everything worked fine.

Hopefully others encountering this problem can see this and it might be their solution as well.
0 Kudos