Search results

Windows 2k. Yeah, I called up Progress and was told to change a registry value which I believe was the memory heap. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\ SubSystems\Windows Changed the value in the string to "SharedSection=1024,3072,1532" where it was...

Win2k server progress 9.1d08, 25 databases, 25 4gl brokers and 25 sql brokers. 4gl: -m3 -Mpb 5 -N tcp -S [service name] -L 100000 sql: -Mn 9 -Mpb 4 -N tcp -S [service name] -L 100000 Now I get a new error after the 4am scheduled task restarts the broker, and a single users tries to connect...

It works for a while and then users have problems connecting. I tried using the PROWDOG app, will see if that helps.

We have Progress 9.1D on a win2k server serving 25 databases. To back up the data every morning at 2:45am a scheduled task shuts down the db's with "pccmd.exe proservice stop" which worked fine. Then at 4:00am the db's were started again with "pccmd.exe proservice start" which also worked fine...

I have just received the exact same error. We have 25 progress databases (9.1D) running as the back end of an accounting package that we use on a win2k server. We decided we wanted to use Crystal Reports to supplement the reporting capabilities in the accounting package so we created a sql...