Recent content by richard_thorp

  1. R

    problems with connecting db to adminserver

    This is usually because you haven't started up the database with a port number. It'll only talk to the admin server if you have entered something here. Drill down to the "Default Server Group" section for the database within progress explorer and add something in the "Service Name or port...
  2. R

    After imaging with AI-extent on another computer

    OK, errno=5 is permissions. Check who the PROSERVICE is started by. The other machine may have full permissions, but PROSERVICE may be owned by "LocalSystem" on the other machine, and that user is not covered by "everyone". Start PROSERVICE as a user, and it should work. KB#17936 may help...
  3. R

    DB cannot started from Progress Explorer Tool

    Silly question - did you install the same progress products and have the same installation type on both of the PCs which have problems? Check the progress.cfg file on both PCs. Are there any other messages in the log file? Have you tried starting the progress database through the proenv command...
  4. R

    Database Contents

    Nope. Have you tried connecting ODBC? Convert it to V9, set up SQL-92 access - you just might be able to get the data out that way. Another option - does the application create reports? Does it put those reports to disk, either as CSV files or spool files? If so, use them! If not, it's...
  5. R

    How to parse the .lg file?

    If you are using 83 or above, check out the database.lic file which resides in the same directory as the log file. That should float your boat.
  6. R

    Progress Session parameters

    Pocket Progress is also a good place to look! Richard
  7. R

    Standby Database

    Hi Progress have just released a product called Fathom for Replication. This will work synchronously. In addition, depending on the version purchased, you can get read-only access to the hot spare and still keep in sync. Funky-doo. Richard
Top