%META:TOPICPARENT{name="ErrorMessagesT"}%

==Error Messages (T)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]
    
===The connection to the server has been aborted===


To resolve this problem, insure that you do not pass {{{<hostname>::<vnodename>}}} in your connect parameters. Simply pass the vnode. Use of hostname should be reserved for instances in which the Ingres database resides on a remote machine.

If the problem persists with Multi-Tier drivers:

1. Install any Multi-Tier server components under the ingres uid.
2. Ensure the ingres user .profile is set before starting the Multi-Tier Request Broker.
3. You may need to switch your agent from ingii_mv to oig2_sv or vice versa.


===Evidence===

Data Source Attributes