Just an FYI, the managers who built this system have left and I got thrown into the deep end and trying to figure things out as I go. So if I sound like I don’t know what I’m talking about, it’s probably true.
The errors do seem to be connected to caching a service. Things were fine until I tried finishing some caching last night and everything went wonky again. So the caching process seems to be the common denominator.
JLenhardt, we do have SQL Server Enterprise but those databases work fine. The ones that constantly have connection issues are file geodatabases on a file server. And I’m not sure how to see the version of the fgdb. When I check properties it looks the same as the attached image from before; it does not show the version. Is there a way to check the version of a file geodatabase?
Vangelo, what are “network shares of file geodatabases”? When I copied the fgbd to a different server it did open fine. So it might be a networking issue since it’s the caching that seems to be the problem. Do you think services should be run from SQL databases instead?
The system is set up like this, as far as I know:
--We have a file server with file geodatabases where we publish services from.
--There are two ArcGIS Servers with file geodatabases that match the file server geodatabases. Somehow the services run off of these.
The cached service uses data from a separate fgdb so I don’t understand why it would cause connection errors on every other fgdb on the file server.
Hopefully that made sense and gives a fuller picture of my problems.
Thanks for any help given. It is much appreciated.