This is a typical problem using ESRI software. It requires hours of my time and often unnecessary time spent by ESRI support staff. In my experience, with proper error trapping, a meaningful error can be provided in almost all cases. I suggest allocating more resources to returning useful error messages. This would probably result in overall savings for ESRI. It certainly would if you include lost time by developers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.