1
0
-1

Hello,

We have a new error -16 in the log Urouter for a week, for example  :

[startup] ======================================================================
[startup] Date/time : 2019-03-17 21:00:15.98
[startup] Uniface : [MSW] 9.6.04.02, X401C (Mar 5 2014), $ioprint=0
[startup] Command : Compuware Urouter Uniface 96 Effort /asn=C:\Compuware\Uniface96\common\adm\Urouter_Prod96_ER.asn tcp:+13096, pid=1872
[startup] Directory : C:\Compuware\Uniface96\common\bin\
[startup] OS : Windows 2008 Server Service Pack 2 (Build 6002)
[startup] Processor : x86 Family 6 Model 63 Stepping 2, Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz, 16382 Mb
[startup] Hostname : SRV-CLIENT.effort-remois.fr
[startup] User : system
[startup] ======================================================================
0:00.000.00 t=1884: CONT_ID=%fv: rout.c-163 % %dc: Mon Mar 04 16:01:33 2013 %
0:00.065.24 t=1884: URouter started at 17-mar-2019 21:00:15
0:00.088.30 t=1884: URouter pid=1872;rid=40C35522-8B3C-489B-9170-7FE1423384E0
0:00.094.62 t=1884: started thread to listen to TCP:+13096
0:00.094.63 t=1884: UROUTERSTART: waiting for listening threads
0:00.216.37 t=1884: UROUTERSTART: All listening threads started
0:19.326.72 t=3900: [Sun Mar 17 21:00:34 2019] err=-16: thpsv: Problems receiving request
0:50.040.49 t=3876: [Sun Mar 17 21:01:04 2019] err=-16: thpsv: Problems receiving request
1:20.693.64 t=4400: [Sun Mar 17 21:01:34 2019] err=-16: thpsv: Problems receiving request
1:51.383.33 t=4768: [Sun Mar 17 21:02:04 2019] err=-16: thpsv: Problems receiving request


This continues since.
-16 is a network error according to the documentation.
But who could say more?

which process is executed every 30 seconds?

a "ping" or another?

Note : Uniface version 9.6.04.02, X401C

thank you in advance

    CommentAdd your comment...

    4 answers

    1.  
      1
      0
      -1

      Hello Bernard,

      The urouter log shows you are using $ioprint = 0. That makes it impossible to say anything about these errors. With $ioprint=255 it might be possible to say more. The regular 30-second interval is interesting, but I think this is caused by application logic rather than some internal 'ping'.

      Assuming you are a customer with a maintenance contract, I would recommend that you log a support case with Uniface.

      Best regards,

      Chris Breemer

      1. Bertrand Herbaux

        Thank you.


        Uniface Paris has found the answer : a process on another server scans port 1309. 
        The Uouter eliminates these requests and makes a trace in the log. Thank you all.
      CommentAdd your comment...
    2.  
      1
      0
      -1

      I have received a -16 error when there was trouble retrieving a license. The license failure was in the log from the userver.exe.

      Coding a retry on the activate worked. The solution according to Uniface was to put the the license file in the asn used by userver.


      Below is my example, but it does not exactly match yours.


      [startup] ======================================================================
      [startup] Date/time : 2019-03-14 00:05:10.31
      [startup] Uniface : [MSW] 9.7.04.02, G416 (Apr 16 2018), $ioprint=0
      [startup] Command : "d:\Program Files (x86)\Uniface\Uniface 9.7.04\common\bin\urouter.exe", pid=22540
      [startup] Directory : d:\Program Files (x86)\Uniface\Uniface 9.7.04\common\bin\
      [startup] OS : Windows 2008 Server "R2" Service Pack 1 (Build 7601)
      [startup] Processor : Intel64 Family 6 Model 79 Stepping 1, Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz, 32767 Mb
      [startup] Hostname : AFSERPAPP2.companyname.local
      [startup] User : system
      [startup] ======================================================================
      0:00.000.00 t=22616: CONT_ID=%fv: rout.c-189:csrc:1 % %dc: Fri Feb 23 12:07:09 2018 %
      0:00.008.20 t=22616: URouter started at 14-mar-2019 00:05:10
      0:00.008.30 t=22616: URouter pid=22540;rid=F23F92E1-1DA6-4D5C-A6CB-6A0D91939F45
      0:00.008.50 t=22616: UROUTERSTART: waiting for listening threads
      0:00.066.80 t=22616: UROUTERSTART: All listening threads started
      69:44.240.43 t=19172: srvdead: server sid=47 is dead
      69:44.240.54 t=19172: srvdead: notifying client there is no server
      69:44.240.61 t=19172: [Thu Mar 14 13:10:42 2019] err=-16: thpsv: Problems handling request
      69:56.937.31 t=19172: srvdead: server sid=48 is dead
      69:56.937.35 t=19172: srvdead: notifying client there is no server
      69:56.937.41 t=19172: [Thu Mar 14 13:10:55 2019] err=-16: thpsv: Problems handling request
      70:14.065.36 t=19172: srvdead: server sid=49 is dead
      70:14.065.40 t=19172: srvdead: notifying client there is no server
      70:14.065.45 t=19172: [Thu Mar 14 13:11:12 2019] err=-16: thpsv: Problems handling request
      70:22.087.02 t=19172: srvdead: server sid=50 is dead
      70:22.087.06 t=19172: srvdead: notifying client there is no server
      70:22.087.12 t=19172: [Thu Mar 14 13:11:20 2019] err=-16: thpsv: Problems handling request
      70:29.434.36 t=19172: srvdead: server sid=51 is dead
      70:29.434.40 t=19172: srvdead: notifying client there is no server
      70:29.434.46 t=19172: [Thu Mar 14 13:11:28 2019] err=-16: thpsv: Problems handling request

      1. Bertrand Herbaux
        Thank you, we are looking for this side
      CommentAdd your comment...
    3.  
      1
      0
      -1

      Hi Bernard,

      I have moved this out of topic Uniface 10 development and into Uniface 9 and server.

      Regards,

      Mike

      1. Bertrand Herbaux

        Oh ! Thank you, sorry for the mistake

      CommentAdd your comment...
    4.  
      1
      0
      -1

      Hi,

      netstat -nao | findstr 13096 (in dos window .... )

      Give you client process id (and her  adresse ip )

      Gilles.

        CommentAdd your comment...