Error Messages (C) A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #Could not connect to server for database <database>, errno 0. (1432) The "Could not connect to server for database x, errno 0. (1432)" is a Progress-specific database error. To resolve this error, establish a socket-based connection to your Progress database. The following instructions will assist you with this task:1. Insure that your Progress database is running in sockets mode.2. Use a text editor to open your server's /etc/services or C:\WINNT\System32\Drivers\etc file.3. Locate and record your Progress socket service entry. For instance:pro91b 6794/tcp # Progress Socket Service 4. Use a text editor to open your client's /etc/services or C:\WINNT\System32\Drivers\etc file.5. Insure that no client service uses the same TCP port number that your server uses for the Progress socket service. For example:ingreslock 6794/tcp ingres 6. Reassign any conflicting TCP ports, as appropriate.7. Create an entry in the client services file, which matches your server socket service entry. For example:pro91b 6794/tcp # Progress Socket Service 8. Save your changes and exit the services file.9. Pass your Progress socket parameters in the Database Options field (Single-Tier) or DB Connection Options field (Multi-Tier) of your Data Source. For example:-S pro91b -N tcp -H example.domain.com10. Insure that your database parameter ends with a .db extension. For example:-db /usr/lpp/progress/dbs/sports.db11. Test.Evidence Data Source Attributes Request Broker Log Services File Session Rules Book