topic Re: Cache Failing in ArcGIS Enterprise Questions

Cache Failing

SonyaCowper — Thu, 17 Sep 2015 18:42:39 GMT

Trying to create a cache for our map services. No matter which map service I pick, it always bails out at 1 hour and 5 minutes. I'm getting ERROR 001470, and ERROR code:201. Using ArcGIS Server for 10.3. I have tried this on a few different map services and each time it bails at 1 hour and 5 minutes.

Any thoughts on where to look to see why I am being kicked out after just a hour? I'm at a loss.

Re: Cache Failing

JakeSkinner — Thu, 17 Sep 2015 18:46:34 GMT

Hi Sonya,

I would recommend checking the log files in Manager > Logs > View Logs.

Re: Cache Failing

MichaelVolz — Thu, 17 Sep 2015 18:48:05 GMT

What is the datasource(s) for your cached mapservice?

Re: Cache Failing

SonyaCowper — Thu, 17 Sep 2015 18:49:57 GMT

Here's what I'm getting in my log file:

Could not connect to the identity store as one or more of the connection parameters is incorrect. Verify that you can connect to the identity store outside of ArcGIS Server using the same parameters. [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A8, comment: AcceptSecurityContext error, data 52e, v1db1]

So confused!

Re: Cache Failing

SonyaCowper — Thu, 17 Sep 2015 18:50:15 GMT

File geodatabases

Re: Cache Failing

DavidColey — Thu, 17 Sep 2015 19:30:12 GMT

You have identity store issues. Server isn't recognizing your connection. Are you using the internal user store or are you connecting via Active Directory? Regardless, you have to make sure you are registered in the admin role from either your internal store login or from your AD login

And since you will be connecting to server from behind your firewall to run a cache, make sure you are connecting to server from Catalog using your internal server connection, and not the external web adapter connection - e:g:

http://<machinename>:6080/arcgis/admin

and not

http://somename.com/arcgis/admin

David

Re: Cache Failing

SonyaCowper — Fri, 18 Sep 2015 12:41:59 GMT

Thank you David. I did go back into the identify store and fix that error.

However I am running the cache using an administrator role and am still timing out on my cache.

This is my new error:

Error performing identify Error handling service request : java.lang.OutOfMemoryError: Java heap space

Re: Cache Failing

JakeSkinner — Fri, 18 Sep 2015 13:11:16 GMT

See if you can build the cache using the Manage Tile Cache tool.

Re: Cache Failing

SonyaCowper — Fri, 18 Sep 2015 13:12:48 GMT

Restarted ArcGIS Server and am redoing the cache now...I'll let you know if I make past a 1hour and 5minutes.

Re: Cache Failing

DavidColey — Fri, 18 Sep 2015 15:12:09 GMT

can you provide any more info about your envrionment and site configuration?

Re: Cache Failing

SonyaCowper — Fri, 18 Sep 2015 17:26:40 GMT

I've made it pass the 1hour 5min mark. Very exciting! And it's still running. Hoping the identity store issue solved me problems. Thank you!

Re: Cache Failing

DavidColey — Fri, 18 Sep 2015 17:35:58 GMT

oh good. Good luck and fyi for caching 10.3.1 is very stable if you can update

Re: Cache Failing

SonyaCowper — Fri, 18 Sep 2015 17:38:16 GMT

Does each map service ArcSoc EXE take up less RAM?

Re: Cache Failing

MichaelVolz — Fri, 18 Sep 2015 17:38:47 GMT

Dave:

Just a quick aside on caching and v10.3.1. Are you using an Oracle database to store your feature class data for caching? If so, do you have a RAC environment?

Re: Cache Failing

DavidColey — Fri, 18 Sep 2015 17:42:03 GMT

no its not that its that esri stabalized the tcp/ip communication that server uses to move files around the site machines and directories, I think.

Re: Cache Failing

DavidColey — Fri, 18 Sep 2015 17:47:59 GMT

No Michael, I'm not. We push out our entire Production (SQL Server 2012) feature classes to a file gdb via python after our weekly replication posts.The file gdb resides in a stage directory on my mahcine. A scheduled task then stops the arcServer.exe process on each site machine and a second scheduled task overwrites the file gdb in the data-store shared location via windows xcopy. The copy and extract from production to stage takes like 35 mins, the xcopy to data store takes like 35 seconds

Re: Cache Failing

MichaelVolz — Fri, 18 Sep 2015 17:57:44 GMT

Thanks Dave. I was just curious before my organization was having cache issues at v10.2.2 against an Oracle 12c RAC database (even with the patch), which appears to have been remedied by upgrading to v10.3.1.

Re: Cache Failing

DavidColey — Fri, 18 Sep 2015 18:07:45 GMT

That's good to know. I know Jeff Pace was having some issues, they're an Oracle shop as well