We are planning to upgrade the Esri UK Online Data Services from ArcGIS 10 to 10.2.1 on 7th April 2014.
One important change at ArcGIS Server 10.2 and above is that the service URLs are now case sensitive. We have therefore taken the decision to make all of our service names lower case only. The service types will remain mixed case.
To minimise the impact on our users we have put in place URL re-direction so that for a period of time URLs in the previous mixed case format will continue to work, however, we recommend that for optimum performance you update your MXDs, LocalView Fusion content and other references to Esri UK Online Data Services to be in lower case.
Examples of the change to the URLs for the OS Open Background service:
Known Issue with Free Census Services
Please be aware that in some circumstances the URL redirection that has been put in place to cope with the changes in case of service names is not working for the fifteen free Census Services.
If you are unable to connect to the census services following this upgrade then please check that you are using all lower case urls.
For example, if you added the Census data (or other data) to an MXD in ArcGIS Desktop using the Services Add-In and you are no longer able to connect to the service - then you should remove the layer from the MXD and re-add it.
We have successfully upgraded our Online Data Services from ArcGIS Server 10.0 to 10.2.1 today.
Esri UK Online Services - Token Issue.
The recent update to our Esri UK online map services, has resulted in a number of our users seeing issues with Long Lived tokens that had been previously generated to enable the services to be used with our web API’s.
The error manifests itself as an “Invalid Token Request” error. If you are affected by the issue, the solution is to regenerate the Long-Lived Token using the token generation page, in exactly the same way as the original token was generated. The new token should be used instead of your existing token.
Up until April 9th at 3pm, Long Lived tokens were set to expire after 24 hours regardless of the length requested. This has now been corrected. If you have created a new token prior to the time above, you will need to create another new token, and this should now behave as expected. Apologies for the disruption to your services.
Known Issue with IP based tokens
Please be aware that to create IP based tokens you currently need to ensure that your URL is correctly cased.
If the URL is incorrectly cased the token created is not valid and you will get an invalid token error when you attempt to use it.
We are currently working on a fix for this issue.