%META:TOPICPARENT{name="ErrorMessagesU"}% ==Error Messages (U)== [[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|#]] ===Unable to find server x with protocol tcp in file services or services file not found...=== If you receive "Unable to find server x with protocol tcp" errors, review the parameters which you pass to Progress at startup. For example: {{{ proserve demo.db -S pro82a -N tcp -H saturnus }}} Specifically, insure that the value passed to the -S parameter appears in your server's {{{/etc/services}}} (UNIX) or {{{%SystemRoot%\System32\Drivers\etc\services}}} (Windows) file. For example: {{{ $ grep pro82a /etc/services pro82a 6791/tcp # Progress Socket Service }}} Ensure that the appropriate socket or service name is passed in the ConnectOptions (Multi-Tier) or Database Options (Single-Tier) field of your DSN. For example: {{{ -S pro82a -N tcp -H saturnus }}} If you use tableview, ensure that the correct value appears in your .pf file. For example: {{{ $ cat tableview.pf -ld demo -db /usr/lpp/progress/demo.db -S pro82a -N tcp -H saturnus }}} ===Evidence=== Request Broker Log Services File