AdminCacheKey

[TedCronin]

How is this value calculated?  How do we get a new one?  Can this go bad where it prevents us from logging in to clear cache?

[RaviNarayanan]

Ted,

The value for admincachekey is set when arcgisserver is installed and it is unique to each installation in ArcGIS Server for .NET. This value is used when generating an admin token. And it is used to validate the token when a token is used to programatically clear the REST cache. If this value changes any tokens that were generated prior to the change in value of admincachekey will be invalid. it does not affect manual login to the REST admin.

more info on admintoken and clearing REST cache using admin token
http://help.arcgis.com/EN/arcgisserver/10.0/apis/rest/generateadmintoken.html
http://help.arcgis.com/EN/arcgisserver/10.0/apis/rest/clearcache.html

Ravi

[TedCronin]

I have post out where I cannot manually clear cache in the Server forums.  This is Server 10 final.

http://forums.arcgis.com/threads/6984-Issues-with-Rest-Admin

[RaviNarayanan]

Is this a local user or a domain user that is used for login? If it is a local user, can you try specifying the user name as MACHINENAME\username? There was bug in pre-release version which allowed login only when the username was specified as MACHINENAME\username for local users.

[TedCronin]

I will try that.  I redid the post install 5 times to see if that would clear everything up, deleteing users, post install, again, again, and again.

I have done:


tcronin
\tcronin
ASRCLKREC\tcronin
but
not Machine name\tcronin

I will have to VPN from home to test this out.

On another note, I am stoked I got the feature access going, finally.

[TedCronin]

Machine name did not work.  I have logged this with Support to resolve.

[RaviNarayanan]

Ted,

Can you check if you can use the same username/password to generate an admin token
http://<server>/arcgis/rest/admin/generateToken

and use the token generated to clear the cache?
http://<server>/arcgis/rest/admin/cache/clear?token=<generatedtoken>

Make sure that if it is domain user the username is specified as:
DOMAINNAME\username

or if it is a local user, then the username is specified as:
MACHINENAME\username or username

Ravi

[TedCronin]

I can use my login to generate a token, but the clear cache will not work because it wants me to login again.   For the token do, the training . .  get added to the text string?

Also, note, I can login as the WebServices user, and I already changed in the config file the manual cache to scheduled within the xml last week, and logging in today as the WS user, I can verify that it is truly scheduled.  It does bother me however, that I cannot login to this machine as me for admin.  Server Manager works as expected, generate Token works as expected.

[RaviNarayanan]

For the token do, the training . . get added to the text string? .

yes, the whole string including the dots in the end .. is the token.

[TedCronin]

ok, I added those and it did not work, and now I am seeing the same issue with my production box regarding no access to the rest/admin.  I will generate token for my production and again for my test to see if that works perhaps tomorrow will be a new day 🙂

I did not have this many issues in any of the beta releases btw, out side of feature access:)

This is my last post to Support for new Production Machine:

For my new server.  I am running 2003 Server R2.  I have only installed GIS Services.  After install, I ran the web services post install.  I logged out and back in.  This is a brand new machine for 10, meaning I just uninstalled 931 to install 10.  I can login with ArcWebServices.  I have attempted to login from my remote machine as well as the server itself.  The server itself has IE 8 and FF 3.6, and both have failed with rest/admin.

Any Ideas. 

Also, So, I should be seeing a login after I type the token, and it is your understanding that this would theoretically clear the cache, or I should not see a login and it should just pass me through???

I have updated the Scheduled as part of the rest.config for this site as well, since that works, but this needs to be resolved.