Error Could not connect to server for database found dbfiles found, errno 0 1432 when Logging into FIMS

When starting FIMS the Error: “Could not connect to server for database n:\found\dbfiles\found, errno 0. (1432)” pops up.  This is a frequently seen error after the FIMS server has been rebooted, either manually or after Windows Updates.  When rebooting, the Progress Admin Service doesn't always have enough time to fully shut down before the reboot occurs, and therefore there is sometimes a database lock file that remains in place, which will prevent the admin service from starting after the server has booted up.

This can also occur if the _dbutil.exe has locked the database files after performing a scheduled task such as copying live to test or backing up the database so that the database cannot be re-started.
If you are receiving the above error:
  1. Navigate to X:\npo\oemgmt\config on the server (replacing X: with the correct drive letter) and look for a file called admsrv.lock.  If this file is present, delete it.
If you receive an error that the file is in use or access denied when trying to delete it, check the task manager and close any java.exe processes that may be running.  Try deleting it again.
  1. Go to Start>All Programs>OpenEdge>ProEnv.
  2. In this command prompt window, type the following separately and press enter after each one: proadsv -stop,  proadsv -start
This should start the admin service, which is what allows workstations to connect to the server.
If you receive a blank line after typing the above command, then the admin service should have started. Check and make sure that the admin service started by going to services and see that it is running.
  1. Now type the following in the ProEnv window: dbman -start -all
This will start your databases if they're not already running.  You may receive errors indicating they are already running, which is fine.
  1. After this step completes, try connecting to FIMS.
  2. If the steps above do not resolve the issue, go to Task Manager\Processes and search for any processes called OpenEdge Database Server/Broker. Right-click on the process and select properties and make sure at the top of the window on the General tab that the process is called _dbutil.exe, if so end this process. You want to ensure that you are stopping just the _dbutil.exe and not another database process that can run under the OpenEdge Database Server/Broker.
  3. After step 6, log into FIMS database and the error should be gone.
NOTE: If this is occurring just for the TEST database, many times copying over live to test will resolve this issue if the steps above do not work.



Was this article helpful?