Search results

  1. D

    Progress error 395: FYI

    After restoring OpenEdge Release 10.1C04 database, we got Progress error 395, complaining about the lock file value in admprod, but only through the GUI MfgPro screen (not in character). Progress recommends adding the -nolkctr client parameter, but we were able to resolve this by restarting...
  2. D

    MSW/PSW workbenches don't start after install

    Hello, installed MSW/PSW in QAD SE2009 Progress 10, and the workbenches don't start. When clicked, QAD spins for a second and then nothing happens. Went back over the install (licensing, NETUI packages, schema add, data load, help file load, etc) and everything seems okay, all the other MSW...
  3. D

    Newbie NetUI question -- where is client propath set?

    Hello, I inherited a smallish EB2.1 NETUI 2.81.4.87 Progress 10C setup in which there is currently no test code directory. I want to make the NETUI Test client point to my new test code directories, but I haven't had to deal with this before -- where is the propath set for NETUI clients? Is...
  4. D

    Resolved Help! Updated licenses, now db won't start

    Updated licenses for 10.1C on Linux, databases now return this error: Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg, reason=-4. (1732) Unable to read progress.cfg...
  5. D

    Zombies are eating my brain and the watchdog won't help

    Had to reboot our ancient, rusty 8.3A QAD (running on HP-UX 11i) database today due to a nasty issue relating to users who were either kicked through an automated proshut script (it kicks users after about 10 minutes of holding open a transaction, to protect the BI file from hitting 1G and...
  6. D

    Help! One database suddenly slow, other fine

    Hello, we are running QAD 8.6e on Progress 8.3C, sitting on HP-UX. We have two databases, mfgpro85e (which is fine) and addmfgpro (which suddenly starting being slow today; was fine Fri and Sat). Users always connect to both db when entering app. Queries against the slow db are running about...
Top