Hi broberc6,
A few things could be causing this; first, on the new production server, can you confirm the database is running? If you have moved the database from one server to another (with a different hostname) there are a few things that will cause the moved database to not even start - so I'd start by confirming it is running.
If you are using Progress Explorer to manage the database, you can use the information button after selecting the database to see the status; or, if you know where the log file(s) are for the database, have a look at the last entries to confirm that it is running. While watching the log file you can stop and restart the database just to monitor the messages to ensure it is starting, and staying started.
While you are looking at the database log (databasename.lg), start at the end and work backwards to find the entries when the database started, and confirm what the service number and hostname are set to; depending on your PROGRESS version, these lines will look something like this:
[2009/01/13@18:48:40.390-0800] P-3039312 T-1 I BROKER 0: (4261) Host Na
me (-H): van-server-1.
[2009/01/13@18:48:40.390-0800] P-3039312 T-1 I BROKER 0: (4262) Service
Name (-S): db-svc-1
and confirm on the client side that you are using the correct hostname when making a connection to the server (the -H parameter). Make sure that, from the client, you can successfully ping the server using that hostname.
Confirm in the production Windows services file that the -S service name has an unused portnumber assigned and this is the same port number you are referencing when making the connection from the client. To be safe you could even directly specify the port numbers when starting the database and also when connection the client (i.e., 25123 or some other large number 20000-50000 that the server would not already be using).
I think you should start there; other things could be wrong, but if you had the client connecting successfully to a test server, and now you have moved the databases to a production server, the things that are most likely to cause the problem are hostname and service number, OR the moved database is not starting successfully possibly because the database files were copied from one server to another using Windows copy commands rather than using the PROGESS utilities (probkup, prostrct, prorest) that are required for moving PROGRESS databases (since hostname, and database paths are contained within the database itself, so you are not able to cp the database from one server or directory to another using Windows O/S commands and have the server start and work).
Let's start there and see if this helps.
If not, it would be helpful to know the following:
PROGRESS version number on Server and Client
How the client is connecting (using ABL code "CONNECT" statement or as a start-up command line parameter when starting the client session.
The start-up parameters from your database log file on the server.
One final note, you can use the PROGRESS knowledgebase to type in error message numbers and get information of similar issues that give this error (1432 in your case). There may be some additional help there that makes sense to your situation:
http://progress.atgnow.com/esprogress/Group.jsp?bgroup=progress
thanks, hope that helps
