esrimohan As mentioned above, I am having general issues with my cached basemaps not printing (10.5.1 in my case....my 10.2.2 serevice print just fine). I am working with tech support and have found a few things. Just in case these help you at all. FYI - we have several basemaps that we cache, and then turn off the layers in the mxd since the cache is what we want to use. So, check these things...
- Make sure all the layers in the mxd for your cache map service turned on (checked).
- Make sure all the datasources for your cached service still available
- if you have a mix of raster and vector data in the cached service, make sure they are all using the same spatial reference.
As mentioned, our 10.2.2 services work fine. Some of our cached services no longer have access to the source, which is ok since we just need the cache. We also have our services in the same SR as the raster layer, but had a few vector layers that projected on the fly. Again, it didn't matter in 10.2.2 since it would print from the cache.
Now it seems that the print itself is trying to be dynamic. I'm hoping they will have a workaround to force the print from the cache. I hope to know more in a few days.
This is all independent of the actual ArcGIS Print Service used (the out-of-the-box or custom, or the version), and independent of the API used. That is, we tested using the REST endpoint to take any API like JavaScript out of the equation. It also is independent of external vs internal-only, web-adaptor or not, etc. It appears to be the way the services and their caches are dealing with printing.
II'm not sure if this is relevant to your situation, but wanted to pass this along. Once I have a resolution, I will post on the thread link I mentioned above.