Geir Otto Olsen (THInc Consulting AS) asked a question.

March 4, 2026 at 3:03 PM
Pro2 replproc logging

12.8.9

pro2 6.5

 

I start this as a service (NSSM)

path: D:\Progress\OE12\bin\prowin.exe

Startup: d:\progress\pro2

Arguments: -ininame Pro2.ini -basekey "INI" -b -pf bprepl\scripts\replproc.pf -p bprepl\RunReplProc.p -param "Thread=1"

 

Servicename: ReplService#1

 

and I have another called ReplService#2

 

I get 2 replproc<date>-n.log files where n is 1 and 2

 

In xxxx-1.log I get these messages repeated:

  1. Replication Log posted - Date: 03-04-2026 Time: 15:45:09
  2. Replication Log posted - Date: 03-04-2026 Time: 15:45:09
  3. Replication Log posted - Date: 03-04-2026 Time: 15:45:09
  4. ** Warning -- database kif is already connected. (1012)
  5. ** Warning -- database kifsh is already connected. (1012)
  6. ** Warning -- database kifsql is already connected. (1012)
  7. ** Warning -- database kompis is already connected. (1012)
  8. ** Warning -- database kompissh is already connected. (1012)
  9. ** Warning -- database kompissql is already connected. (1012)
  10. Replication Log posted - Date: 03-04-2026 Time: 15:45:09
  11. Replication Log posted - Date: 03-04-2026 Time: 15:45:12
  12. Replication Log posted - Date: 03-04-2026 Time: 15:45:12
  13. Replication Log posted - Date: 03-04-2026 Time: 15:45:12
  14. ** Warning -- database kif is already connected. (1012)
  15. ** Warning -- database kifsh is already connected. (1012)
  16. ** Warning -- database kifsql is already connected. (1012)
  17. ** Warning -- database kompis is already connected. (1012)
  18. ** Warning -- database kompissh is already connected. (1012)
  19. ** Warning -- database kompissql is already connected. (1012)

and in xxx-2.log

  1. 03-04-2026 16:01:15 - Started ProcStatBlock execution at 03/04/2026 16:01:15,649 Finished ProcStatBlock execution at 03/04/2026 16:01:15,649+01:00
  2. 03-04-2026 16:01:15 - Replication Queue Finished (ReplBlock) at 03/04/2026 16:01:15,654+01:00. Processed a total of 0 records. Total Elapsed Time was: 0h:0m:0s.5ms
  3. 03-04-2026 16:01:15 - 0 records were locked,
  4. 0 records failed, and
  5. 0 transactions were open during this run.
  6. 03-04-2026 16:01:35 - Started ProcStatBlock execution at 03/04/2026 16:01:35,680 Finished ProcStatBlock execution at 03/04/2026 16:01:35,680+01:00
  7. 03-04-2026 16:01:35 - Replication Queue Finished (ReplBlock) at 03/04/2026 16:01:35,685+01:00. Processed a total of 0 records. Total Elapsed Time was: 0h:0m:0s.5ms
  8. 03-04-2026 16:01:35 - 0 records were locked,
  9. 0 records failed, and
  10. 0 transactions were open during this run.

Why do I get the connect messages in -1.log and not in -2.log, and visa versa, there is something I do not understand here :-)

 

 

  • 2 answers
  • 91 views
Peter Judge likes this.

  • Tom Bascom (White Star Software LLC)

    I don't know why you're getting the errors but I wouldn't be using PROWIN.EXE for a background service. That is the job of _PROGRES.EXE

  • Geir Otto Olsen (THInc Consulting AS)

    Sorry Tom, a bit late response... working 10 hours days at the time.. anyway, good for me :-) The reason for using prowin.exe is that I am using assemblies for CrystalReports and I thought that I needed to run prowin for using does .dlls, What is the biggest problems using prowin ? I have runed it for years without any problems... but still learning :-)