Open a first Windows Explorer then connect to a first Windchill server using the DTI "Windchill Documents"
Keep the window opened
Run a new Windows Explorer then connect to a second Windchill server using the DTI "Windchill Documents"
Go back to the first window and press F5 to refresh => unclear error message saying ObjectNoLongerExistsException
The request is to improve this error by catching this ObjectNoLongerExistsException and display an intelligible message; something like "You are disconnected from this server".
Here is the real use-case:
The customer will use the DTI with several Windchill instances.
There is a transparent authentication configured between the client machines and all these servers, based on Windows session => the user does not have to enter any login/password => the switch from 1 Windchill server to another is also transparent for the user
A user will work intensively in collaborative manner on Documents spread in these several Windchill instances
A user can browse the DTI Windows Explorer on a Windchill Server #1, then receive a request from a colleague to look at a document on a Windchill Server #2, then come back to his first Windows Explorer and get the error message "ObjectNoLongerExistsException" (instead of like for example "You are disconnected from this server")
A user may not know perfectly and constantly to which server his DTI is connected to.
So the request is just to improve a bit this error by catching this ObjectNoLongerExistsException and display an intelligible message.