Search results

  1. G

    **Could not connect to server for database...

    - "Started on port 3001 using tcp, pid 2976. (5646)" You need to open de ports 3001-3010 at least.
  2. G

    **Could not connect to server for database...

    When you connect a database in Client-server mode, the port specified by -S is the first of the ports used, then Progress start a "server" process wich use another TCP Port. You can see the port that is used for each server in the database log file ("Starting server x for database in port nnnn")...
  3. G

    **Could not connect to server for database...

    Hi Check the configuration of the "new" Windows Firewall, now enabled by default in 2003 Server. This can avoid the connection via TCP ports required for Progress.
  4. G

    DB Migration from 9.1D to 10.1A

    Hi. Could you review the database log file (.lg) searching for any message additional to the normal startups messages? What products of the new versions are installed in the server?
  5. G

    Help with Progress Monitoring

    Hi! The fields _Connect-id and _Connect-Usr from table _Connect give you a list of all users connected to the database. Useful for a query like yours. For db monitoring, the "promon" utility can give you too many statistics about the database and your execution status. Regards Gabriel Flores
  6. G

    Database Reports slow after 10.b05 conversoin

    Hi! If the server is a new server, a check to the Server performance values (CPU, Disk, Memory, etc) when reports are running and compare whit values on work hours may be a good idea. Regards Gabriel Flores
  7. G

    AI Circular

    I recently have an interesting experience related to fixed and variable extents Dump & Load process of a database and make some tests before de real process and in one of the tests, I forgot to create fixed size database extents and the db was created with variable extents. The result: three...
Top