topic Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn in ArcGIS Online Questions

Tiled Service displays at incorrect scale, variable by scale of map, only in AGOnline

DavidTreering — Fri, 18 May 2012 19:14:32 GMT

Adding two of my own services that display correctly everywhere else, even ArcGIS Explorer Online. The Cached Tiled layer shows up at the wrong scale. I can't figure it out.
http://bit.ly/KwgyWP
Any ideas? I'm stumped.
David

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

MikeMinami — Fri, 18 May 2012 21:41:13 GMT

I can't see your services in the map. Is your server publicly accessible? it seems not.

Mike

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

DavidTreering — Tue, 22 May 2012 00:10:21 GMT

http://147.126.65.155:8399/arcgis/rest/services/campus/lurec_base1/MapServer?f=jsapi

I cannot figure out why the service is not visible to you. I can view it from anywhere on the web. Port 8399 is open, unrestricted.

What should I try to make it available to you?
Thanks.

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

MikeMinami — Tue, 22 May 2012 15:24:46 GMT

I still can't access it. I don't know how to make it visible...

Mike

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

DavidTreering — Tue, 22 May 2012 21:28:42 GMT

I've tried opening it up. Can you try again?

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

MikeMinami — Tue, 22 May 2012 21:53:47 GMT

Nope. I still can't access it.

Mike

Re: Tiled Service displays at incorrect scale, variable by scale of map, only in AGOn

DavidTreering — Thu, 24 May 2012 17:09:04 GMT

Stay tuned...the problem, finally discovered by Grant R. (who deserves a serious lollipop for Incident #1039390) is that I'm still using port 8399 for production deployment. I left it as the default instead of changing it to the recommended port 80 or 443.

Apparently, there is internal ESRI use of 8399, so my traffic couldn't be seen by the tech support people (and only them), while people all over the place outside my network could see it fine. That was baffling and frustrating.

Whew! I'll get back to you when it is deployed on the correct port.